Check whether a page is compressed with Gzip or Brotli, how many bytes it really sends, and what the rest of the page weighs
Run a complete audit to check performance, mobile-friendliness, meta tags, and more.
Run Free Website Audit
Text files such as HTML, CSS and JavaScript compress extremely well, often shrinking by 70 to 90
percent. When a web server compresses them with Gzip or Brotli before sending, pages download faster,
use less mobile data, and cost less bandwidth. This tool requests your page the way a browser does,
once for each compression format, and counts the real bytes that come back, so you see exactly which
formats your server supports and how much each one saves. It compares that against the uncompressed
size, checks whether the Vary: Accept-Encoding header is set so caches behave, and, if you
like, measures the CSS, JavaScript, images and fonts the page loads to estimate total page weight and
point out files that are uncompressed or oversized. Total weight counts only the assets that could be
measured, so treat it as a lower bound for pages that load content with JavaScript.
Gzip is supported everywhere. Brotli usually produces smaller text files and is supported by all modern browsers over HTTPS. The best setup serves Brotli to browsers that ask for it and falls back to Gzip for the rest.
On Nginx, add this to your http or server block:
On Apache, enable mod_deflate:
Many CDNs and hosting platforms, such as Cloudflare, also offer a one-click compression setting.
JPEG, PNG, WebP and AVIF files are already compressed, and applying Gzip to them gains almost nothing. Reduce them by resizing and by using modern formats instead.
For responses under about 1 KB, compression saves almost nothing and many servers skip it on purpose, so it is not counted against you.
Text files such as HTML, CSS and JavaScript compress extremely well, often shrinking by 70 to 90 percent. When a web server compresses them with Gzip or Brotli before sending, pages download faster, use less mobile data and cost less bandwidth. This tool shows you whether your server is actually doing that, and how much it saves, using measurements rather than guesses.
The checker requests your page the way a browser does, once for each compression format, and counts the real bytes that come back. From that it reports:
Vary: Accept-Encoding header is set, so caches and CDNs do not hand a compressed copy to a client that cannot read it.Every byte your server sends has a cost for someone. Visitors on slow or metered mobile connections wait longer and spend more data, and you pay for the bandwidth. Because speed is part of page experience, heavy pages also make it harder to pass Core Web Vitals such as Largest Contentful Paint. Compression is a server setting, needs no redesign, and applies to every text response.
It is also one of the easiest settings to get wrong. A CDN may compress some file types and skip others, a reverse proxy may strip the header that triggers compression, or Brotli may be enabled for HTML but not for JavaScript.

A browser announces the formats it understands in an Accept-Encoding request header, and the server picks one and labels its answer with Content-Encoding. This tool repeats that exchange on purpose: one request that accepts only Gzip, one that accepts only Brotli, and one that accepts neither. It then counts the bytes that arrive for each, so the numbers reflect what your server really sends rather than what a configuration file says it should send.
With the page-weight option on, the tool also measures each referenced resource and lists large, uncompressed files first.
Vary: Accept-Encoding so shared caches store one version per encoding.
If the report shows a gap, these are the usual starting points. Test your own configuration before deploying it.
Nginx: enable gzip on;, set gzip_vary on; and list the text types to compress with gzip_types. Brotli needs the Brotli module.
Apache: enable mod_deflate, add AddOutputFilterByType DEFLATE text/html text/css application/javascript and send Header append Vary Accept-Encoding.
CDNs and managed hosting: look for a compression or Brotli toggle in the dashboard, and re-run this check afterwards to confirm the change reached visitors.
Total page weight counts only the assets that could be measured, so treat it as a lower bound for pages that load content with JavaScript. Resources fetched after the page runs scripts, lazy-loaded media and third-party calls made in the browser may not appear. Results can also differ by location, because a CDN may serve different edge servers. For a full picture of load behavior, pair this tool with a lab test such as the Website Speed Test & Core Web Vitals checker.
Compression is one part of a fast, healthy site. These free tools cover the neighboring checks:

Gzip is supported everywhere. Brotli usually produces smaller text files and is supported by all modern browsers over HTTPS. The best setup serves Brotli to browsers that ask for it and falls back to Gzip for the rest.
On Nginx, add this to your http or server block:
gzip on; gzip_comp_level 5; gzip_min_length 256; gzip_vary on; gzip_types text/css application/javascript application/json image/svg+xml font/ttf font/otf application/xml;
On Apache, enable mod_deflate:
AddOutputFilterByType DEFLATE text/html text/css application/javascript application/json image/svg+xml font/ttf font/otf
Many CDNs and hosting platforms, such as Cloudflare, also offer a one-click compression setting.
JPEG, PNG, WebP and AVIF files are already compressed, and applying Gzip to them gains almost nothing. Reduce them by resizing and by using modern formats instead.
For responses under about 1 KB, compression saves almost nothing and many servers skip it on purpose, so it is not counted against you.
Built and maintained by Kester Terna, founder of Auditest, as part of a free suite of technical SEO and performance checkers. Results come from live requests to the URL you enter. Questions or corrections are welcome through the contact page.