Enable Gzip Compression for Faster HTML (Test and Fix Guide)

What Gzip Compression Does to Your HTML

Gzip is a compression format that wraps the DEFLATE method (RFC 1951) inside a small container (RFC 1952). Text compression works because markup repeats itself constantly, and zlib, the library behind most implementations, does the heavy lifting. Tag names, class names, keywords and runs of indentation get swapped for short back references, and the browser reverses the swap without losing a single character.

The two sides settle on a coding through content negotiation. The browser sends an Accept-Encoding request header, one of the request headers every page load carries, listing the codings it can unpack. The server picks one, compresses the body and answers with a Content-Encoding header naming its choice. The rules for this exchange live in RFC 9110, and the MDN guide to HTTP compression explains the flow with examples.

Compressed responses should also carry Vary: Accept-Encoding. That header tells shared caches, including a CDN, to keep one copy per coding so a client that cannot read gzip never receives a gzipped body. Apache adds it for you in the normal case, while Nginx needs gzip_vary on.

Gzip belongs on text types: HTML, CSS, JavaScript, JSON, SVG and XML. Images, video, PDF files and WOFF2 fonts are already compressed, so running gzip over them burns CPU and saves almost nothing.

Minification is a different job. It edits the file at build time by removing whitespace and comments, while gzip works on the wire, so the two stack. Run your markup through the free HTML Minifier first and let the server compress the result. Brotli (RFC 7932) and Zstandard (RFC 8878) are newer codings that do the same wire job, and a later section compares them with gzip.

Why Enabling Gzip Compression Matters for Speed and SEO

We measured real files rather than quoting a generic percentage. The gzip figures use level 6, and the last row shows minifying first and compressing second.

Smaller HTML saves bandwidth for you and arrives sooner for every visitor, so the browser discovers your stylesheets, scripts and images sooner and can start fetching them sooner. That helps First Contentful Paint and Largest Contentful Paint, and it saves mobile data for visitors on slow connections. Total weight is a wider topic that our page size guide covers, so this page sticks to the transfer saving.

Compression is not a ranking signal by itself. It helps indirectly, through faster loading, and the background is in our write-up on page speed and SEO. Crawlers are not a concern either: Google Search Central documents gzip, deflate and Brotli as encodings Googlebot accepts, so compressed pages are safe to crawl.

One more reference point: Lighthouse and PageSpeed Insights flag text responses that arrive uncompressed (the classic audit skipped anything under about 1.4 KiB or with savings under 10 percent). Our row has no such thresholds, which the next section spells out.

How SEO Site Checker Tests Gzip Compression

The check is narrow. It looks at one header on one response and answers Passed or Failed, with no Warning state.

The exact rule: our report reads the Content-Encoding header of the main HTML document, lowercases it and compares it with the single value gzip. Equal means Passed. Anything else means Failed.

A Failed row is a request for a closer look, not a verdict on your hosting. The red How to Fix button opens the short steps that also appear lower on this page, and a Passed row adds one to the passed total in the report summary.

What the report reads

Our scanner opens your URL in headless Chromium, waits for the page to finish loading and takes the response for the main document, after any redirects. From that response it reads the Content-Encoding header, lowercases the value and compares it with gzip. Nothing else about the response is judged, and no before and after size comparison is made.

What Passed and Failed mean

Passed means the header says gzip, in any letter case. Failed means the header is absent or names a different coding. The savings percentage that appears in the Failed message is a typical estimate, not a measurement of your page. Our own tests gave about 81 percent for the home page HTML and about 71 percent for unminified jQuery, so the real number depends entirely on your markup.

Why a compressed site can still show Failed

Chromium advertises gzip, deflate, br and zstd when it talks to an HTTPS site. Servers and CDNs that prefer Brotli or Zstandard will answer with br or zstd, and our row reads both as not gzip. In our own spot check of 25 well known sites, 8 of the 20 that loaded a normal page answered with br.

So if DevTools or curl shows br or zstd, your compression is working and the red row is a limit of this check. Do not downgrade a healthy Brotli setup just to turn the row green. The check steps below show how to read the header yourself.

What this check leaves out

Only the HTML document is examined, so CSS, JavaScript, JSON and SVG files can be uncompressed while the row still says Passed. Compression level, the Vary header and BREACH exposure are not tested either, and the check steps below show how to read the Vary header and the level by hand.

Run the free report on my site

How to Check If Gzip Compression Is Enabled

Two checks need no extra tools, and the free report gives you a third. Run one of them before you change anything.

1. Use Chrome DevTools. Open the Chrome DevTools Network tab, reload the page and click the first request, which is the HTML document. Under Response Headers look for content-encoding, and compare the two numbers in the Size column, where the transferred size should be well below the resource size.
2. Use curl. Send a request with an Accept-Encoding header that advertises gzip and print only the response headers, using the first command below. Then run the second command, which advertises br, to see whether Brotli is switched on as well.
3. Read the answer. A content-encoding of gzip means compression is on. A value of br or zstd means it is on with another coding, and no header means it is off or the file type is missing from the compress list. Because the first command only advertises gzip, it will show gzip or nothing, never br.
4. Look for the Vary header. The same response should include vary: accept-encoding, so caches store a separate copy for each coding.
5. Run the free report. Our scanner shows the row exactly as it sees your page, which helps when a CDN or firewall treats it differently from your browser.

curl -s -o /dev/null -D - -H "Accept-Encoding: gzip" https://example.com/

In the output, find the line content-encoding: gzip. Header names are case-insensitive, and the capitalization depends on the HTTP version: HTTP/2 and HTTP/3 always show lowercase names, while an HTTP/1.1 server usually sends Content-Encoding with capitals. If the response shows only a status line and a few ordinary headers, the server is sending the page at full size.

curl -s -o /dev/null -D - -H "Accept-Encoding: br" https://example.com/

A content-encoding: br line here means Brotli is already on, which is a healthy result.

How to Enable Gzip Compression on Apache and Nginx

The rule is the same on both servers. Compress text types only, keep the configuration in one place, reload the server and test again. The same files also control HTTP/2, which our HTTP/2 setup guide covers without repeating this page.

Enable gzip on Apache with mod_deflate

First confirm that mod_deflate is loaded. On Debian family systems, a2enmod deflate followed by a reload does it. Then put the block below in the virtual host, or use the .htaccess gzip route if you have no access to the main config, and keep the file type list short. Apache's own Apache mod_deflate documentation lists every directive and the notes on Vary and BREACH.

<IfModule mod_deflate.c>
  AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css
  AddOutputFilterByType DEFLATE text/javascript application/javascript
  AddOutputFilterByType DEFLATE application/json application/xml image/svg+xml
</IfModule>

The module is called mod_deflate, yet the header it sends says gzip. That mismatch catches people out, because they look for the word deflate in the response and conclude the filter is not working.

Enable gzip on Nginx

Place the directives in the http block, or in a server block if you only want them for one site. The Nginx gzip module reference documents each one and its default.

gzip on;
gzip_comp_level 5;
gzip_min_length 256;
gzip_vary on;
gzip_proxied any;
gzip_types text/plain text/css text/xml text/javascript application/javascript application/json application/xml image/svg+xml;

Nginx compresses text/html on its own once gzip is on, so you do not list it. By default gzip is off, the level is 1 and the minimum length is 20 bytes. Each line does one job:

• gzip on turns the module on for the chosen context.
• gzip_comp_level 5 picks a middle compression level that balances size and CPU.
• gzip_min_length 256 skips tiny responses where the gzip wrapper would not pay for itself.
• gzip_vary on adds Vary: Accept-Encoding so shared caches stay correct.
• gzip_proxied any also compresses responses to requests that carry a Via header, which is how a proxy or CDN in front of your server identifies itself.
• gzip_types lists the extra MIME types to compress beyond HTML.

Choose a sensible compression level

We gzipped jQuery 3.7.1 at three levels. Level 1 produced about 102 KB, level 6 about 84 KB and level 9 about 83.6 KB, rounded because gzip builds differ by under one percent. Levels 5 and 6 capture almost all of the gain, while the jump to 9 saves only a few hundred bytes and costs noticeably more CPU.

Reload and test again

Check the syntax with nginx -t or apachectl configtest, reload the server, then run the curl command again and read the content-encoding line.

Enable Gzip Compression in WordPress, cPanel and Other Platforms

Many hosts already compress, so read the header before touching anything. If it is missing, find your platform in the table. Behind a CDN, remember that compression can happen at the edge, a topic our CDN usage test page owns.

For WordPress gzip compression, test first, then ask the host, then edit .htaccess. A plugin that compresses while the server also compresses is the classic double compression trap, covered below.

Gzip vs Brotli: Which Compression Should You Enable?

Gzip is the universal baseline, Brotli usually makes text smaller and Zstandard is the newest of the three. The browser lists the codings it understands in Accept-Encoding and the server answers with the best one it has, so a server that offers both Brotli and gzip serves each visitor the smaller format their browser accepts.

Apache has had mod_brotli since version 2.4.26, and it takes the same kind of type list, for example AddOutputFilterByType BROTLI_COMPRESS text/html text/css application/javascript. Nginx open source ships without Brotli, so it needs the third-party ngx_brotli module.

The other route is a CDN, and many switch Brotli on by themselves. Cloudflare compression, for example, is applied at the edge without any change on your origin. Brotli's highest levels cost a lot of CPU, so the usual way to get them is precompression: the server stores a .br or .gz copy next to each static asset and serves it, with no compression bill on every request.

Our advice is to keep gzip as the safe baseline and add Brotli where your stack supports it, because visitors get the smaller file and older clients still get gzip. Today our row accepts gzip only, so a br answer shows Failed even though Brotli is good practice (see the explanation above).

Common Gzip Compression Mistakes to Avoid

Most failed setups come from a short list of slips, so check these before blaming the server.

• Compressing files that are already compressed. JPEG, PNG, WebP, MP4, WOFF2 and ZIP files gain nothing from gzip, so use the Image Compressor to shrink pictures instead.
• Leaving out JSON, SVG or XML. If the type list stops at HTML and CSS, API responses and vector graphics still travel at full size.
• Running level 9 on dynamic pages. The extra CPU buys a handful of bytes and can slow Time to First Byte.
• Skipping Vary: Accept-Encoding. Without it a cache can hand a compressed copy to a client that cannot read it.

Double compression: if both the application and the server compress, or both the origin and the CDN do, the browser can fail with ERR_CONTENT_DECODING_FAILED. Compress in one layer only.

BREACH caution: compressed HTTPS responses that mix a secret token with text an attacker can influence can leak that token. Masking or rotating tokens per request is the usual defence.