web validator

HTTP Compression Validator

Check HTTP response headers for gzip/br compression, numeric lengths, and basic ratios—client-side only.

Results

Processing…
Status
Processing...
Details
Processing...
Encoding
Processing...
Content-Length
Processing...
Original size
Processing...
Compression ratio
Processing...

How to use this validator

  1. Paste the response headers.
  2. Run validate to check encoding and sizes.
  3. If missing encoding or bad sizes, fix server/CDN config and re-run.

Rules & checks

Checks for Content-Encoding (gzip, br, deflate).

Ensures Content-Length is numeric when present.

Supports optional X-Original-Size to compute compression ratio.

Runs fully client-side; no data stored.

Inputs explained

  • HTTP response headers

    Paste raw headers (one per line) from curl/DevTools. Include Content-Encoding and sizes if available.

When to use it

  • Verify CDN/edge compression headers
  • Check server responses in CI before deploys
  • Support/ops debugging missing compression

Common errors

  • Content-Encoding missing
  • Non-numeric Content-Length or X-Original-Size
  • Already-compressed assets being recompressed

Limitations

  • Header-level checks only; does not measure real transfer or decode bodies.
  • Relies on provided sizes; cannot fetch assets.

Tips

  • Include X-Original-Size to see computed ratios
  • Avoid compressing already-compressed assets (images, video)
  • Ensure compression happens after templating to avoid double work

Examples

Gzip with sizes

  • Content-Encoding: gzip
  • Content-Length: 1024
  • X-Original-Size: 4096 -> ratio 0.25

Missing encoding

  • Content-Length present but no Content-Encoding -> flagged

Brotli

  • Content-Encoding: br
  • Content-Length: 2048

Deep dive

This compression validator checks Content-Encoding and size headers entirely in your browser to confirm gzip/br are set and sizes are numeric.

Use it to QA CDN/server responses pasted from DevTools or curl before shipping.

FAQs

Do you fetch responses?
No. Paste headers only; validation is local.
Do you decompress bodies?
No. This is header-only validation.

Related validators

All validation happens in your browser. No data is sent, logged, or stored.

Header-level checks only; does not measure real transfer or decode bodies.