vs HTTP/2 though, the reality of multiplexing benefits is more complicated: Latency of responses isn't just network RTT: a slow server response because of server processing will block your TCP connection just as hard as network latency. Your load balancer is often not co-located with your backend, e.g. if you serve everything through a geographically distributed CDN, which serves most content from its cache, but falls back to a separate application server backend for dynamic content & cache.