VoriTools

Gzip Compression Check

Enter a website address to request it once through VoriTools. The report names the HTTP status, the redirects followed, the Content-Encoding of the response that answered, and both sizes: the body after decompression and the bytes that crossed the network.

How to read the compression report

Enter a public website address and the VoriTools server requests it once with the Accept-Encoding header a browser sends. The report shows the HTTP status, how many redirects were followed, the Content-Encoding of the response that answered, and two sizes: the body after decompression and the bytes that actually crossed the network.

The result describes the single response the VoriTools server received. It is not a browser test, not a CDN report and not a page-speed score: a server can compress HTML and leave JSON or images plain, and an edge cache can answer differently from the origin.

  1. Type the address (example.com or https://example.com/page) and press Test.
  2. Read the HTTP status and the redirect count first; only the response that finally answered is measured.
  3. Compare the uncompressed size with the transferred size. Equal numbers mean the response arrived without compression even though the server may support it.
  4. Read the Content-Encoding row together with the headers table to see what the server chose for this request: gzip, br, deflate or none.
  5. Repeat the check on a second page or on a second run to see whether a cache layer answers differently.

What the numbers mean

Reading the two sizes

The uncompressed size is the response body after the content coding was removed; the transferred size is what the network carried for that body. The difference between them is the saving, shown as a percentage. A response without content coding reports the same number twice and 0 %.

Headers are not part of either figure, and a redirect's own body is not added to the page you asked for. When the body is empty, for example a 204 or an error page without content, the percentage is shown as a dash instead of a number.

Redirects, caches and which answer is measured

Up to five redirects are followed. The header table lists only the response that finally answered, so a redirect's Content-Length cannot be mistaken for the size of the page. The hop count is reported as its own row.

The check runs from one machine in one location with one resolver. A CDN may compress, re-compress or cache per edge node, so visitors elsewhere can receive a different encoding than this report shows, and a caching layer may return an older copy.

Limits and privacy

Only HTTP and HTTPS addresses are accepted, and private, reserved or local addresses such as 10.x, 192.168.x, 127.x, link-local ranges and cloud metadata endpoints are refused before any request is sent. Responses larger than 8 MB are not measured.

The address you type is sent to VoriTools, requested once and not stored with the result. There is no account, no history and no download of the page; the report is the answer to this one request.

Recent tools: