Inputs
Enter a public page URL. The checker uses the same protected URL validation and bounded fetch model as the Website Speed Test.
Free public URL tool
Check whether the public HTML response advertises gzip, Brotli, or zstd compression and compare transferred page weight.
Problem, cause, fix, verify
Problem
Teams often blame images or JavaScript before checking whether text responses are compressed and whether transferred bytes match expectations.
Audience
Developers, hosting teams, agencies, and site owners reviewing public response efficiency.
First check
Enter a public page URL. The checker uses the same protected URL validation and bounded fetch model as the Website Speed Test.
Verify
After enabling compression or CDN rules, retest the same URL and compare transferred bytes, cache-control, and failed resource counts.
Editorial trust
On this page
Decision Support
For: Developers, hosting teams, agencies, and site owners reviewing public response efficiency.
Use The Tool
Enter a public page URL. The checker uses the same protected URL validation and bounded fetch model as the Website Speed Test.
Review the public content-encoding signal, transferred page weight, resource count, and resource-domain weight from the collected HTTP-lite result.
Missing HTML compression is a practical review item, especially for text-heavy pages. Asset compression still needs CDN or server confirmation when the decision depends on specific CSS, JavaScript, SVG, XML, or JSON files.
After enabling compression or CDN rules, retest the same URL and compare transferred bytes, cache-control, and failed resource counts.
This checks the public HTML response and transferred resources collected by the HTTP-lite test; it does not inspect private server configuration.
Limitations