How to use
- Enter
example.comorhttps://example.com/app.jsunder Address to check. Give the address of a JavaScript, CSS or JSON file instead of a page to check that file. The port is fixed at 443. - Choose the requested compression. The default offers
gzip, br, zstdtogether, and to test whether one method is supported, pick it alone and check separately. - Pick one or more regions. South Korea is the default.
- Press Check compression. A probe in each region sends one GET request with an
accept-encodingheader. - In the table read whether it is compressed,
content-encoding,vary,content-type, size and status code, then read the fix tips under What it means. Copy result gives you the text.
How it decides
A browser adds a header such as accept-encoding: gzip, br to say “I can unpack responses compressed with these methods”. The server picks one of them, compresses the response and announces it in the content-encoding response header. This tool sends the same kind of request and reads whether content-encoding is present. Without it the response is uncompressed.
| Method | Notes | Remarks |
|---|---|---|
| gzip | The most widely used, supported by every browser | The method to have on by default |
| br (Brotli) | Usually shrinks files more than gzip | Browsers request it over HTTPS only |
| zstd | A newer method with good speed and ratio | Only some browsers support it so far |
The judgement follows this order:
| Response | What the tool says |
|---|---|
content-encoding is gzip, br or zstd |
Compressed |
| None, text type (html, css, js, json, svg and so on), 1 KB or more | Not compressed, needs fixing |
| None, under 1 KB | A small response, can be normal |
| None, already compressed format such as image, video, pdf or woff2 | Normal |
| None, with a 301 or 302 redirect | Not judged, check the final address |
The 1 KB line is this tool’s own rule of thumb, and the minimum size differs by server.
Why the vary header matters
A compressed response should come with Vary: Accept-Encoding. Without it, a shared cache such as a CDN or proxy may hand a gzip copy to a client that cannot unpack it. In a real response, the python.org home page answered with gzip but only vary: Cookie, while a JavaScript file on the same site sent gzip together with Vary: Accept-Encoding. This tool flags the first case as a warning. It is not always an error, though, because some CDNs tell the copies apart in their own way.
How to turn compression on
- nginx: set
gzip on;andgzip_types text/css application/javascript application/json image/svg+xml;. text/html is compressed by default. Brotli needs a separate module. - Apache: enable mod_deflate and add
AddOutputFilterByType DEFLATE text/html text/css application/javascript application/json. - CDN or hosting: most dashboards have a compression (gzip, Brotli) option. Turning it on lets the CDN compress even if the origin does not.
- Images, video and pdf are already compressed, so compressing them again gains almost nothing and leaving them out is right.
What is sent, and the limits
- The address you enter is sent to the measurement service Globalping, and the probe IP is logged by the target server. See the privacy policy for details. Results are not stored.
- Private and internal addresses are not measured, and there is an hourly request limit.
- This sends one request per region for one address as a checking tool. It is not meant for generating load or scanning. Only the start of the body is received, and it never repeats automatically.
- The server picks one of the methods you offer, so with “all” you only see its preferred one. The compression ratio (size saved) is not available.
- For all response headers use the HTTP Header Viewer, and for the connection protocol the HTTP/2 & HTTP/3 Checker.
Frequently asked questions
How much faster does gzip make a site?
Text with a lot of repetition, such as HTML, CSS and JavaScript, shrinks a lot when compressed, which shortens loading especially on slow connections. How much depends on the content, so no single figure fits.
Is br always better than gzip?
It usually produces smaller files but can cost more CPU to compress. A common setup is to precompress static files with br and use gzip or a low br level for dynamic responses.
It says not compressed, but I know compression is on.
Check whether the address redirects, whether the response is under 1 KB, and whether the file type is already compressed. The server may also answer differently for different accept-encoding values, so set the requested method to gzip only and try again. The Redirect Checker can find the final address.
Should images be compressed too?
JPEG, PNG and WebP are already compressed, so adding gzip gains almost nothing. For images, reduce the file size itself instead. SVG is text, though, and is worth compressing.
Can I check security headers here too?
They are separate from compression. Use the HTTP Security Header Checker for response security headers.
The address you enter is sent to an outside measurement service (Globalping) and is never stored on this site’s servers.