Nobody cares about web performance. It's hard, expensive and unneeded
summary
Argues that web performance still matters because mobile reality keeps bandwidth and CPU constrained, cites a 5‑second budget of ~100 KB HTML/CSS and ~300 KB JS, and shows wins: an Angular app drops scripting from ~28s to ~3–4s after subscription and form fixes, a rail operator gains £8M/year from a 300 ms improvement, Walmart links 1s to ~2% conversion. Recommends pragmatic steps: Lighthouse + WebPageTest + RUM for measurement, bundle budgets, Brotli, image conversion, lazy loading, and CDN tradeoffs; most gains come from infra and simple removals, not micro‑hacks.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:07Why performance matters
- 3:37Excuse 1: Good enough
- 6:27Mobile internet reality
- 12:07Excuse 2: Complex code
- 21:40Excuse 3: No resources
- 25:10How to start optimizing
- 27:37Summary
- 28:03Q&A
related talks
33mRedefining Web Performance
41mSpeed at Scale: Web Performance Tips and Tricks from the Trenches
28mWhat we talk about when we say "web performances"
29mWeb Performance Kinetosis
32mEverything you need to know about Web Performance
31mWe're All Doing the Best We Can
39mGiving you ways to increase, but also explain site performance, to your boss.
42mLessons Learned Sciencing The Web