Performance in the World of HTTP 2.0
summary
HTTP 2.0 already lands in major browsers and many servers so implementing it cuts latency by removing head‑of‑line blocking, using header compression to one byte for common tokens, and multiplexing many resources on a single TCP connection. Measured examples: a HuffPost run shows 240 requests and 3.88MB for the home page; server push delivering 1KB CSS arrives without extra round trips. Use Chrome/Firefox devtools and WebPageTest to verify protocol, and check nginx/Apache or CDN support.
AI-written summary · about
chapters (14)
- 0:00Start
- 4:17Servers, Switches
- 9:46HTTP/2: Connections Use Streams
- 11:07HTTP/1: Bloated Headers
- 12:14HTTP/2: HPACK Compression
- 16:08We Didn't Keep the Wire Busy!
- 16:39Connection Coalescing
- 17:37Rethink: Cookieless Domains
- 19:15Rethink: Combining files Combining files reduces requests BUT
- 21:09Server Push
- 23:00How a Browser Prioritizes
- 25:30Chrome
- 25:52Edge
- 26:37HTTP/1 and HTTP/2 Can Coexist
