Gzip compression test that lets you check gzip compression (and Brotli) for any URL. See encoding, size before/after, and savings.

The browser requests the URL with Accept-Encoding: br, gzip. The server tells us which compression it used via the Content-Encoding response header. Some sites block cross-origin requests — if testing fails, run curl -I -H 'Accept-Encoding: br,gzip' URL from your terminal.
Confirms whether your origin or CDN is gzipping text assets.
Brotli typically saves 15–25% more than gzip on the same file — worth confirming you're shipping it.
Paste the URL of a specific .js or .css file to verify it's compressed in transit.
If results show no encoding header, enable gzip in your caching plugin or at the CDN.
Both are HTTP compression algorithms. Brotli is newer and compresses text assets ~15–25% better than gzip at similar CPU cost. All modern browsers support both.
No. We make a single read-only request to fetch response headers — nothing is stored or shared.
Either your origin server isn't compressing text assets, or your CDN is stripping the Accept-Encoding header. Enable gzip/Brotli at the CDN or web-server level.
No. Images (JPG, PNG, WebP, AVIF) are already compressed — gzipping them wastes CPU and saves nothing.
Text assets typically shrink 70–85% in transit, which speeds up first paint noticeably on slow connections.
Want your whole site this fast? Our team offers full website speed optimization — done for you .