07-25-2019, 06:10 AM
Hi,
I'm trying to figure out why the HTTP/2 loadout for a particular site is behaving like it is.
The attachment First18H2 shows the first 18 assets being loaded, with the origin site on H2. The other 17 assets come from 8 different CDNs. The next 3 assets being on H/2. So the first 4 assets, are all HTTP 2 (the 4th being Quic/Google Analytics)
[attachment=902]
The attachment First18H1 shows the first 18 assets being loaded, but the origin site is on HTTP 1.1. The next 4 assets after the first, are HTTP /2.
[attachment=903]
What I don't understand is why the loadout looks like it does on First18H2...it looks like it loads the HTML first, then all other assets multiplex?
On First 18H1, it loads the HTML on HTTP 1.1 but then starts loading the other assets on H/2 almost immediately.
There are no primitives in the code to push assets or delay them.
Am I wrong in thinking that First18H2 should be looking more like First18H1?
I'm trying to figure out why the HTTP/2 loadout for a particular site is behaving like it is.
The attachment First18H2 shows the first 18 assets being loaded, with the origin site on H2. The other 17 assets come from 8 different CDNs. The next 3 assets being on H/2. So the first 4 assets, are all HTTP 2 (the 4th being Quic/Google Analytics)
[attachment=902]
The attachment First18H1 shows the first 18 assets being loaded, but the origin site is on HTTP 1.1. The next 4 assets after the first, are HTTP /2.
[attachment=903]
What I don't understand is why the loadout looks like it does on First18H2...it looks like it loads the HTML first, then all other assets multiplex?
On First 18H1, it loads the HTML on HTTP 1.1 but then starts loading the other assets on H/2 almost immediately.
There are no primitives in the code to push assets or delay them.
Am I wrong in thinking that First18H2 should be looking more like First18H1?