About GZIP Compression
What is a GZIP test?
A GZIP test asks a simple question: when your server sends a page, does it compress it first? GZIP is the compression method the web has used for decades, and it works by finding repetition in text and encoding it more efficiently.
HTML, CSS and JavaScript are extremely repetitive, so the savings are large, typically 70 to 90 percent. The browser expands the file on arrival, and the visitor never knows it happened.
It is configured once on the server, applies to everything at once, and costs almost nothing in processing. That is why a failed GZIP test is worth acting on immediately: few fixes are this cheap or this broad.
GZIP and Brotli
Brotli is a newer compression method that generally outperforms GZIP on text, often by another 15 to 20 percent, and is supported by every current browser.
It has not replaced GZIP so much as joined it. Servers negotiate with each client and use the best method both support, so the normal configuration is Brotli with GZIP as the fallback.
A GZIP test that passes tells you compression is happening. Whether the better method is being used is a separate question, and worth asking once the basic case is covered.
Does compression still matter in 2026?
It is one of the few optimisations that is close to free and helps every visitor on every request. Nothing else on a performance checklist has that combination of reach and cost.
Most modern hosting enables it by default, which is precisely why it goes unnoticed when a migration, a custom server configuration or a new CDN layer switches it off. Sites lose compression far more often than they gain it.
The effect is invisible on a single page load and considerable across a whole site, which is the sort of problem that survives for years without anyone reporting it.
How compression relates to AI search
Crawlers request compressed responses like any other client. Serving uncompressed HTML makes every fetch larger and slower, which reduces how much of a large site gets read in a given crawl.
That cost is invisible per page and significant across thousands, which makes it exactly the kind of thing worth checking rather than assuming.
It has no bearing on how content is understood, only on how much of it is reached.
Compression best practices
- Enable it for HTML, CSS, JavaScript, SVG and JSON.
- Do not compress images or video; they are already compressed and will get slightly larger.
- Prefer Brotli where supported, with GZIP as the fallback.
- Re-check after any hosting, CDN or server change.
- Verify with response headers rather than trusting the control panel setting.
- Combine with minification; the two remove overlapping but not identical redundancy.
What this tool checks
The GZIP test requests the page and reports whether the response arrived compressed, passing when it did.
It checks the page document, so a compressed page that serves uncompressed stylesheets or scripts will still pass. If the document is compressed but the site still feels heavy, the assets are the next place to look.
Where to go next
Compression is one of three ways to make files smaller. Check whether your assets are also
minified, see what the page weighs in total with the
webpage file size tool, and confirm the server is using a modern protocol with the
HTTP/2 check.