How to Fix: GZIP/Brotli enabled

GZIP/Brotli enabled is an SEO check in the Technical Foundation category, and it is a high-priority issue for a good reason: it is one of the highest return-on-effort fixes on the whole web. Ten minutes of work can shave a large fraction off the bytes every visitor downloads, on every page. If this check is failing, fix it before almost anything else on your technical list.

What this check is actually about

GZIP and Brotli are compression methods your server uses to shrink text-based files — HTML, CSS, JavaScript, SVG — before sending them to the browser, which then unpacks them. Because these files are highly compressible, the savings are dramatic, often well over half the transfer size. Brotli is the newer method and generally compresses a little tighter than GZIP; both are widely supported. This check verifies that one of them is actually switched on.

When it fails, your server is shipping full-size, uncompressed text over the wire — paying for bandwidth and load time you do not need to spend.

Why an old dinosaur takes bytes seriously

I have a reflex about wasted bytes that comes from learning this craft when bytes were genuinely scarce. My first machine was a Mac Plus with a whole megabyte of RAM, and the work I did later shipped over dial-up modems where every kilobyte cost the user real seconds of their life watching a progress bar. You did not “optimize later.” You budgeted space and weight from the first decision, because there was no bandwidth to bail you out. Squeezing an asset as small as it would go without visibly breaking was a daily discipline, not an afterthought.

Modern connections hid that discipline, and a lot of the web got flabby as a result. But compression is the one place where the old habit still pays off effortlessly — the server does the squeezing for you, automatically, for free, on every request. When I see GZIP or Brotli switched off, it reads to me the way leaving the lights on in an empty room reads to someone who grew up counting the meter. There is no reason to pay for bytes you do not have to send.

Why it matters for SEO

• Smaller transfers mean faster loads, which feed Core Web Vitals and the page-experience signals
• Speed is a direct ranking factor and a strong influence on conversions and bounce
• Mobile and slower-connection users benefit the most, and Google indexes mobile-first
• It reduces your bandwidth costs at the same time — a rare win with no trade-off

How to check where you stand

1. Open your browser dev tools (F12), load the site, and check the Content-Encoding response header — it should read gzip or br
2. Run the site through PageSpeed Insights or GTmetrix, which flag missing text compression directly
3. Use an online “GZIP/Brotli test” tool for a quick yes/no on your main URL
4. Confirm compression is applied to HTML, CSS, and JavaScript, not just some file types

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

Step 1: Check with your host first

Many quality hosts enable Brotli or GZIP at the server level already. Ask support or check your hosting panel — if it is on server-side, you may simply need to confirm it and move on. This is the fastest path and the one I try first.

Step 2: Enable it via a caching plugin or config

• Caching plugins such as WP Rocket or W3 Total Cache can turn on compression with a checkbox
• On Apache, GZIP can be enabled with mod_deflate rules in .htaccess
• On Nginx or LiteSpeed, it is a server-config or LiteSpeed Cache setting rather than .htaccess

Step 3: Verify the header changed

1. Reload the site and confirm Content-Encoding now reports gzip or br
2. Re-run PageSpeed Insights to confirm the text-compression warning is gone
3. Re-run the SEO Roadmap audit to confirm the check passes

Recommended tools & plugins

• WP Rocket – Enables compression and caching with a simple toggle
• W3 Total Cache – Free caching plugin with GZIP compression controls
• Google PageSpeed Insights – Free tool to confirm text compression and measure the gain
• SEO Roadmap – Complete SEO audit and action plan tool

Common mistakes to avoid

• Adding .htaccess compression rules on an Nginx server, where they do nothing
• Enabling it in a plugin while the host already handles it, causing double configuration
• Compressing only some file types and leaving JavaScript or CSS uncompressed
• Assuming it is on without ever checking the Content-Encoding header

Need more help?

If the header still shows no compression after you have tried the plugin route, the answer is a one-line question to your host — it is almost always a server-level setting. A full SEO Roadmap audit will confirm this win landed and point you to the next technical-foundation item worth your ten minutes.

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