The Future of Performance Tooling
summary
Chrome adds a DevTools recorder that captures and replays full user journeys, generates traces and a Lighthouse flow report, and exports flows to Puppeteer or to WebPageTest and Cypress for cross‑browser runs. A new responsiveness metric interaction-to-next-paint appears in PSI and Lighthouse, with Chrome claiming ~70% of users suffer poor responsiveness at least weekly. Lighthouse shows a “minimize work during key interaction” audit and Stack Packs give framework‑specific suggestions.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:39The evolving web experience
- 3:05Focusing on user flows
- 6:01Measuring and testing flows
- 9:10Tooling interop and testing
- 12:38Actionable performance metrics
- 16:37Debugging insights
- 18:28Contextual optimization
related talks
31mAutomated Performance Testing With WebDriver
43mAutomated Performance Testing With WebDriver
29mLighthouse, Headless Chrome, and Puppeteer
37mAutomated Performance Testing With WebDriver
50mHow to Think like a Performance Engineer
27mWays of Frontend performance auditing with Lighthouse
28mDevTools & The Performance Tab
48mLighthouse for Chrome