To push, or not to push?! - The future of HTTP/2 server push
summary
Preload headers give a measurable win — customers see 50% (≈1.2 s) improvement for fonts and hidden subresources; HTTP/2 server push saves a round trip but suffers races and per-connection push caches, with a CDN observing only 800 pushes per million requests. Typical server think time is 200–400 ms, Node already supports HTTP/2 push, and promising fixes include a cuckoo-filter cache-digest and the 103 Early Hints response to let the browser decide.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:40To push or not to push
- 5:10Preload API
- 15:45The Problem
- 17:33The Cache
- 18:59Summary
- 19:55Edge
- 21:17Cached Digest
- 22:17JIT specification
- 22:48Early hints specification
- 25:10Conclusion
related talks
40mTo push, or not to push?! - The future of HTTP/2 server push
24mEmbracre HTTP2 Server Push
19mHTTP/2 is here, now let's make it easy
01h 00mHTTP/2 - The future of the web today
03h 16mPUSHing web app performance with HTTP/2
50mHigh-performance web apps using HTTP/2
43mPerformance in the World of HTTP 2.0
47mHTTP 2.0 from the Developer's Viewpoint