It’s My (Third) Party, and I’ll Cry if I Want To
summary
Third-party scripts often multiply requests and bytes — WebPageTest plus RequestMap shows requests rising 4.2× and bytes 2.7×, and blocking tag managers can stall Chrome for over 80 seconds (1.3 minutes). Audit with requestmap + WebPageTest, extract domains, rerun with blocks, and profile runtime (DevTools bottom‑up) — Google Tag Manager sometimes costs more CPU than the app. Mitigate by self‑hosting critical assets, loading third parties async, using preconnect/preload, SRI, CSP/Feature Policy, and targeted throttling with Charles proxy.
AI-written summary · about
chapters (4)
related talks
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
31mIt’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
47mIt'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