HTML served without compression
low Performance no_compression
What we check
An HTML response has no gzip or brotli Content-Encoding although the crawler accepts gzip.
Why it matters
Text compresses well; compression usually shrinks HTML by more than half, which matters most on mobile networks.
How to fix it
Enable gzip or brotli for text types on the web server or CDN.
How to confirm the fix
curl -sI -H 'Accept-Encoding: br, gzip' URL | grep -i content-encoding.
In the API response
When this check fails, output.technical_issues contains an item with "id": "no_compression", the affected URLs as evidence and the fix. If it is among the highest-priority problems it also appears in actions (as finding_id) and in plan.
Related checks
Run the full audit on your site. One call checks every item in the check reference and ranks the fixes.
Open the playground Endpoint details