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.