WebGee Docsالتوثيق
WordPress

Check whether LiteSpeed Cache is working

Confirm your pages are being served from LSCache using the response headers, and understand what a hit, a miss and no header at all each mean.

Two ways to confirm LSCache is serving your pages. Applies to all shared and reseller hosting, which runs LiteSpeed.

Read the response headers

This is the reliable method, because it tells you about the exact page you are looking at.

  1. Open your site in Chrome.
  2. Open Developer Tools with F12.
  3. Switch to the Network tab.
  4. Reload the page.
  5. Select your domain in the request list — the first entry, the HTML document.
  6. Look at the Response Headers for x-litespeed-cache.
HeaderMeaning
x-litespeed-cache: hitServed from cache. Working
x-litespeed-cache: missGenerated by PHP, then stored. The next request should be a hit
No header at allThe page is not being cached

A miss on first load is normal and not a fault. Reload once and expect a hit.

Logged-in pages are deliberately not cached, so wp-admin and any page viewed while signed in will always miss. Test in a private window.

Use the LiteSpeed checker

check.lscache.io reports whether a URL is being served by LSCache. It is quicker than opening Developer Tools, but it only checks the one URL you give it.

If nothing is cached

  • Confirm the plugin is active. LSCache needs the LiteSpeed Cache plugin installed and enabled in WordPress — see Install and enable LiteSpeed Cache.
  • Check for a .litespeed_flag file in the site's document root. That file tells the server not to cache the site — see Prevent LSCache from auto-installing.
  • Check for a conflicting cache plugin. Two page caches will fight, and the usual symptom is that neither works.

On this page