It’s My (Third) Party, and I’ll Cry if I Want To
summary
Shows specific failures and fixes: measure third‑party overhead with WebPageTest and Request Map to get a jellyfish CSV, rerun blocking tests, and simulate outages with Charles throttling and a black‑hole IP; quantify cost (200 ms per script, Trainline sees +0.3s → £8.1M revenue impact, every 100 ms ≈ +1.11% conversions); demonstrate a blocking script that stalls renders up to 80s on UNIX (20s on Windows); advise concrete mitigations: self‑host, async load, preconnect, CSP, SRI, lazy‑load.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:10Third-party performance risks
- 10:22Third-party script security
- 21:18Measuring third-party impact
- 32:42Risks with marketing teams
- 42:16Mitigating third-party issues
related talks
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
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
53mThird Party Woes
05mThe Performance Of Others