Skip to content

Tracks issues / notes for HTTP/2 prioritization across browsers, CDNs and servers


Notifications You must be signed in to change notification settings


Folders and files

Last commit message
Last commit date

Latest commit



34 Commits

Repository files navigation

Tracking HTTP/2 Prioritization Issues


HTTP/2 uses multiplexing to support multiple concurrent requests over the same TCP connection.

HTTP/2 also has a prioritization scheme (via weights & dependencies) that enables browsers to communicate the relative priority of each request.

Unfortunately not all servers are equal – some don't appear to implement prioritization and so serve responses on a 'first come, first served' basis, and others that implement prioritization seem to have a few bugs too – and these issues can create a suboptimal experience for the visitor. This can be a result of the server implementation itself or (more likely) from how it is configured in production.

Browsers implement their priority trees in quite different ways too – if you're interested in digging deeper @DaanDeMeyer's h2vis and WebPageTest can visualize these for Chrome and Firefox.

Now WebPageTest visualises HEADERS and DATA frames for responses we can get a much clearer picture of how prioritization is implemented across different servers and CDNs.

This repo aims to track and highlight prioritisation issues – if they get fixed then the web become better for all of us. As long as prioritisation is broken there will be significant performance issues with HTTP/2 which isn't good for anybody.

Getting Started

@PatMeenan's http2priorities test page is the easiest way to get started – find an appropriate image on your server / host / CDN of choice and then test it using Chrome with WebPageTest using the "3G Fast" network profile (do not use 3G, as of Chrome 74 Chrome restricts the number of in-flight requests on low-speed connections). It is recommended that you do a full 9 runs to make sure it consistently passes and is not intermittent.

Pay close attention to requests 33-34, these are high-priority visible images that are loaded after the low-priority images start to load. They have a higher priority so their frames should be re-prioritized ahead of the earlier images.

CloudFlare - reprioritizes the requests Waterfall with important resources being reprioritised

CloudFront - requests are only partially reprioritized Waterfall with important resources being partially reprioritised

Netlify - requests are not reprioritized Waterfall with important resources not being reprioritised

If requests 33-34 don't appear to be prioritised correctly, please raise an issue with the relevant project or vendor.

Visually the difference can be quite dramatic in the filmstrip view: Waterfall with important resources being reprioritised

Current Status

If you create an issue in this repo with a link to your test (whether good or bad) we'll add it to the table below.

It is important to note that what matters most is whatever the edge is that terminates the HTTP/2 connection from the browser. For example, if you have a CDN in front of a hosting provider (or load balancer) then the CDN will be the thing being tested (and that has the most impact). That also means that you can potentially solve broken prioritisation by putting your site behind a CDN that passes.

CDNs / Cloud Hosting Services

CDN / Hosting Status Test Result
Akamai Pass ✅ Dec 22, 2018
Amazon CloudFront FAIL ❌ Nov 28, 2019
BitGravity FAIL ❌ Dec 22, 2018
Cachefly FAIL ❌ Dec 22, 2018
CDN77 FAIL ❌* Dec 22, 2018
CDNetworks FAIL ❌ Dec 22, 2018
CDNsun Pass ✅ Dec 22, 2018
ChinaCache FAIL ❌ Dec 22, 2018
Cloudflare Pass ✅ Dec 22, 2018
DreamHost Pass ✅ Dec 22, 2018
Edgecast FAIL ❌ Dec 22, 2018
Facebook Pass ✅ Dec 22, 2018
Fastly Pass ✅ Dec 22, 2018
Google Cloud CDN FAIL ❌ June 12, 2019
Google Firebase Pass ✅ Dec 22, 2018
Google Storage FAIL ❌ Dec 22, 2018
Highwinds FAIL ❌ Dec 22, 2018
Incapsula FAIL ❌ Dec 22, 2018
Instart Logic FAIL ❌ Dec 22, 2018
KeyCDN FAIL ❌ Dec 22, 2018
LeaseWeb CDN FAIL ❌ Dec 22, 2018
Level 3 FAIL ❌ Dec 22, 2018
Limelight FAIL ❌ Dec 22, 2018
Medianova FAIL ❌ Dec 22, 2018
Microsoft Azure FAIL ❌ Dec 22, 2018
Netlify FAIL ❌ Nov 28, 2019
Reflected Networks FAIL ❌ Dec 22, 2018
Rocket CDN FAIL ❌ Dec 22, 2018 Pass ✅ Jan 1, 2019
Sucuri Firewall FAIL ❌* Dec 22, 2018
StackPath/NetDNA/MaxCDN FAIL ❌ Dec 22, 2018 Pass ✅ Dec 22, 2018 Jetpack CDN (Photon) FAIL ❌ Dec 22, 2018
Yottaa FAIL ❌ Dec 22, 2018
Zeit FAIL ❌ Feb 02, 2020
Zenedge FAIL ❌ Dec 22, 2018

* Intermittent Failure

Load Balancers

This is for cloud or on-premises load balancers (Amazon ALB, Citrix Netscaler, Foundry F5, etc).

Load Balancer Status Test Result
Amazon AWS ALB FAIL ❌ Dec 3, 2018
Foundry F5 FAIL ❌ Nov 28, 2019


Most servers technically support HTTP/2 prioritisation but are effectively broken when deployed because of buffering in the networking path (within the server, in the TCP stack or in the network itself). Read more about it here.

TODO: Add notes about configuration settings to get prioritisation working for various operating systems and servers.

Finding Test Images

The HTTP Archive BigQuery dataset is particularly useful for finding images for a given CDN or host for testing.

Here is a sample query (warning, each query run can consume close to 1TB of BigQuery quota):

  RTRIM(LTRIM(JSON_EXTRACT(payload, '$._full_url'),"\""),"\"") as url,
  INTEGER(JSON_EXTRACT(payload, '$._bytesIn')) as size
  RTRIM(LTRIM(JSON_EXTRACT(payload, '$._protocol'),"\""),"\"") = "HTTP/2" AND
  RTRIM(LTRIM(JSON_EXTRACT(payload, '$._contentType'),"\""),"\"") LIKE "image/%" AND
  INTEGER(JSON_EXTRACT(payload, '$._bytesIn')) > 90000 AND
  INTEGER(JSON_EXTRACT(payload, '$._bytesIn')) < 110000 AND
  RTRIM(LTRIM(JSON_EXTRACT(payload, '$._cdn_provider'),"\""),"\"") = "Cloudflare"


Tracks issues / notes for HTTP/2 prioritization across browsers, CDNs and servers








No releases published