Answer
HTTP/1.1
- One request at a time per connection; browsers open ~6 parallel connections.
- Head-of-line (HOL) blocking at the request level; text-based headers, no compression.
- Workarounds: domain sharding, sprite sheets, concatenation.
HTTP/2
- Multiplexing: many concurrent streams over a single TCP connection.
- Binary framing, header compression (HPACK), server push, stream prioritization.
- Still suffers TCP-level HOL blocking: one lost packet stalls all streams.
HTTP/3
- Runs over QUIC (UDP) instead of TCP.
- Eliminates TCP HOL blocking (independent streams), faster connection setup (0-RTT/1-RTT, TLS 1.3 built in).
- Better performance on lossy/mobile networks and seamless connection migration.
Summary: 1.1 → fix concurrency with multiple connections; 2 → multiplex over one TCP connection; 3 → move to QUIC/UDP to remove transport-level HOL blocking.