2022 State Of JS: A Performance Profile
summary
Surveying State of JS data with WebPageTest and the HTTP Archive and CrUX, the web ships a median of 461 KB median JS with p75 at 857 KB and p90 near 1 MB; unused JS runs 30–44% (p50–p90). Third‑party code is ~63% at median and 73% at p90. Gatsby, Next and React sites show low CrUX pass rates (≈37%, 27%, 33%) and median Lighthouse scores around 34, 31, 29; long tasks and main‑thread boot time drive the failures.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 4:36State of JavaScript 2022 overview
- 8:30JavaScript usage on mobile devices
- 11:25Unused JavaScript and third-party impact
- 14:13Long tasks and performance metrics
- 16:01Core Web Vitals and framework analysis
- 18:30Gatsby performance data
- 20:57Next.js performance data
- 22:23React performance data
- 23:47Vue.js performance data
- 24:51Top performance improvement opportunities
- 28:54Testing and performance oversight
- 29:58WebPageTest and free resources
- 32:06Q&A session
related talks
27mSlashing Performance Bottlenecks and Poor User Experience
37mThe Cost of JavaScript
45mDid We(b Development) Lose the Right Direction?
21mState of Performance
42mLessons Learned Sciencing The Web
41mMake JavaScript Faster
01h 02mThe Wrong Kind of Fast: Embracing Evidence-Based Architecture
51mWhen JavaScript Bytes