Google Chrome does not do multiplexing with http2

Question

I am building a webapp and serving it over http2. However when I analyze network in Google Chrome (Version 59.0.3071.115 (Official Build) (64-bit))\'s developers tools, it i

Answer 1

There may be multiple reasons why Chrome decides to limit multiplexing when using HTTP/2.

For example, the behavior is very different when you are downloading a page with a large number of images, depending on whether the images are shown or not in the browser viewport.

The documents you are downloading are scripts and scripts may block, or depend on each other, or otherwise change the way the browser downloads resources.

In fact, if you go to online examples of HTTP/2 such as https://http2.golang.org/gophertiles?latency=0, you will see that Chrome does multiplex really well the download of images (but only if they are displayed in the viewport).

Therefore for your case it could be something with the scripts; perhaps they have dependencies on each other, and that is why Chrome cannot multiplex them beyond 6 at a time.

I would not be surprised if this is a limit of JavaScript loaders that assume HTTP/1.1 and are now obsolete with HTTP/2.

You can use the "Performance" tab in the Chrome Developer Tools to understand more about the performance of your page.

You also want to look at tools such as Page Speed, that give you an idea of how to optimize your page.

In summary, I don't think it's an issue with how Chrome implements HTTP/2, but rather something in your application/scripts that is not optimized for HTTP/2.