It’s My (Third) Party, and I’ll Cry if I Want To
summary
Shows how to find, measure and fix third-party cost: run WebPageTest and feed its ID into RequestMap to get a CSV, import that into a spreadsheet, then re-run WebPageTest blocking domains to compare impact. Use Charles proxy and WebPageTest’s black‑hole host to simulate slow origins or outages. Real findings: a tag manager or Google Fonts can cause a 1.3 minute blank screen, 200ms of third‑party delay maps to millions in lost revenue (Trainline £8.1M for 300ms), and fixes include self-host critical assets, async loading, preconnect, CSP and SRI, and simply using fewer third parties.
AI-written summary · about
chapters (6)
- 0:00The risks of third-party code
- 6:26Understanding security impacts
- 11:12Performance and outages
- 17:31Auditing and measurement
- 31:32Communication and collaboration
- 40:01Mitigation and best practices
related talks
41mIt’s My (Third) Party, and I’ll Cry if I Want To
50mIt’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
46mDeep dive into third-party performance
54mReducing the Speed Impact of Third-Party Tags