Chaperones and curfews – We Love Speed 2019

F085bf2092cb300bac787cc5bc65d301?s=47 Ryan Townsend
September 20, 2019
Programming
0
250

Chaperones and curfews – We Love Speed 2019

F085bf2092cb300bac787cc5bc65d301?s=128

Ryan Townsend

September 20, 2019
Tweet

More Decks by Ryan Townsend

See All by Ryan Townsend
F085bf2092cb300bac787cc5bc65d301?s=48 ryantownsend
1
540
F085bf2092cb300bac787cc5bc65d301?s=48 ryantownsend
1
78
F085bf2092cb300bac787cc5bc65d301?s=48 ryantownsend
1
130
F085bf2092cb300bac787cc5bc65d301?s=48 ryantownsend
0
110
F085bf2092cb300bac787cc5bc65d301?s=48 ryantownsend
0
71
F085bf2092cb300bac787cc5bc65d301?s=48 ryantownsend
0
100
F085bf2092cb300bac787cc5bc65d301?s=48 ryantownsend
0
110
F085bf2092cb300bac787cc5bc65d301?s=48 ryantownsend
0
230
F085bf2092cb300bac787cc5bc65d301?s=48 ryantownsend
0
130

Other Decks in Programming

See All in Programming
4d78b749c315e21a956053dcbf0508a9?s=48 po3rin
2
430
E0e036f89c14b3e59640318eedf9670b?s=48 bkuhlmann
2
210
110cd4dcaed019b3bd9809e541afdeb6?s=48 okuramasafumi
0
200
Fc96157614ee73039c4a575906167979?s=48 fukumura
0
250
38a509643276213e62730e92ef220405?s=48 masatakamiki
0
180
5d0a36a99b7fa2731c2bf1ad56ed1e6f?s=48 struuuuggle
0
190
770ede26fb450c104128e35ac37711fd?s=48 musaprg
0
690
822cde5b176ef140171a27f8294c2bd8?s=48 andycraig
0
540
05aa2872bc4c3a92aca20f009c58a5dd?s=48 riririusei99
0
260
0a98ad166f9cdf8d27d92c37438c6e9d?s=48 matsumana
0
290
A8341bc33e5d88f607328d5a82fa42e1?s=48 smartcamp
0
250
9af444e4e7110845f0b3319efb1ca252?s=48 920oj
1
660

Featured

See All Featured
433acaea1012b25d97ae66da9b998dad?s=48 malarkey
391
60k
C7393b7ba7ec9c8890dd77d209fbb3c9?s=48 maltzj
497
36k
E190023b66e2b8aa73a842b106920c93?s=48 zenorocha
295
39k
56c4053438af8e8b90d6f53cbb7573be?s=48 jakevdp
766
190k
15f2b8221f247985a27a627d2ece72f0?s=48 pauljervisheath
193
15k
20bfe76b3d6105641f879fe45cfc9272?s=48 bkeepers
50
3.9k
6bb82b13cda86d3b821fa44100335ddf?s=48 thoeni
2
290
5f2da528927a2ec9ba4fec2069cbc958?s=48 kneath
293
38k
E4f5d494ebdc9e7cce1aecf3ce3e8bc1?s=48 shpigford
366
42k
61857dafbd287b3027c4dcea9008ad3c?s=48 carmenhchung
13
760
39488f9d172ab92fd352f2cd7b73258d?s=48 mza
80
3.9k
5ce91fa49a613cbc3e20d5f96856473f?s=48 edds
55
9.2k

Transcript

  1. Chaperones and curfews Minimising 3rd party impact Photo by Spenser

    on Unsplash

  2. Who am I? Ryan Townsend @ryantownsend

  3. None
  4. None

  5. • What are third parties? • Why are they problematic?

    • Why use them at all? • What can I do to mitigate against their impact?

  6. What are third parties?

  7. Any infrastructure or service on a separate origin that you

    don’t control

  8. Why are third parties a problem?

  9. Rewind back to Velocity 2011…

  10. None
  11. None

  12. The web lived happily ever after.

  13. Except it didn’t.

  14. • Social media buttons • Tag managers • Ads •

    A/B testing tools • Personalisation • Analytics & Event Capture • Independent Customer Reviews • Retargeting • Affiliate trackers • Live chat • Hosted webfonts • Comment platforms • Videos • Developer Utilities

  15. Source: Steve Souders / HTTP Archive

  16. Source: Yottaa Average # of 3rd Parties (eComm) 2015 2016

    2017 2018 85 60 37 15

  17. “Can I bring a +1?”

  18. requestmap.webperf.tools

  19. But it’s not just the volume…

  20. “There is zero performance overhead to using our synchronous script

    […] our typical response time is around 200ms” – Popular Third Party Provider

  21. Source: Steve Souders / HTTP Archive

  22. And it’s not just the network…

  23. Continual JavaScript execution 1 second

  24. “Third party script execution is the majority chunk of the

    web today” – Patrick Hulce, Lighthouse

  25. The average execution time per third-party is 225ms

  26. 85 third-parties x 225ms = 19s

  27. It’s not even just the visitors who are affected…

  28. • Inaccurate development & QA experience • Unable to perform

    commit/build-time linting • Governance processes in the hands of the 3rd party

  29. Why use third parties?

  30. None
  31. None
  32. None

  33. • You can’t build it all yourself • You shouldn’t

    build it all yourself • You’re hacking around technical limitations • You’re hacking around organisational limitations

  34. So, what can we do?

  35. Identify your third parties

  36. requestmap.webperf.tools

  37. Long-running JavaScript Large payloads webpagetest.org/easy

  38. None

  39. • It’s My (Third) Party and I’ll Cry If I

    Want To
 Harry Roberts (@csswizardry) • AB Testing, Ads & Other 3rd Party Tags
 Andy Davies (@andydavies) • Performance Audit (Live)
 Tim Kadlec (@tkadlec) • Raiders of the Fast Start
 Katie Sylor-Miller (@ksylor)

  40. Consider your loading strategy

  41. 1. Where/when do you need to load it?

  42. Can you load it on user behaviour?

  43. Load reviews on user action -8s blocking JavaScript execution

  44. 2. How critical is it?

  45. Progressive enhancement isn’t just for first-party JavaScript

  46. 3. Do we need ALL of it?

  47. None

  48. • Check for GZIP/Brotli compression • Subset fonts • Centralise

    data capture (e.g. Segment) • Disable loading libraries

  49. You can’t all bring jQuery as your +1!

  50. Check for image transformation

  51. Avoid tech debt

  52. Optimise your 3rd party scripts

  53. A/B test implementation +20s JavaScript execution

  54. 4. Can you load it asynchronously or defer it?

  55. None

  56. “But what about the flicker!?”

  57. Curfew

  58. font-display: fallback

  59. Implement this one NASTY trick… you’ll never believe what happened

    next
  60. None
  61. None
  62. None

  63. <head> <script> function showBody() { document.body.style.display = 'block'; } setTimeout(showBody,

    3000) </script> <script src="https://myadprovider.com/" onload="showBody()" onerror="showBody()" importance="high" async> </script> </head> <body style="display:none"> ... </body> when the script loads/fails: show the body hide the whole body after 3 seconds: show the body regardless
  64. None

  65. function timeout(delay){ return new Promise(function(resolve, reject) { setTimeout(function() { resolve(new

    Response('', { status: 408, statusText: 'Request timed out.' })) }, delay) }) } self.addEventListener('fetch', function(event) { // if the request is not for example.com, serve requests normally if (!event.request.url.includes('example.com')) { return } return event.respondWith(caches.match(event.request).then(function(response) { return response || Promise.race([ timeout(2000), fetch(event.request) ]) })) }) attempt the request force a 2-second timeout service-worker-timeout.twnsnd.com

  66. 5. Can you self-host the resources?

  67. • No DNS lookup • No connection setup • No

    SSL negotiation • “Better” HTTP/2 prioritisation • You can fingerprint and use far-future expiry • Plays nicer with Content-Security-Policies *

  68. What about changes?

  69. None

  70. Dual-phase loading

  71. https://medium.com/caspertechteam/we-shaved-1-7-seconds-off-casper-com-by-self-hosting-optimizely-2704bcbff8ec

  72. https://medium.com/caspertechteam/we-shaved-1-7-seconds-off-casper-com-by-self-hosting-optimizely-2704bcbff8ec

  73. 6. Can we preconnect or preload?

  74. • DNS Prefetch • Preconnect • Preload • Prefetch •

    Prerender (Nostate Prefetch) Check out: Harry Roberts – More Than You Ever Wanted To Know About Resource Hints
  75. None

  76. Choose your friends

  77. None
  78. None

  79. The Windows 95 launch really got out of hand

  80. None

  81. Protect your site from 3rd parties

  82. None

  83. Kill Switch

  84. Feature-Policy

  85. sync-xhr, document-write, legacy-image-formats, max-downscaling-image, unsized-media, image-compression, font-display-late-swap, lazyload, unoptimized-images

  86. Protect your site from your company

  87. Tag Managers

  88. It’s all our fault

  89. • Embed manually and maintain a clear release runway •

    Migrate long-term scripts to core site • Server-side tag management

  90. TWO TAG MANAGERS?

  91. None
  92. None

  93. Remember you have leverage

  94. Everybody wins…

  95. “Huge props to WordAds for reducing their impact from ~2.5s

    to ~200ms on average!” – Patrick Hulce, Lighthouse

  96. 32,000 sites benefitted.

  97. • You don’t make friends taking toys away • Understand

    really how your third parties are used • Work with what you’ve got and optimise • Assume third parties will burn you • Protect yourself • Work with them for the better of the whole web

  98. Thank you! Ryan Townsend CTO, SHIFT – @ryantownsend twnsnd.com/welovespeed