What we talk about when we say "web performances"
summary
Claim: average web pages hit 2 MB average page size (May 2015) and studies tie delays to revenue — roughly $1.6B lost per second — so front-end cost matters. Concrete techniques shown: server push via HTTP/2 link header, Brotli compression, edge-side includes for fragment caching, PRPL-style precache plus lazy load, and inlining critical CSS computed with a headless Chrome critical-css extractor; measure with Navigation Timing, Speed Index, first-meaningful-paint, time-to-interactive and custom performance marks.
AI-written summary · about
chapters (14)
- 0:00Introduction to web performance
- 1:24From simple pages to complex assets
- 4:16Impact of slow loading times
- 5:43Web applications vs web pages
- 9:17Browser-side performance focus
- 10:43HTTP/2 server push benefits
- 12:50Critical CSS optimization
- 15:47Real-world performance challenges
- 17:34Measuring user device performance
- 21:11Angular app performance patterns
- 23:00Why performance matters today
- 24:51Third-party code bottlenecks
- 25:54Communication beyond optimization
- 26:37Premature optimization warning
related talks
33mRedefining Web Performance
30mPerformance as a Religious Experience
31mEvery Millisecond Counts: Performance & UX
36mHacking Web Performance
36mNobody cares about web performance. It's hard, expensive and unneeded
39mGiving you ways to increase, but also explain site performance, to your boss.
32mEverything you need to know about Web Performance
48mJavaScript in Browser Performance