DE

↑ ↓ select, Enter open, Esc close

Check whether a website serves gzip or Brotli

harmlessnginxalle
Adjust the values, the command updates live
user@server
curl -s -o /dev/null -D - -H "Accept-Encoding: br, gzip" https://example.com/ | grep -i "^content-encoding"

Sends a normal GET request announcing that Brotli and gzip are accepted, discards the content and shows only the Content-Encoding header. If it says br or gzip, compression is active. Empty output means the response is served uncompressed.

Note: Also test a CSS or JS file instead of just the homepage, since compression is often configured only for certain MIME types.

Also searched as

  • check if gzip is enabled
  • test brotli compression curl
  • is my site served compressed
  • pagespeed enable text compression

Related one-liners

All in nginx

Measure gzip and Brotli savings for a URL

$for e in identity gzip br; do curl -s -o /dev/null -H "Accept-Encoding: $e" -w "$e: %{size_download} Bytes\n" https://example.com/; done
harmlessImages and performance

Check the browser caching headers of a file

$curl -sI https://example.com/wp-includes/css/dist/block-library/style.min.css | grep -iE "^(cache-control|expires|etag|last-modified|age):"
harmlessnginx

Check whether a website supports HTTP/2

$curl -sI --http2 https://example.com/ | head -1
harmlessnginx

Check if LiteSpeed Cache serves a page from cache

$curl -s -o /dev/null -D - https://example.com/ | grep -iE "^(server|x-litespeed-cache[a-z-]*):"
harmlessLiteSpeed

Measure HTTP load times and TTFB with curl

$curl -o /dev/null -sS -w 'DNS: %{time_namelookup}s Connect: %{time_connect}s TLS: %{time_appconnect}s TTFB: %{time_starttransfer}s Gesamt: %{time_total}s\n' https://example.com/
harmlessNetwork

Measure the HTML and header size of a page

$curl -s -o /dev/null -w 'Status: %{http_code} Header: %{size_header} Bytes HTML: %{size_download} Bytes\n' https://example.com/
harmlessSEO checks

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.