Profile picture
Patrick Meenan @patmeenan
, 6 tweets, 1 min read Read on Twitter
ugh. Browser's implementations of HTTP/2 priorities are worse that I could have imagined (Chrome and Firefox at least try). I'll write it up with pictures and debugging how-to but here are the basics:
Chromium-based (best IMHO but I'm biased):

A strict order is specified with all resources set to "exclusive" (only browser to use the exclusive bit). No concurrency for images but really good for JS, CSS, etc. Ordering is based on priorities from blink.

High-level groupings are created for the resource types and weighted so more-important types get more bandwidth. Within a group all resources are peers, weighted equally (i.e. all scripts download concurrently with a lower weight than css).

No dependencies/grouping. All resources are weighted based on the webkit resource priority (JS/css: 24, font: 16, image: 8). Looks a lot like Chrome's old SPDY implementation but HTTP/2 weights don't work the same way.
Edge/IE: ¯\_(ツ)_/¯

No dependencies, everything gets a weight of 16. Probably a side-effect of the architecture with HTTP/2 being implemented deep in the OS with no priority/dependency info.
tl;dr - for everything except Chrome, ALL of the resources on your page will be downloading in parallel (images competing with your critical CSS/scripts/etc).

Chrome and Firefox are the only two I'd say "support" HTTP/2, the others only support the framing (barely)
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Patrick Meenan
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member and get exclusive features!

Premium member ($30.00/year)

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!