Readiness check · Accelerate lane · weight 4
HTTP/3 advertised
The homepage response advertises h3 in its Alt-Svc header.
- Observed on
- 37%
- Top 1K sites
- 40%
- Top 1M band
- 39%
- Not measured
- 11,311
of 28,784 measured sites
286 measured
4,672 measured
blocked, challenged or not applicable
Why it matters
HTTP/3 runs over QUIC, which copes better with lossy mobile networks and recovers faster when a connection changes.
How to fix it
Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
How we check
The homepage response advertises h3 in its Alt-Svc header.
Observed: HTTP/3 advertised.
Not observed: HTTP/3 not advertised.
Limit: Read from the homepage response only; other pages or regions may send different headers.
Stack-specific steps
- Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.
- Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.
By popularity band
| Chrome UX Report band | Observed | Measured |
|---|---|---|
| Top 1K | 40% | 286 |
| Top 5K | 33% | 1,308 |
| Top 10K | 35% | 1,648 |
| Top 50K | 36% | 12,853 |
| Top 100K | 37% | 3,896 |
| Top 500K | 38% | 4,121 |
| Top 1M | 39% | 4,672 |
Categories most likely to do this
Categories least likely
By stack
- Shopify94%
- WordPress on Cloudflare80%
- Next.js on Google edge76%
- Nuxt on Cloudflare63%
- Webflow61%
- Next.js on Cloudflare59%
- Astro49%
- Nuxt on Amazon CloudFront45%
- WordPress44%
- Drupal on Cloudflare43%
- Nuxt36%
- PrestaShop35%
- Next.js35%
- Next.js on Amazon CloudFront34%
- Magento / Adobe Commerce34%
- Adobe Experience Manager on Amazon CloudFront31%
- WordPress on Amazon CloudFront30%
- Next.js on Akamai30%
- Next.js on Fastly30%
- Angular28%
- Blogger26%
- Adobe Experience Manager24%
- Drupal20%
- Next.js on Vercel18%
- Sitecore12%
By provider
- Cloudflare74%
- Google edge73%
- Amazon CloudFront32%
- Fastly29%
- Vercel19%
- Akamai18%
- Azure Front Door/CDN3.6%
- Imperva<1%