Response Compression Test
Inspect compression headers on the fetched HTTP response.
Run the response compression test
Public website checkWhat response compression test helps you do
Inspect compression headers on the fetched HTTP response. Content-Encoding: gzip or br indicates a compressed representation. Text assets usually benefit most; already compressed image formats need different optimization decisions.
Prepare a useful input
Example input: https://example.com/ Save the original input alongside the result so another person can reproduce the check and judge whether a proposed change addresses the same page or file.
Read the result before making changes
A sampled response does not prove that all assets, encodings or CDN regions use compression. Record the checked URL and observation time. Compare the evidence with the intended page behavior, then verify the affected page again after a change instead of assuming the issue is resolved.
Inspect the selected representation rather than a file extension
A server can compress an HTML response on request without storing a .gz file on disk. The Content-Encoding header describes that representation, while transfer size and decoded size answer different questions. Compare responses with the same request conditions when investigating a discrepancy. If text is uncompressed, review origin and CDN configuration before changing application markup. Already compressed images may gain little from another compression layer. Keep a browser transfer sample alongside the header finding so the team can distinguish a configuration omission from an asset that simply contains too much data.
Verify the result and continue
Compare the response encoding with a browser transfer sample for the same resource. If a compressed response still transfers excessive data, inspect the resource itself instead of repeatedly changing compression settings. Keep HTML, JavaScript and image findings separate because their source formats and optimization options differ. Continue with the web page transfer size checker or explore the performance tool cluster.
How this tool works
Inspect compression headers on the fetched HTTP response. The server fetches the submitted public URL with bounded redirects and response sizes. The result reports observed HTML, headers or network evidence for this specific check.
What the result does and does not establish
A sampled response does not prove that all assets, encodings or CDN regions use compression.
Use this check as part of a repeatable website review. Record what you found, make a specific change and run the same check again.
Browse all toolsContent and technical review workflow