To push, or not to push?! - The future of HTTP/2 server push

on YouTube ↗40m

" summary

HTTP/2 server push promises one RTT savings but often overpushes because the server lacks client cache knowledge; real sites see mixed results and a Shopify case reports a 50% faster time-to-text (≈1.2s) from preload of fonts. Practical patterns are async push from an edge or CDN, or using a service worker to avoid repeat pushes. Upcoming fixes include cache digests to let servers know client caches and 103 Early Hints plus priority hints to let browsers fetch and prioritize earlier and smarter.

AI-written summary · about

" chapters (13)

1. 0:00Start
2. 5:05Critical Path
3. 8:24The Preload Api
4. 9:02Hidden Critical Sub Resources
5. 10:22Render Tree
6. 11:17Preload Api
7. 14:20Traditional Request Flow
8. 19:21Recap Server Push
9. 27:40User Agent Sniffing on the Server
10. 27:56The Rate of Adoption of Push Is Extremely Low
11. 29:24Async Push Pattern
12. 32:25103 Early Hint Status Code
13. 38:30Hosting Static Assets with S3

" related talks

• 26mTo push, or not to push?! - The future of HTTP/2 server pushPatrick Hamann · JSConf EU 2018
• 24mEmbracre HTTP2 Server PushDale Bustad · CascadiaFest 2016
• 03h 16mPUSHing web app performance with HTTP/2Inian Parameshwaran, Sebastiaan Deckers · JSConf.Asia 2018
• 01h 00mHTTP/2 - The future of the web todayRob Crowley · NDC Sydney 2017
• 19mHTTP/2 is here, now let's make it easyRebecca Murphey · dotJS 2015
• 39mWith Great Power Comes Great Responsibility - Using HTTP/2 ResponsiblyTomasz Pęczek · DevConf 2018
• 50mHigh-performance web apps using HTTP/2Owais Zahid · Voxxed Days Singapore 2017
• 47mHTTP 2.0 from the Developer's ViewpointDave Methvin · NDC Oslo 2016