Web Performance: Autobahn or Pedestrian Zone?
summary
The talk examines web performance costs—noting each extra second of page load reduces conversions (~5%) and that shaving 1000 ms from viewport render is critical. It presents WebPageTest measurements across locations and a demo site (amuma.de) with ~3s loads, shows an image optimization that saved ~19.75% using Kraken, explains root causes (DNS and TCP handshakes, HTTP/1.1 head-of-line blocking), and recommends practical fixes: avoid redirects (~200 ms), combine CSS/JS, enable gzip, use preconnect/prefetch, and adopt HTTP/2 (about 20% faster in practice).
AI-written summary · about
chapters (8)
- 0:00Web performance basics
- 1:14Speed decides success
- 10:10TCP slow start and latency
- 15:27How browsers render pages
- 23:13Analyzing slow websites
- 33:00HTTP/2 for performance
- 36:14Quick speed wins
- 40:51Q&A
related talks
31mEvery Millisecond Counts: Performance & UX
47mMake the Web Faster
36mNobody cares about web performance. It's hard, expensive and unneeded
29mHigh Performance in the Critical Rendering Path
28mWhat we talk about when we say "web performances"
39mGiving you ways to increase, but also explain site performance, to your boss.
29mWeb Performance Kinetosis
24mWeb Speed in Perfection