Server & delivery
Your pages are sent uncompressed
Missing response compression
What this means
The server sends text — HTML, JavaScript, CSS — without compressing it. Compression is a one-line setting and typically cuts what the visitor has to download by three to five times.
Why it matters
Every visitor waits longer and spends more mobile data than needed, and the slower load counts against you in search rankings. Nothing looks broken, so this stays unnoticed until someone measures.
When this is not a problem
Already-compressed formats — images, video, fonts — are not compressed again on purpose. This check only looks at text responses.
How to fix it
- Enable gzip or brotli for text responses in your server or CDN; on managed hosting it is usually a single switch.
- Behind a proxy, make sure it does not strip the Accept-Encoding header before your app sees it.
- Reload the page and confirm the response carries a Content-Encoding header.
Prompt for your AI agent
Text responses are served uncompressed. Enable gzip or brotli compression for HTML, CSS and JavaScript.
Verify the fix: request the page and confirm a Content-Encoding header is present
Is your app doing this?
Find out in about a minute — the first scan is free.