HTTP Headers that Make Your Website Go Faster
summary
Shows how to use HTTP headers with Varnish Cache to cut origin load: claims 1.3 Tbps on one machine and 1.17 Gbps per watt as performance/efficiency proof points, recommends emitting ETags + conditional 304 and validating them early (pre-hook or Redis) to skip framework boot, explains s-maxage/age remaining, stale-while-revalidate and stale-if-error for async revalidation and outage tolerance, covers Vary, immutable, surrogate-control and Edge Side Includes (ESI) for composable edge rendering.
AI-written summary · about
chapters (15)
- 0:00Website speed matters
- 2:28Caching fundamentals
- 8:26Caching proxies protect servers
- 10:11HTTP headers for caching
- 11:35Key caching concepts
- 13:40Cache-Control deep dive
- 18:15Efficient revalidation
- 22:29Stale content handling
- 25:18Real-time updates with must-revalidate
- 26:23Immutable content rules
- 28:32No-cache vs no-store directives
- 29:57Multilingual caching
- 32:25Surrogate caching and edge
- 33:50Edge Side Includes
- 36:40Implementation beyond headers
related talks
56mCaching the uncacheable in Varnish
38mThe power of cache in a slow world
58mCaching the uncacheable: delivering personalized experiences without sacrificing performance
39mHTTP headers for the responsible developer
28mTaking Laravel to the edge with HTTP caching & Varnish
28mCaching the uncacheable in Varnish
34mHow HTTP already solved all your performance problems 10 years ago
33mTaming the Beast: Understanding and Harnessing the Power of HTTP Proxies
