1. Home
  2. Glossary
  3. HTTP/2 and HTTP/3
Server/HTTP

HTTP/2 and HTTP/3

Newer versions of the protocol browsers use to talk to servers. HTTP/2 sends many requests over one connection. HTTP/3 runs over QUIC (UDP) and recovers faster from packet loss. Both need HTTPS in browsers.

Why it matters

Newer protocol versions handle many files at once and recover from packet loss better, which helps pages with many resources. Most CDNs and modern servers support them.

Where you will see it

The free Compression & caching checker looks at this on a live page and explains what it finds in plain English: test Brotli and gzip compression, browser caching and HTTP/2 or HTTP/3, with server config fixes.

Related terms

  • TLS: Transport Layer Security, the protocol that encrypts the connection between browser and server.
  • CDN: A network of servers in many locations that keeps copies of your files and serves each visitor from a nearby one.
  • Gzip: A widely supported compression format for text responses.

Go deeper

  • Compression & caching: How gzip and Brotli compression and HTTP caching work, which settings to use for HTML, CSS, JavaScript and images, and how to turn them on in Nginx and Apache.

← All 66 glossary terms

↑ ↓ to moveEnter to openEsc to closeAll results