Downloaded 18 times
Uploaded byBarbara Bermes
3rd party footprint - A PUBLISHER'S TAKE ON CONTROLLING 3RD PARTY SCRIPTS
The document discusses the implications of third-party scripts on website performance, highlighting their prevalence and potential issues such as single points of failure and privacy concerns. It outlines various types of third-party scripts, their impact on loading times, and offers solutions like asynchronous loading and monitoring. The document also encourages publishers and developers to take proactive measures regarding third-party content management.
More Related Content
Similar to 3rd party footprint - A PUBLISHER'S TAKE ON CONTROLLING 3RD PARTY SCRIPTS
3rd party footprint - A PUBLISHER'S TAKE ON CONTROLLING 3RD PARTY SCRIPTS
- 1. #WDC14 3RD PARTY FOOTPRINT BARBARABERMES | @BBINTO A PUBLISHER'S TAKE ON CONTROLLING 3RD PARTY SCRIPTS
- 2. #WDC14 I LIVE INTORONTO, CANADA
- 3.
- 4. #WDC14 I’M PASSIONATE ABOUTWEB PERF
- 5. #WDC14 LET’S GET THISPARTY STARTED
- 6. #WDC14 –Ben Vinegar, Authorof “Third-Party Script” “In the strictest sense, anything served to the client that’s provided by an organization that’s not the website provider is considered to be third-party”
- 7. #WDC14 TYPES OF 3RDPARTY SCRIPTS Ads Tracking and Analytics Fonts Social Media Libraries and Frameworks
- 8. #WDC14 WHAT’S THE #1USED 3RD SCRIPT?
- 9. #WDC14 STATS FROM BIGQUERY #WDC14
- 10. #WDC14 31% 34.5% 38% 2011 2013 2014 32% 36% 38% 3rdparty content DISTRIBUTION OF 3RD PARTY SCRIPTS VS. 1ST PARTY #WDC14
- 11. #WDC14 Advertising Analytics Personalization Marketing Tag Management Search Social Media 025 50 75 100 23 45 53 53 62 92 92 Percentage of sites with each third party function present Source: Intechnica - The impact of third party content on retail web performance
- 12. #WDC14 VISUALIZE THE IMPACTOF 3RD PARTY SCRIPTS
- 13.
- 14.
- 15.
- 16.
- 17.
- 18. #WDC14 BUT WHAT’S THEISSUE?
- 19. #WDC14 THINGS TO TALKABOUT TODAY
- 20. #WDC14 THE ISSUES ANDNEGATIVE IMPACTS Performance Front-end Single Point of Failure (SPOF) Privacy
- 21. #WDC14 POTENTIAL SOLUTIONS Safe snippets Cachingand Hosted Libraries Tools and Initiatives
- 22.
- 23. #WDC14 The value youget out of the widget needs to be greater than the performance hit you are taking - John Hjelmstad Google I/O 2012 (How we Make JavaScript Widgets Scream) RULE OF THUMB
- 24. #WDC14 A user whohas to endure an 8-second download delay spends only 1% of their total viewing time looking at the featured promotional space on a landing page. In contrast, a user who receives instantaneous page rendering spends 20% of viewing time within the promotional area (source: Jakob Nielsen) PERCEPTION OF PROMOTIONAL SPACE
- 25. #WDC14 WHAT WOULD ALIFE WITHOUT ADS FEEL LIKE?
- 26. #WDC14 THE PERFORMANCE IMPACTOF ADS #WDC14
- 27. #WDC14 Using no (client-side)ad code reduced CBC’s page load time by 40% 40% <script/>
- 28.
- 29. #WDC14 ArithmeticMeanins 0 2.5 5 7.5 10 10/4/12 10/31/12 BAD 3RDPARTIES (CBC TOUCH SITE) Smooth sailing Client-side Ads Ads turned off Server-side Ads Source: Keynote Daily Reports We noticed a spike #WDC14
- 30. #WDC14 SINGLE POINT OFFAILURE
- 31. #WDC14 A single pointof failure (SPOF) is a part of a system that, if it fails, will stop the entire system from working –Wikipedia
- 32. #WDC14 THE OFFENDER It willblock rendering anything after this line
- 33. #WDC14 YEAH….BUT DO THIRDPARTY PROVIDERS EVER GO DOWN??
- 34.
- 35.
- 36.
- 37.
- 38. #WDC14 THE GREAT FIREWALLOF CHINA
- 39. #WDC14 SIMULATING SPOF ONTECHCRUNCH
- 40.
- 41.
- 42.
- 43. #WDC14 SPOF WIRED Without SPOF WithSPOF: Visually complete 40s
- 44.
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52. #WDC14 SAFEST WAY: DYNAMICSCRIPT TAG (to cover most of the browsers)
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60.
- 61. #WDC14 5 seconds 25seconds
- 62.
- 63.
- 64. #WDC14 PREVENTION! PROTECT YOURSELF WITHTHE HELP OF TOOLS
- 65.
- 66. #WDC14 CACHE POLICIES 30min. 30 min 12hrs 20 min 1 hr 336 hrs no cache 1 hr 3 min #WDC14
- 67.
- 68. #WDC14 DON’T JUST COPYAND PASTE #WDC14
- 69.
- 70.
- 71. #WDC14 RATHER DO THIS:SILENTLY FAIL
- 72. #WDC14 Other 55% 1.7.2 14% 1.7.1 13% 1.10.2 9% 1.8.3 9% GOOGLE’S HOSTED JQUERYFRAGMENTATION Source: March 2014, Big Query result on jQuery from Google CDNs
- 73. #WDC14 SO, WHATS THEVERDICT: HOSTED LIBRARIES OR NOT?
- 74.
- 75. #WDC14 “The Like buttonis the quickest way for people to share content with their friends. A single click on the Like button will 'like' pieces of content on the web and share them on Facebook.”
- 76. #WDC14 What they don’ttell you…. Track the visited website, your IP, and more….???? Did you agree to that? !
- 77. #WDC14 OPEN SOURCE INITIATIVES AND RESOURCES
- 78.
- 79.
- 80. #WDC14 3RD PARTY PERFHEROES PHILIP TELLIS & STOYAN STEFANOV
- 81.
- 82.
- 83.
- 84.
- 85. #WDC14 NEXT TIME BEFOREYOU COPY AND PASTE
- 86. #WDC14 WHAT TO DOAS A PUBLISHER & DEVELOPER • Refuse 3rd party content that doesn’t provide async options • Put the risk in the SLA (uptime etc.) • Review jsmanners • Educate other (junior) developers
- 87. #WDC14 • Ask forserver-side options • Evaluate tag managers • Investigate hosted libraries (if no own CDN is available) • Monitor, monitor, ….and monitor WHAT TO DO AS A PUBLISHER & DEVELOPER
- 88. #WDC14 WHAT TO DOAS A SCRIPT PROVIDER • Provide non-blocking code samples and snippets • Educate developers and verify the integration of your script developers (proof-check)
- 89.
- 90.