Skip to content

HTTP/2 test:Is your site using HTTP/2 and HTTP/3?

See which protocol your server picks, whether HTTP/3 is advertised, and which files on the page, yours or third-party, still load over HTTP/1.1.

  • Free, no account
  • Results in under a minute
  • Every file on the page, by protocol
Example result

example-shop.hr

WordPress 6.8

Sample shop · homepage · mobile Chrome · the same check you get for your own site

Run it on your site
Best practices

1 passed · 1 failed · 2 warnings. Biggest issue: The site is served over HTTP, not HTTPS.

Detected technology

  • WordPress 6.8
  • WooCommerce
  • Elementor
  • jQuery 1.12.4
  • LiteSpeed

Protocol

Negotiated protocols and TLS details
HTTP/2 (ALPN)not tested (plain http)
HTTP/3 (Alt-Svc)not advertised
Alt-Svc header—
TLS—
Responses by protocol (Chromium)http/1.1: 15

What we found

1 failed2 warnings1 to note1 passed
Show 1 passed checks

Fix these first

From the example above. Check your own site to get the fixes that apply to it.

  1. Problem: The site is served over HTTP, not HTTPS

    Browsers label HTTP pages "Not secure" and Google ranks HTTPS pages higher.

    How to fix it: Get a certificate (Let's Encrypt is free) and enable HTTPS on your host.

  2. Warning: 11 text files are sent uncompressed

    HTML, CSS and JavaScript shrink 3–5× with gzip or Brotli.

    How to fix it: Enable Brotli (or gzip) for text types in your server, hosting panel or CDN; Cloudflare and most hosts have it as one switch.

  3. Warning: 15 requests still use HTTP/1.1

    HTTP/2 and HTTP/3 load many files over one connection at once; HTTP/1.1 queues them six at a time.

    How to fix it: Turn on HTTP/2 or HTTP/3 in your hosting or CDN panel; on Cloudflare and most managed hosts it is a checkbox.

What this tool checks

Protocol, compression, caching and CDN checks, because they are usually set in the same place.

  • HTTP/2 server support

    Checks your server offers HTTP/2, a setting that makes pages with many files load faster.

  • HTTP/3 advertised

    Checks your server announces HTTP/3, which connects faster and copes better with flaky mobile networks.

  • HTTP/2 or HTTP/3 requests

    Finds requests still on HTTP/1.1, which loads files slowly in small batches instead of all at once.

  • Text compression

    Checks HTML, CSS and JavaScript are compressed with Brotli or gzip, saving visitors data and time.

  • Cache lifetime for static files

    Checks images, CSS and scripts can be cached, so returning visitors do not download them again.

  • CDN in front of the site

    Checks for a CDN, which serves files from near each visitor and absorbs traffic spikes.

  • Minimum TLS version

    Checks the server refuses old TLS 1.0 and 1.1, which attackers can use to weaken a connection.

  • HTTPS connection

    Checks the site is served over HTTPS, so browsers don't label it "Not secure" and visits stay private.

Show 4 more checks

  • Cache lifetime for static files

    Checks images, CSS and scripts can be cached, so returning visitors do not download them again.

  • CDN in front of the site

    Checks for a CDN, which serves files from near each visitor and absorbs traffic spikes.

  • Minimum TLS version

    Checks the server refuses old TLS 1.0 and 1.1, which attackers can use to weaken a connection.

  • HTTPS connection

    Checks the site is served over HTTPS, so browsers don't label it "Not secure" and visits stay private.

How it works

  1. Run a TLS handshake

    We connect with ALPN offering h2 and http/1.1 and record the protocol the server picks, with the TLS version and cipher.

  2. Read Alt-Svc

    The Alt-Svc header of the page response tells whether HTTP/3 is advertised for the next visit.

  3. Load every file

    The page is loaded in Chromium and every response is grouped by protocol (h3, h2, http/1.1), so you also see third-party files still on HTTP/1.1.

We report the first-visit handshake. A browser that has seen the Alt-Svc header before can switch to HTTP/3 on its next visit, which the handshake alone does not show.

Questions

Is this really free?

Yes. getReport is funded by donations, not plans. This tool runs the full report and shows you the part it is about; the complete report with all seven modules is one click away, also free.

The test says HTTP/2 but my browser shows h3. Which is right?

Both. ALPN is negotiated once per connection; a browser that has seen the Alt-Svc header before switches to HTTP/3 on the next visit. The tool reports the first-visit handshake and whether HTTP/3 is advertised.

Does HTTP/2 need HTTPS?

In every browser, yes. Plain http:// pages are stuck on HTTP/1.1, which is one more reason to redirect them.

Do you store my results?

The report is kept for 12 months at its shareable link so you can come back to it. Reports are not listed publicly and carry a noindex tag; nothing about your visitors is collected.

Why do HTTP/2 and HTTP/3 matter?

HTTP/1.1 opens up to six connections per host and queues everything else, so a page with 80 files waits in line. HTTP/2 sends them all over one connection at once, and HTTP/3 removes the slow handshake and copes better with packet loss on mobile networks. On most hosts and every major CDN this is a single setting, one of the cheapest speed wins there is. The catch is third-party scripts and image hosts that still answer over HTTP/1.1; the per-file table shows them.

Related free tools

All 41 tools →

Free, funded by the people who use it

€0 of €75 this month. At €75, site crawl up to 500 pages + weekly re-check switches on for everyone.

Chip in