Updated

Technology · Other

HTTP/3

httpwg.org

What is HTTP/3?

HTTP/3 is a major revision of the HTTP network protocol that runs over QUIC instead of TCP. It is defined as an Internet standard.[1][2]

HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.

HTTP/3 belongs toMiscellaneouscategory.

Version of

The HTTP protocol, succeeding HTTP/2[1]

Transport

QUIC over UDP instead of TCP[1]

Effect

Lower latency and no HTTP head-of-line blocking[1]

Encryption

QUIC includes TLS 1.3[2]

852websites

use it — 33.6% of the 2,539 websites we scanned in the last 12 months

#3of 35

tools in its category seen in our scans (we recognize 140)

312public pages

on UptimeCard — open any of them to see how that site is doing

In short: a newer transport for HTTP that runs over QUIC to reduce latency.[1]

35.5% of all websites we track run HTTP/3

What is HTTP/3 used for?

In short, from the websites we scan

Faster connection setup
QUIC offers lower connection setup latency than running TLS over TCP.[2]
Avoiding head-of-line blocking
A lost packet no longer holds up unrelated requests on the same connection.[1]
What it does
HTTP/3 is one of the miscellaneous tools websites use. In our scans it is #3 of the 35 we see.
On real websites
Among 60 public websites we scan that use it: speeding up page loads (55 sites), encrypting connections (9 sites), reducing connection latency (6 sites), transporting video and audio (2 sites). Counted automatically from a short description of each site (one site can do several jobs), so read it as an estimate.
Used together with
It is often installed next to Cloudflare, Cloudflare Bot Management, jsDelivr.

Should you use HTTP/3?

The 10-second version, from the vendor’s own pages and what we see in our scans

HTTP/3 fits if…

  • Your pages load many resources and you want lower latency[1]
Networks that block or throttle UDP cannot carry this protocol[1]

HTTP/3 next to HTTP/2

Both carry HTTP semantics. Wording comes from the defining RFCs.

HTTP/3HTTP/2
What the specifications say
Defined inRFC 9114published in June 2022[4]RFC 7540published in May 2015[3]
Carried overQUICa mapping of HTTP semantics over QUIC[4]The abstract does not name the transport
Connection setupLow latencylow-latency connection establishment[4]Reduced latencythrough header compression and concurrent exchanges[3]
StreamsQUIC streamsstream multiplexing and per-stream flow control[4]Concurrent exchangeson the same connection[3]
What we see in our scans
Websites running it85233.6% of 2,539 scanned sites0too few to compare
  • HTTP/2: The previous HTTP version, still widely used, that runs over TCP with multiplexed streams[3]

Choose HTTP/3 if…

  • You want streams and low-latency connection setup from QUIC[4]

Choose HTTP/2 if…

  • You want the HTTP version with header compression and concurrent exchanges that predates QUIC[3]

Support and help for HTTP/3

How the vendor says you can reach it, and the public help community

Stack Overflow

109 questions[7][8]

59% have an upvoted answer. [http3] questions

How HTTP/3 sites protect themselves

Share of the 852 sites we scanned that run each protection

HSTS64% · 549 sites

HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS

Cloudflare Bot Management23% · 199 sites

Cloudflare bot management solution identifies and mitigates automated traffic to protect websites from bad bots

reCAPTCHA18% · 156 sites

reCAPTCHA is a free service from Google that helps protect websites from spam and abuse

Protections add up, they do not replace each other: a site can run all of them.

What sites use HTTP/3 for

An estimate from UptimeCard's technology map of 267 public sites

Runs the whole site259 sites

abeta.co.uk · accredible.com · accurx.com

Hosts help, docs or support content6 sites

digipost.no · discordstatus.com · expo.dev

Publishes a blog or resources1 sites

appfigures.com

Runs a shop or catalog1 sites

peachpayments.com

Rough guide, not a measurement: each description is written automatically from the site’s technology stack and the site has not confirmed it. A site is counted once, in the first group its description fits (shop, help and docs, blog, marketing site; otherwise the whole site). Descriptions that only guess (“likely”, “may”) are left out.

At a glance

UptimeCard's own scans and tests of 2,539 websites · refreshed weekly

How HTTP/3 sites scoreout of 100 · hover or tap a score for details

52PerformanceLowaverage site: 5191AccessibilityGoodaverage site: 9196Best practicesGoodaverage site: 9692SEOGoodaverage site: 92

Page load time

Loads about as fast as the average site

HTTP/3 sites
3.5 s
All sites
3.5 s

Most HTTP/3 sites load in 2.5–5.3 s. Home page weight: 3.3 MB vs 3.4 MB for all sites. 305 public sites measured.

Where are they hosted?

Mostly Cloudflare and Amazon Web Services

  • Cloudflare48%
  • Amazon Web Services18%
  • Google Cloud7%
  • Fastly2%
  • Other25%
United States 55%Canada 24%Netherlands 4%

Who uses it?

Technology and Software is the biggest group

Technology and Software57%
Business Services13%
Software as a Service (SaaS)7%
Educational Resources4%

Share of 312 classified public sites. “× average” compares with all 961 public sites.

Usually installed alongside

The bigger the bubble, the more of the 852 HTTP/3 sites also run the tool. Colour shows what the tool does. Hover or tap a bubble for details.

Google Tag Manager56%Google Analytics55%Linkedin Insight Tag18%Facebook Pixel18%HubSpot15%OneTrust14%Microsoft Advertising12%DoubleClick Floodlight11%Yoast SEO10%Webflow10%
Tag managerAnalyticsMarketingCookie consentAdvertisingSearch visibilityPage builder

Similar tools in its category

Miscellaneous: 140 tools known, 35 seen in our scans

How websites combine HTTP/3 with other tools

Relationships found on the websites that use it, from the same map status pages show.

Built on a platform 110Complements another tool 47Integrates with another 44Needs another tool 16

Websites using HTTP/3

852 websites use HTTP/3: 33.6% of the 2,539 websites we scanned in the last 12 months. A selection is shown below.

Scores are out of 100: P Performance · A Accessibility · B Best practices · S SEO. Green 80+, yellow 65–79, orange 50–64, red below 50. The dot shows whether our last scan found the site failing (red) or not (green); Red, amber or blue: an active incident on the site's status page (outage, degraded, maintenance) or a failing scan; amber also means a certificate ending within 30 days. Hover the dot for details.

Who is behind HTTP/3

From its own pages and public records, with sources

Developed by

Internet Engineering Task Force[2]

Its story

  1. 2015

    RFC 7540 defined HTTP/2, introducing header field compression and multiple concurrent exchanges on one connection.[3]

  2. 2021

    RFC 9000 defined QUIC, a UDP-based multiplexed and secure transport with streams, low-latency connection setup and path migration.[5]

  3. 2022

    RFC 9114 defined HTTP/3 as a mapping of HTTP semantics over QUIC and described how HTTP/2 extensions can be ported.[4]

Questions about HTTP/3

What is HTTP/3?
HTTP/3 is a major revision of the HTTP network protocol that runs over QUIC instead of TCP. It is defined as an Internet standard.
What is HTTP/3 used for?
QUIC offers lower connection setup latency than running TLS over TCP. A lost packet no longer holds up unrelated requests on the same connection. HTTP/3 is one of the miscellaneous tools websites use. In our scans it is #3 of the 35 we see. Among 60 public websites we scan that use it: speeding up page loads (55 sites), encrypting connections (9 sites), reducing connection latency (6 sites), transporting video and audio (2 sites). Counted automatically from a short description of each site (one site can do several jobs), so read it as an estimate. It is often installed next to Cloudflare, Cloudflare Bot Management, jsDelivr.
What carries HTTP/3?
QUIC, which runs over UDP.[1]
Is HTTP/3 encrypted?
Yes. QUIC builds in TLS 1.3.[2]
What is QUIC?
A UDP-based, multiplexed and secure transport protocol that provides flow-controlled streams, low-latency connection setup and network path migration.[5]
Which RFC defines HTTP/3?
RFC 9114, published in June 2022.[4]
What happened to HTTP/2 features?
RFC 9114 identifies HTTP/2 features that QUIC subsumes and describes how HTTP/2 extensions can be ported.[4]
Who developed QUIC?
The IETF QUIC Working Group produced QUIC version 1, published as RFC 9000.[5][6]
How many websites use HTTP/3?
We found HTTP/3 on 852 of the 2,539 websites we scanned in the last 12 months (33.6%). 312 of them have a public status page.
What are the alternatives to HTTP/3?
Other miscellaneous tools we recognize include Open Graph, Webpack, Module Federation, PWA.

Is your website built with HTTP/3?

Create a free status page that shows your visitors your site is up. It also gives your site its own public page where new people can discover it.

Example status page card