Jaipur, India · serving India, UAE and USA
Home/Free Tools/Technical SEO/Compression Checker

Compression Checker

Check whether a page is served with gzip or Brotli and how much it saves.

100% free No signup Live server-side check

Try it now

About this tool

What is the Compression Checker?

A compression checker tests whether a server sends a page compressed with gzip or Brotli and compares the transferred size with the uncompressed size. Compression is one of the cheapest speed wins.

This tool fetches the address you enter once, from our server, and reports what a crawler would receive. The URL is not stored; only a short-lived rate-limit counter is kept. Results show the page at the moment of the check and can differ from what a logged-in browser or a bot with different headers sees.

Why use it

Why use this tool

Live check

Reads the real page at the moment you run it, with every redirect followed and shown.

Plain-English output

Each finding says what it means and what to do next, not just a raw value.

Copy-ready

Copy the output straight into your CMS, spreadsheet, ticket or client report.

No account needed

Free, with no signup. Fair-use limits keep the tool fast for everyone.

How it works

A few clicks to a better result

1

Enter the address

Use a full public URL.

2

Run the check

The page is fetched live from our server.

3

Fix and retest

Apply the fixes, then run it again.

Written, edited and verified by Hemant Kumar, SEO consultant in Jaipur with about 8 years of experience in technical SEO, AEO and GEO. Last reviewed: Oct 2026.
Guide

How to read the result and act on it

The result should show a content-encoding of gzip or br and a transferred size clearly smaller than the uncompressed size. Text formats such as HTML often shrink by well over half, so a tiny difference or no encoding signals a problem. If compression is missing, enable it at the server or CDN: mod_deflate or mod_brotli on Apache, gzip or brotli directives on Nginx, or a toggle in your CDN or hosting panel. Prefer Brotli for text where supported and keep gzip as a fallback. After enabling, retest and confirm the vary: accept-encoding header is present so caches serve the right version.

Common mistakes to avoid

A typical mistake is enabling compression only for HTML while leaving CSS, JavaScript, JSON and SVG uncompressed. Compressing already compressed formats such as JPEG, PNG, WebP or video wastes CPU for almost no gain. Setting very high compression levels on dynamic pages can raise response time and cancel the benefit. Forgetting the Vary header can cause a cache to serve compressed content to a client that cannot read it. A CDN may compress differently from your origin, so test the public URL, not just the server. Finally, compression does not replace removing unused code and oversized assets, which still need separate work.

Next steps

Use this with

Browse all 41 free technical seo tools, or see the full free SEO toolbox. If you would rather have this handled for you, take a look at our technical SEO services and the results from real projects.

Similar free tools

More free tools you may need

All free tools ↗
FAQ

Questions, answered

It tests the URL you enter; test asset URLs separately.
The page is requested by our server and the comparison is shown to you, not stored. Avoid URLs with private tokens, since they are sent to the target site as part of the request.
CDNs often apply their own compression and may cache a different encoded version. Test the public URL that visitors use, and review CDN compression settings so the edge and origin do not conflict.
WhatsApp Get your free proposal