It’s My (Third) Party and I'll Cry If I Want To
summary
Shows concrete audits and fixes: uses requestmap.webperf.tools plus WebPageTest and the WebPageTest block feature to compare before/after, probes origins with Charles Proxy, and pulls runtime hotspots via Chrome profiles and SpeedCurve. Quantifies harm — a 300 ms gain maps to £8.1M uplift, 100 ms to ~$376k, a 200 ms third-party delay becomes hundreds of thousands lost — and demonstrates breakage (Chrome can hang ~80s leaving a blank page). Advises self‑host, async loading, preconnect, and a Google Sheets CSV template for prioritization.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:55Harry Roberts
- 4:30Security
- 6:28Delays
- 11:05Performance Audit
- 14:40Slow Origin
- 15:25Full Outage
- 16:05Missing Files
- 18:30Runtime Cost
- 20:30Discuss
- 21:52Form a hypothesis
- 24:04Third party problems with internal teams
- 26:22Ask Dont Tell
- 27:22SelfHost
- 28:47Resource Hint
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
47mIt'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
54mReducing the Speed Impact of Third-Party Tags
05mThe Performance Of Others