Bringing Excellent UX to the React Ecosystem via Strong Defaults in Next.js
summary
Chrome teams partner with Next.js and React and ship concrete tooling: Google font inlining that eliminates a round trip and pairs with preload, a Script loader: lazy/defer/eager/dangerous to control third‑party download timing, an Image component with automatic optimization, sizing, preload and CDN hooks, and a conformance layer (an ESLint + Webpack conformance system) that warns and enforces defaults. Features land in Next.js at varied stages—shipped, in review, or experimental—and are validated by tracing and measured FCP/LCP gains on real partner sites.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:05Open-source powered tools
- 4:15The challenges are the same
- 4:49Scheduling is a hard problem
- 11:52Critical Resources Preloaded
- 12:17Loading third-party scripts
- 13:45Next.js Image Component
- 14:43Critical CSS
- 16:33Static generation
- 17:16Server-side rendering
- 17:39Concurrent Mode
- 20:19A core vision
related talks
18mNext.js - The Hybrid Architecture for Web Developer
24mChrome ❤️ ⚛️ (no, really)
26mClosing Keynote
45mOpening Keynote
21mWhat to expect from a modern web framework?
27mOptimizing the Critical Rendering Path in React
21mNuxt Performances
42mElevating the Web Platform with the JavaScript Framework Community