HTTP/2 is coming! Unbundle all the things?!?

on YouTube ↗25m

" summary

HTTP/2 reduces parallel TCP connections into one multiplexed stream so latency drops (demo shows ~800 ms saved on a blog and about half the load time on mobile), but old rules still matter: the web averages 2.3 megabyte / 40 TCP connections and rendering must not be blocked. Practical moves: split into small, versioned bundles and long-cache static assets (SVGs), use tree shaking with ES2015 modules via rollup.js or webpack, and follow the maxim best request is a request not being made — note Khan Academy’s case where removing bundling made things slower because gziped repetition disappeared.

AI-written summary · about

" chapters (10)

1. 0:00Start
2. 2:36HTTP/2 is here!
3. 6:19Head of line blocking
4. 7:33triggering requests
5. 12:13mobile connections
6. 12:40Performance guidelines
7. 19:20Frequency of change
8. 20:04Optimised utility layer
9. 20:17Extending the utility layer
10. 20:39Tree Shaking

" related talks

• 01h 00mHTTP/2 - The future of the web todayRob Crowley · NDC Sydney 2017
• 50mHigh-performance web apps using HTTP/2Owais Zahid · Voxxed Days Singapore 2017
• 01h 00mHTTP/2 : What you need to knowRobert Boedigheimer · NDC Sydney 2016
• 20mA quick primer on http2Cyrus Dasadia · Rootconf 2015
• 43mHTTP 2.0: why and howSimone Bordet · Voxxed Days Ticino 2017
• 43mPerformance in the World of HTTP 2.0Dave Methvin · Web Unleashed 2015
• 18mThe Route to HTTP/2Karen Farzam · JSConf.Asia 2015
• 47mHTTP 2.0 from the Developer's ViewpointDave Methvin · NDC Oslo 2016