Audit rules
HTML Not Compressed
The HTML response has no Content-Encoding (or only identity), so it is sent uncompressed. In a QuikSEO audit, a failure of this rule has info severity and counts against the score. Below are the exact condition, its exceptions and the sources behind it, followed by the other rules of the same group.
http.compressionInfo01 — Definition
How This Rule Is Checked
The rule is a pure function of the fetched page: no extra requests, no account settings. The same input always gives the same result.
Rule Severity and Score
- Rule id
http.compression- Group
- HTTP
- Severity of a failure
- Info
- Counts in the score
- Yes, whenever it applies to the page
- Required for a score
- No
- Replaces the check
server_compression
Condition and Exceptions
- Condition
- No Content-Encoding (or identity) on the HTML response → fail (info)
- Exceptions
- —
Sources
- Sources
- Overview of Google crawlers and fetchers (user agents) (Google for Developers, Q03)
Document request latency (Chrome for Developers, Q22)
02 — HTTP
Other Rules in This Group
The other checks of the same group, each with its own condition and sources.
- No Cache Validatorshttp.cache_validators
- Page Answers With an Error Statushttp.error_status
- WWW and Non-WWW Both Serve the Pagehttp.host_variant_duplicate
- HTTP Protocol Versionhttp.http2
- HTTP Version Not Redirected to HTTPShttp.http_variant_not_redirected
- Page Not Served Over HTTPShttp.https
- Mixed Contenthttp.mixed_content
- X-Powered-By Version Disclosedhttp.powered_by
- Redirect Chainhttp.redirect_chain
- Server Version Disclosedhttp.server_header
- TLS Certificate Expiring Soonhttp.tls_expiring
- Invalid TLS Certificatehttp.tls_invalid