But chrome holds back lower-priority requests until after it has finished processing the head of the document.
-
-
-
Sort of. Still issues 1 low priority at a time. Once it gets into the body all bets are off and things like body scripts or fonts get requested after images (but at a higher priority). Also, Firefox, Safari, Edge, etc don't hold back.
-
Ya, just struggling to understanding (and identify) of how HTTP/2 prioritization works. Anyway, big thanks for the official repository for the WebPageTest web-performance testing code.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.