How to Fix: HTTP/2 enabled

HTTP/2 enabled is an important SEO check in the Technical Foundation category. This is a medium-priority issue. While not urgent, fixing it will improve your overall SEO health.

What is This Check About?

This check verifies that your server delivers pages over HTTP/2 (or HTTP/3) rather than the ageing HTTP/1.1. HTTP/2 is a fundamental upgrade to how a browser and server talk: it multiplexes many requests over a single connection, compresses headers, and lets the server work more efficiently — which shows up directly as faster page loads, especially on asset-heavy WordPress sites. When this check fails, your site is still speaking a protocol designed for a very different web, and every extra image, script, and stylesheet is paying a tax it no longer needs to.

The reassuring part: this is usually a server or host setting, not a code change. On a decent modern host it is often already on, or one toggle away. That is why it is medium-priority rather than a project — high value, low effort, when the host cooperates.

Why Does This Matter for SEO?

Search engines evaluate hundreds of factors when ranking websites. HTTP/2 helps indirectly but genuinely because:

• Faster load times feed Core Web Vitals, which are confirmed ranking signals — HTTP/2 improves how quickly all your assets arrive
• Multiplexing removes the old “too many requests block each other” bottleneck that hurt image- and script-heavy pages most
• Header compression and a single persistent connection cut overhead, which matters most on mobile and higher-latency networks
• It is table stakes for a modern technical foundation — most quality hosts and CDNs already run HTTP/2 or HTTP/3, and being behind flags an ageing setup

How to Check This Issue

You can identify this issue by:

1. Running an SEO audit using the SEO Roadmap tool to flag the protocol your server is using
2. Opening your browser’s DevTools Network panel, loading your site, and adding the “Protocol” column — h2 means HTTP/2, h3 means HTTP/3, http/1.1 means you are on the old one
3. Using an online HTTP/2 test tool by entering your domain
4. Confirming your site is served over HTTPS first — HTTP/2 in browsers requires a valid SSL certificate

How to Fix This in WordPress

Difficulty Level: EASY – This fix is straightforward and can typically be completed by anyone with basic WordPress knowledge.

Estimated Time: 10 min

Follow these steps to fix this issue:

Step 1: Confirm the Current State

Run the SEO Roadmap audit and the DevTools protocol check together so you know exactly what you are on. If you are already on h2 or h3, this check is a pass and you can move on. If you are on http/1.1, note whether you have HTTPS active, since that is a prerequisite.

Step 2: Access the Right Settings

Unlike most checks in this series, the fix lives at the server layer, not inside WordPress:

• Your hosting control panel — many hosts expose an HTTP/2 (or HTTP/3) toggle, or enable it by default on supported plans
• Your SSL settings — ensure a valid certificate is installed and the whole site is served over HTTPS
• Your CDN (Cloudflare and most CDNs serve HTTP/2 and HTTP/3 automatically) — putting a CDN in front is often the fastest route if your origin host is behind

Step 3: Enable It

If your host offers a toggle, enable HTTP/2 (and HTTP/3 if available) and confirm HTTPS is enforced site-wide. If your host does not support it, you have two clean options: put a modern CDN in front of the site, or move to a host that runs current server software — a host still stuck on HTTP/1.1 in this era is telling you something about the rest of its stack. There is nothing to change inside WordPress itself.

Step 4: Verify the Fix

After making changes:

1. Clear your WordPress and CDN caches, then hard-refresh
2. Recheck the Protocol column in DevTools and confirm requests now report h2 or h3
3. Re-run the SEO Roadmap audit and re-test page speed to confirm the improvement carried through

Don’t over-optimise for a protocol that changed the rules

Here is a subtlety worth knowing, because it changes advice you may have read years ago. Under HTTP/1.1, a whole cottage industry of “optimisations” existed to work around the protocol’s one-request-at-a-time bottleneck: concatenating every stylesheet into one giant file, spriting images together, sharding assets across multiple domains. HTTP/2 makes several of those tricks pointless — and a couple of them actively counterproductive, because multiplexing already solves the problem they were compensating for, and domain sharding fights against the single-connection efficiency HTTP/2 is built on.

So my recommendation is twofold. First, enabling HTTP/2 is close to a free win — do it. Second, once you are on it, revisit any aggressive concatenation or sharding your optimisation plugin is doing and test whether it still helps; on HTTP/2 it may be neutral or worse. This is the boring truth of a technical foundation: the goal is not to pile on every optimisation you have ever heard of, but to match your setup to how the current stack actually behaves. Turn the protocol on, then let it do the job the old workarounds used to fake.

Recommended Tools & Plugins

These tools can help you fix and prevent this issue:

• Yoast SEO – Comprehensive SEO plugin to keep your on-page fundamentals strong on the faster foundation
• Rank Math – Feature-rich SEO plugin with detailed analysis
• Google Search Console – Free tool to watch Core Web Vitals improve as load times drop
• SEO Roadmap – Complete SEO audit and action plan tool

Common Mistakes to Avoid

• Assuming HTTP/2 is on without checking the actual protocol in DevTools
• Trying to enable HTTP/2 without a valid SSL certificate, which browsers require
• Keeping HTTP/1.1-era hacks like domain sharding that now work against HTTP/2
• Staying on a host that cannot offer HTTP/2 instead of adding a CDN or moving

Need More Help?

If you’re still having trouble fixing this issue, consider:

• Asking your hosting support directly whether HTTP/2 or HTTP/3 is available on your plan and how to enable it
• Adding a CDN such as Cloudflare, which serves modern protocols in front of your origin
• Reviewing your host and CDN documentation on protocol and SSL configuration
• Running a complete site audit with SEO Roadmap for a prioritized action plan

This guide is part of the SEO Roadmap knowledge base – your complete resource for WordPress SEO optimization.