The Unbearable Weight of Massive JavaScript
summary
Claims that Interaction to Next Paint (INP) exposes JS bloat as the root cause of sluggish sites, and that swapping SPAs for native platform APIs — custom elements, view transitions and the navigation API plus scroll‑snap and scroll‑linked animations — cuts JavaScript from ~55,000 lines to ~650, drops TTI from 12s to 3s, and reduces slow interactions (one site had ~20% >500ms). Framework pass rates can be as low as ~40% for INP; browser‑managed prefetching via speculation rules speeds navigation with zero JavaScript.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 7:45Misaligned priorities
- 12:38Illusion of productivity gains
- 23:52Over-reliance on client JS
- 31:10Embrace the web platform
- 46:43Practical steps
related talks
53mThe Unbearable Weight of Massive JavaScript
39mYou really don't need all that JavaScript, I promise
24mUnderstanding and Optimizing Interaction to Next Paint (INP)
45mDid We(b Development) Lose the Right Direction?
41mHow we make Web Apps lightning fast at Microsoft!
01h 03mSpeed up your Web Application
48mFrom Here to There
37mSecret Shortcuts of Loading Web Performance