Readiness check · Accelerate lane · weight 7
HTTP/2 negotiated
The TLS handshake selects h2 via ALPN.
- Observed on
- 90%
- Top 1K sites
- 94%
- Top 1M band
- 89%
- Not measured
- 865
of 39,230 measured sites
469 measured
5,471 measured
blocked, challenged or not applicable
Why it matters
HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.
How to fix it
Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
How we check
The TLS handshake selects h2 via ALPN.
Observed: HTTP/2 negotiated.
Not observed: Server stayed on HTTP/1.1.
Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Stack-specific steps
- Nginx: Enable http2 on the TLS listener.
- Amazon CloudFront: Choose HTTP/2 (or HTTP/2 and HTTP/3) as supported versions on the distribution.
By popularity band
| Chrome UX Report band | Observed | Measured |
|---|---|---|
| Top 1K | 94% | 469 |
| Top 5K | 93% | 2,093 |
| Top 10K | 92% | 2,481 |
| Top 50K | 90% | 18,312 |
| Top 100K | 90% | 5,152 |
| Top 500K | 89% | 5,252 |
| Top 1M | 89% | 5,471 |
Categories most likely to do this
By stack
- Shopify>99%
- WordPress on Cloudflare>99%
- Nuxt on Cloudflare>99%
- Next.js on Cloudflare>99%
- Next.js on Vercel>99%
- Next.js on Fastly>99%
- Magento / Adobe Commerce99%
- Drupal on Cloudflare99%
- Next.js on Amazon CloudFront99%
- WordPress on Amazon CloudFront98%
- Nuxt on Amazon CloudFront97%
- Next.js on Google edge97%
- Adobe Experience Manager on Amazon CloudFront97%
- Next.js on Akamai96%
- Webflow96%
- Next.js95%
- Blogger95%
- Astro95%
- PrestaShop93%
- WordPress93%
- Nuxt92%
- Adobe Experience Manager90%
- Angular89%
- Sitecore86%
- Drupal84%
By provider
- Vercel>99%
- Cloudflare>99%
- Fastly>99%
- Google edge98%
- Azure Front Door/CDN98%
- Amazon CloudFront98%
- Akamai95%
- Imperva88%