Third Party Woes
summary
Audit shows one checkout widget injects ~800 KB of JS and removing it cuts total blocking time by ~2.4s, a chatbot removal improves LCP by ~2.24s, and moving scripts into a worker with PartyTown in a worker initially slashes main‑thread contention but breaks when GTM injects scripts so it gets removed. Tools used: requestmap/webpagetest/lighthouse and the Core Web Vitals technical report. Emerging fixes: server/edge rewrites and measured total blocking time comparisons.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:26Early web performance insights
- 3:12Third-party scripts challenges
- 8:09Analyzing third-party performance
- 17:24Finding problematic scripts
- 19:11Evaluating necessity and alternatives
- 22:22Unavoidable dependencies frustration
- 25:57Website owners' struggles analogy
- 27:19Party Town and Cloudflare Workers
- 31:14Other performance strategies
- 34:02Third-party scripts data lack
- 37:59Core Web Vitals technical report
- 39:02Call to action for community
- 44:45Third-party-free future dream
- 45:15Q&A
related talks
09mOffloading Main Thread: Improving Web Performance with PartyTown
46mChaperones and curfews: minimising 3rd party impact
54mReducing the Speed Impact of Third-Party Tags
31mIt’s My (Third) Party and I'll Cry If I Want To
13m"Don't Let Third Parties Slow You Down"
52mIt’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
41mIt’s My (Third) Party, and I’ll Cry if I Want To
