It's My (Third) Party and I'll Cry If I Want To
summary
Shows concrete failures and fixes: a tag manager outage blocks rendering for ~80–90 seconds (Chrome timeout ~80s) and can freeze pages; WebPageTest plus RequestMap CSVs reveal byte/TTFB culprits; use Charles throttling to simulate slow origins and blackhole webpagetest.org to emulate outages. Cites YouTube crypto‑mining ads and carrier mangling of jQuery, and business impact numbers — Trainline 0.3s → £8.1M, Walmart 100ms → ~1% revenue — so mitigate by self‑hosting, async loads, preconnects, and moving critical tags out of the head.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:03Third Parties
- 5:21Key Sections
- 5:40How Can Third Parties Affect Us
- 6:22ManInTheMiddle
- 7:29YouTube
- 8:29Network Issues
- 9:13Third Party Runtime
- 10:10Train Line
- 10:36Walmart
- 11:30Skycalm
- 14:50RequestMap
- 18:17Specific Domains
- 21:40What happens if a file goes missing
- 22:01How well does our JavaScript fail
- 24:46Group by domain
- 26:23Unafraid spoilers
- 33:45Ask Dont Tell
- 41:00Third Party vs CDN
related talks
50mIt’s My (Third) Party, and I’ll Cry if I Want To
47mIt’s My (Third) Party, and I’ll Cry if I Want To
41mIt’s My (Third) Party, and I’ll Cry if I Want To
31mIt’s My (Third) Party and I'll Cry If I Want To
52mIt’s My (Third) Party, and I’ll Cry if I Want To
46mChaperones and curfews: minimising 3rd party impact
46mDeep dive into third-party performance
54mReducing the Speed Impact of Third-Party Tags