Getting your Team Passionate About Web Performance to Achieve Performant Web Apps
summary
A year-long program at a 100+ developer consultancy cuts page load times by 50–80% and raises apps meeting a <3s interactivity goal from 3 of ~20 to 12. It uses value stream mapping to pinpoint which of nine steps slow a page, implements jidoka checks (IDE import-cost, Chrome Coverage, paint-flashing, why-did-you-update), enforces bundle size via 500KB CI threshold and Bundlesize, and runs weekly perf workshops plus a shared performance-budget spreadsheet.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker intro
- 1:18Performance improvement journey
- 3:06Three pillars of performance culture
- 3:29Lean methodology and value stream
- 7:03Value stream analysis benefits
- 10:19Jidoka philosophy for developers
- 11:24IDE and CI performance tools
- 14:16Hidden Chrome DevTools features
- 17:36Bundle size monitoring tools
- 18:40Bundle Phobia for library selection
- 20:27Sharing performance knowledge
- 21:11Weekly performance meetings
- 21:54Dedicated performance community
- 22:15Visual management and progress
- 23:39Learning resources for web performance
related talks
01h 04mNeed for speed 8, performance tuning of your web application
28mEmpowering a Performance Culture
48mThink Fast, First: Empowering a Performance Culture
57mSite-Speed That Sticks
29mThe Road to Web Performance in 3 Critical Steps
29mClient Says Your Awesome Web App Works Slowly. Now What?
39mFrom make it work to make it fast: quick wins to boost your application
23mPerformance Optimizations for Progressive Web Apps