Comment by kevg123
> As the packet loss rate increases, HTTP/2 performs less and less well. At 2% packet loss (which is a terrible network quality, mind you), tests have proven that HTTP/1 users are usually better off - because they typically have up to six TCP connections to distribute lost packets over. This means for every lost packet the other connections can still continue.
Why doesn't HTTP/2 use more than one socket?
Because one thing it tries to optimize for is avoiding TLS session negotiation.