Toolsky

Free Online Tools & Utilities for Every Task.

GZIP Compression Test

Test if Gzip is working on your website.

Enter the complete URL of the website you want to test for GZIP compression.

You enabled compression in your hosting panel, added the plugin, saved the settings — but is anything actually being compressed? The GZIP Compression Test on ToolSky answers that in one step: give it a page URL and it fetches the page the way a browser would, then reports whether the server returned the content compressed with gzip or sent it uncompressed. No server login, no digging through terminal output — just a clear yes or no, with the response details behind it.

Gzip in Plain Terms: What Is Being Tested

Gzip is a compression method applied to web traffic on the fly. When a browser requests a page, it tells the server which compression formats it accepts. If the server supports gzip, it shrinks the response — mainly HTML, CSS, and JavaScript, which are text and compress extremely well — and marks it with a Content-Encoding: gzip response header. The browser then decompresses the body transparently and renders the page exactly as if it had arrived uncompressed. Nothing about the page's appearance changes; only the number of bytes crossing the network does, and for text-heavy pages that number often drops by more than half.

The test therefore looks at evidence in the response itself: whether the Content-Encoding header is present, and how the transferred size compares with the full size of the resource. If the header is missing, the server (or an intermediary such as a CDN or proxy) is not compressing, regardless of what a settings screen claims.

What the Test Checks

  • Any public URL: test your homepage, a blog post, or a specific CSS or JavaScript file — compression is often enabled for one type and not another.
  • The real response headers: the verdict comes from the actual headers your server sends, not from configuration files that may or may not be in effect.
  • Compressed versus uncompressed size: see how much data compression is saving on that URL, which tells you whether fixing a "disabled" result is worth the effort.
  • A plain-language result: gzip working, or gzip not working — without needing to read raw HTTP output yourself.

How to Run the Test

  1. Copy the full URL of the page you want to check, including the https:// part.
  2. Paste the URL into the GZIP Compression Test on this page.
  3. Start the test and wait a few seconds while the tool requests the page.
  4. Read the result: it will tell you whether gzip compression is active for that URL, along with the relevant header and size information.
  5. If compression is off, enable it in your server configuration, hosting panel, or caching plugin, then run the test again to confirm the change took effect.
  6. Repeat for one or two other page types — for example a product page and a stylesheet — since servers sometimes compress HTML but not static assets, or the reverse.

When Site Owners Typically Run This Check

A common moment is right after moving hosts. A site that was compressed on the old server can silently lose that setting during migration, and the first symptom is just a vague feeling that pages feel heavier. A ten-second test settles it. Another is after installing a caching or optimisation plugin: plugins advertise compression, but conflicts with server-level settings mean the feature sometimes never activates, which is why verifying beats trusting the dashboard.

Here is a practical reading of a result. Suppose the test reports your homepage arriving uncompressed at roughly 180 KB of HTML, while the compressed figure shown for comparison is a fraction of that. Every visitor — especially on mobile connections — downloads the difference, on every page, forever, until compression is switched on. Multiply that by a CSS and JS bundle in the same state and the wasted data becomes the single cheapest speed problem you will ever fix. While you are auditing, it is also worth confirming the site itself responds cleanly with the Website Status Checker and reviewing what else the server reveals using the HTTP Headers Parser.

If the Test Says "Not Enabled": Causes and Caveats

Work through the usual suspects in order. On Apache servers, gzip is handled by mod_deflate, which must be enabled and configured for the right file types; on Nginx, the gzip directives must be switched on in the configuration. Shared hosting may manage this from the control panel instead. If you use a CDN, compression can be applied at the CDN edge even when the origin does not compress — and vice versa — so test the public URL visitors actually use, which is what this tool does.

A few honest caveats. First, do not try to gzip images, videos, or PDFs: those formats are already compressed, and gzipping them wastes CPU for essentially no gain. Second, there is a newer sibling called Brotli that often compresses slightly better; a "gzip disabled" result does not always mean "no compression at all" if the server prefers Brotli — check the Content-Encoding value in the headers to see which one is in use. Third, compression settings can differ between the www and non-www versions of a site, or between HTTP and HTTPS, so test the exact address your visitors land on.

Frequently Asked Questions

What does gzip actually do to my web pages?

It compresses text-based responses (HTML, CSS, JavaScript, XML) on the server before sending them, and the browser decompresses them on arrival. The page looks identical; it simply travels in fewer bytes.

How can a test tell whether gzip is working?

By requesting your URL with headers that announce gzip support and then inspecting the response. If the server replies with a Content-Encoding: gzip header and a compressed body, compression is working.

The test says disabled, but I turned compression on. Why?

Common reasons include testing a different URL variant (www vs non-www), a CDN or plugin overriding the server setting, compression enabled for HTML but not the file type you tested, or the configuration not being reloaded. Retest the exact public URL after each change.

Does gzip compression help SEO?

Indirectly. Compression itself is not a ranking signal, but it makes pages load faster, and speed affects user experience and Core Web Vitals, which search engines do consider.

What is the difference between gzip and Brotli?

Both compress web responses. Brotli is a newer algorithm that often achieves slightly smaller files, especially at higher compression levels; gzip is older and universally supported. Either one is far better than no compression.

Should I compress images with gzip?

No. JPEG, PNG, WebP, and similar formats are already compressed internally, so gzip adds processing time without meaningfully reducing their size.

Is gzip the same as a ZIP file?

They are related in spirit — both shrink data — but different in use. A ZIP is an archive you download and open manually; gzip on the web happens automatically, per response, between server and browser.

One Check That Settles the Question

Compression is invisible when it works and silently costly when it does not, which makes it exactly the kind of setting worth verifying rather than assuming. Run the test after any hosting change, plugin install, or speed complaint, and you will know — from your server's own response — whether your pages are travelling light or travelling heavy.