Response compression is enabled
Why it matters
Uncompressed HTML, CSS, and JavaScript responses force users to download 3–5x more bytes than necessary. For a 200 KB uncompressed page, enabling Brotli or gzip typically reduces transfer to 40–80 KB — a direct reduction in time-to-interactive, especially on mobile connections. ISO 25010 performance-efficiency is directly impacted: slow load times increase bounce rate, hurt Core Web Vitals scores, and degrade SEO rankings. Compression is a server-side toggle that costs negligible CPU and delivers guaranteed bandwidth savings. Its absence signals misconfigured infrastructure rather than an intentional choice.
Severity rationale
High because missing compression directly increases page load time by 3–5x for text assets, with measurable impact on Core Web Vitals, bounce rate, and SEO rankings on every page load.
Remediation
Enable Brotli or gzip compression at your server or CDN. On nginx:
gzip on;
gzip_comp_level 6;
gzip_types text/html text/css application/javascript application/json image/svg+xml;
For Brotli (nginx with ngx_brotli module):
brotli on;
brotli_comp_level 6;
brotli_types text/html text/css application/javascript;
On Vercel and Netlify, compression is enabled automatically — no action needed. For Express, add the compression middleware:
import compression from 'compression';
app.use(compression());
Verify: curl -sI -H 'Accept-Encoding: gzip, br' https://yoursite.com | grep -i content-encoding.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Site Health Check audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- iso-25010:2011 · performance-efficiency.time-behaviour — Time Behaviour — response compression reduces transfer time for text assets
Taxons
History
- 2026-04-18·v1.0.0·Initial import from site-health-check·automated