HTTP/2
Quick Definition
HTTP/2 is a major upgrade to the web protocol that makes websites load faster by allowing multiple files to download simultaneously over a single connection. Most WordPress hosts support it by default.
What Is HTTP/2?
HTTP/2 is the second major version of the Hypertext Transfer Protocol — the rules that govern how browsers and servers communicate. It was published in 2015 as a successor to HTTP/1.1 (which had been the standard since 1997) and is designed to make websites load significantly faster.
The key improvement is multiplexing: the ability to send multiple files simultaneously over a single connection. With HTTP/1.1, your browser opens separate connections for each file and can only process about 6 requests in parallel. With HTTP/2, dozens or hundreds of files — CSS, JavaScript, images — can all download at the same time over one connection.
HTTP/2 vs HTTP/1.1
| Feature | HTTP/1.1 | HTTP/2 |
|---|---|---|
| Connections | ~6 parallel connections | 1 multiplexed connection |
| Format | Text-based (human-readable) | Binary (faster to parse) |
| Headers | Sent in full with every request | Compressed (HPACK) |
| Server push | Not available | Server can proactively send files |
| Prioritization | No request prioritization | Streams can be prioritized |
The result: websites using HTTP/2 can load up to 20% faster than those on HTTP/1.1, depending on how many files the page loads. Sites with lots of small assets (typical WordPress sites with multiple plugins) benefit the most.
HTTP/2 and WordPress
The good news: you probably already have HTTP/2. Most modern WordPress hosting providers — including SiteGround, Hostinger, Kinsta, WP Engine, and Cloudways — enable HTTP/2 by default. If your site uses HTTPS (which it should), HTTP/2 is almost certainly active.
You can verify by:
- Visiting KeyCDN HTTP/2 Test and entering your domain
- Opening Chrome DevTools → Network tab → right-click the column headers → enable "Protocol" — look for "h2"
If you use Cloudflare as your CDN, HTTP/2 is automatically enabled for all traffic through their network, regardless of your origin server.
One important change: With HTTP/1.1, combining CSS and JavaScript files into fewer bundles (concatenation) was a best practice because fewer connections meant faster loading. With HTTP/2, this is no longer necessary — multiplexing handles many small files efficiently. Some older caching plugins still concatenate files by default, which can actually hurt performance on HTTP/2. If your host supports HTTP/2, consider disabling file concatenation in your caching plugin settings.
Why It Matters
HTTP/2 is a free performance upgrade that most WordPress sites already have but few site owners are aware of. It reduces latency, eliminates the need for some traditional speed hacks (like file concatenation and domain sharding), and makes your page speed better without any effort on your part. The key takeaway: make sure your site is on HTTPS, confirm your host supports HTTP/2, and disable file concatenation if your caching plugin has it enabled.
Sources: Cloudflare, Wikipedia, DebugBear