Everything you need to know about Web Performance
summary
Claims that improving Largest Contentful Paint halved bounce rate for NDTV and that optimizations lifted mobile revenue by 42% for a resale service; recommends keeping TTFB under 200 ms via SSG/SSR caching, avoiding external calls on the critical path, shipping compressed small assets, code‑splitting and lazy hydration (Vue lazy hydration example), serving right‑sized lazy images, offloading third‑party scripts to web workers with partytown, using service worker caching via workbox, and measuring with webpagetest plus CI checks like bundle‑size and Lighthouse CI.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:51Performance is hard
- 9:19Avoid external connections on critical path
- 16:02Workbox
- 18:35Optimize your critical path
- 20:41Optimize hydration
- 29:18Define Performance Budget
- 30:43Performance is a tradeoff
related talks
36mHacking Web Performance
58mNeed for speed 8, performance tuning of your web application
38mCSS and the first meaningful paint
39mGiving you ways to increase, but also explain site performance, to your boss.
36mNobody cares about web performance. It's hard, expensive and unneeded
41mSpeed at Scale: Web Performance Tips and Tricks from the Trenches
01h 04mNeed for speed 8, performance tuning of your web application
31mWe're All Doing the Best We Can