Need for speed 8, performance tuning of your web application
summary
Claims concrete fixes that reduce real load times and conversions: use Lighthouse and WebPageTest plus RUM or New Relic, measure First Meaningful Paint, hero render, input responsiveness and TTI, aim for TTI <4s on 3G and 170KB gzipped bundle targets, prefer defer/async, code splitting, dynamic import, preload/prefetch and server push, compress and serve images as WebP with srcset and lazy load, cache via proper headers or CDN, and optimize fonts with font-display. A quick image and unused-library cleanup yields a 33% bump from image fixes and removing dead JS (a mining loop) cuts main-thread time.
AI-written summary · about
chapters (20)
- 0:00Start
- 6:54Choose your metrics
- 10:54Data sources
- 11:45Process
- 12:26Know your tools
- 15:04Goals
- 17:07Size
- 18:01How browsers build the DOM
- 19:55Critical Rendering Path
- 21:34Rules to keep in mind
- 21:53Did we miss something?
- 23:38CSSDOM
- 23:58PRPL
- 26:07Styles
- 28:36Using webpack?
- 29:16JavaScript
- 33:31Web Fonts
- 37:45Progressive images
- 38:56Recap
- 39:29Caching
related talks
01h 04mNeed for speed 8, performance tuning of your web application
32mEverything you need to know about Web Performance
29mHigh Performance in the Critical Rendering Path
01h 03mSpeed up your Web Application
41mSpeed at Scale: Web Performance Tips and Tricks from the Trenches
23mOptimizing page load speed on front end side
31mWe're All Doing the Best We Can
27mHigh Performance in the Critical Rendering Path