An interesting proof-of-contept: http2.golang.org.
Especially with simulated latency, HTTP/2 shows its true potential.
HTTP/1: 31s to load
Loading happens in clear concurrency blocks of 6 assets each.
30 seconds later
And done, after a whopping 31 seconds.
HTTP/2: 1.7s to load
Concurrency shows its power here. Assets are loaded over a single multiplexed TCP stream.
1.5 seconds later
These results are in line with my earlier testing on HTTP/2;
Despite all its hate HTTP/2 seems to be receiving, some benchmarks just don't lie.