Optimizing Third-Parties - Nuxt and Chrome Aurora
summary
Chrome Aurora claims that third parties correlate strongly with worse metrics using a 90,000‑site sample: sites with ≥1 third party have 36% good LCP (≤2.5s) while sites with ≥50 third parties only 1% do, and INP (≤200ms) degrades similarly. The team builds concrete tools—useScript composable, higher‑order composables like useGoogleAnalytics and useGoogleTagManager, wrapper components, and a light YouTube embed—and shows the embed loads significantly faster; a Nuxt third‑party module is shipping soon.
AI-written summary · about
chapters (10)
- 0:00Chrome Aurora and Nuxt collaboration
- 1:22Third-party resources impact
- 2:30Third parties and LCP correlation
- 3:32Third parties and INP
- 4:56Developer challenges with third parties
- 6:22Managing third-party scripts
- 7:27useScript and utilities
- 8:30Third-party embed wrappers
- 9:12Optimizing third-party components
- 9:54Acknowledgments
related talks
14mOptimizing Third-Party Loading in Next.js
50mOptimizing third parties in frameworks with DX
46mDeep dive into third-party performance
30mHow to use Nuxt.js and Chrome
46mChaperones and curfews: minimising 3rd party impact
31mIt’s My (Third) Party and I'll Cry If I Want To
22mOptimally using third-party services with Next.js
52mIt’s My (Third) Party, and I’ll Cry if I Want To