Free tool
Compression and caching
Two server settings that cost nothing and make every visit lighter: compress text files before sending them, and let browsers keep what doesn't change. We check your page and its main files.
Two settings, two different gains
01
Compression
The server shrinks text files (HTML, CSS, JavaScript, SVG) before sending them; the browser unpacks them instantly. Brotli does better than gzip. Images and WOFF2 fonts are already compressed: nothing to gain there.
02
Cache
The Cache-Control header tells the browser how long it may keep a file without asking again. Long for fixed files, short for pages.
03
Validators
ETag and Last-Modified let the browser ask “has it changed?”: if not, the server answers in a few bytes.
How to read the table
“Size” shows what travels over the network, then the real size once unpacked. A green “Brotli” or “GZIP” badge on text files: all good. A red or orange “none” on a CSS or JavaScript file: that's where to start.
Frequently asked questions
Does my site use compression and caching?
Enter the page address: the tool checks the page and its main files, namely CSS, JavaScript, images and fonts. It reports the encoding (Brotli, gzip), the transferred size, the cache duration and the HTTP version.
How do I read the table?
“Size” shows what travels over the network, then the real size once unpacked. A green Brotli or GZIP badge on text files is good. A red or orange “none” on a CSS or JavaScript file is where to start.
Should images be compressed?
Not with this setting. Images and WOFF2 fonts are already compressed, so there is nothing to gain. Compression targets text files: HTML, CSS, JavaScript and SVG.
