DE

↑ ↓ select, Enter open, Esc close

Check if LiteSpeed Cache serves a page from cache

harmlessLiteSpeedalle
Adjust the values, the command updates live
user@server
curl -s -o /dev/null -D - https://example.com/ | grep -iE "^(server|x-litespeed-cache[a-z-]*):"

Fetches the page and shows the Server header plus the LiteSpeed cache headers. hit means the page came from the cache, miss means it was freshly generated and is now being stored. A second request should therefore return hit. If it stays at miss or the header is missing, the cache does not apply to this URL.

Note: Logged-in users and pages with cookies are often deliberately not cached, so test without cookies.

Also searched as

  • is litespeed cache working
  • x-litespeed-cache hit or miss
  • check if page is cached litespeed
  • test lscache

Related one-liners

All in LiteSpeed

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

Purge LiteSpeed Cache for a WordPress site with WP-CLI

$wp litespeed-purge all --path=/var/www/vhosts/example.com/httpdocs
cautionLiteSpeed

Check whether a website serves gzip or Brotli

$curl -s -o /dev/null -D - -H "Accept-Encoding: br, gzip" https://example.com/ | grep -i "^content-encoding"
harmlessnginx

Check whether a website supports HTTP/2

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

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.