So Long and Thanks for All the Requests: Front-end Performance in the Age of HTTP/2
summary
HTTP/2 changes the tradeoffs: multiplexing and HPACK cut per-request overhead, but excessive unbundling (case studies show tens-to-hundreds of files can slow sites) still costs CPU and compression savings. Practical tactics: use partial bundles (component or page bundles via Drupal 8 libraries), prefer SVG icons and responsive images, avoid data‑URI fonts, experiment with server push cautiously (needs cache-digest or service worker help). HTTPS/HTTP2 is broadly supported (~90–95%); CDNs, image compression and preload/font loading (Font Face Observer) remain essential.
AI-written summary · about
chapters (17)
- 0:00Start
- 3:09Minimize number of font files
- 18:07HTTP/2 is here!
- 26:22Turn on HTTP/2!
- 29:31Improve critical path
- 34:24Server caching still matters
- 35:29Fallbacks to http/1.1?
- 37:13Server support
- 38:12Browser support
- 38:44CDN support
- 39:16Case studies
- 42:05Unbundling has limits
- 48:38Assets in stream
- 49:13Pushing all assets
- 51:32Service workers?
- 52:23Push assets to service worker
- 52:35Service worker caching HTML?
