Use Test cache
On the Dashboard, click Test cache. It clears your homepage and loads it twice as a logged-out visitor. “1st visit · MISS” then “2nd visit · HIT” means the cache works.
Look at the response header
Open your site in a private window (you must be logged out) and look at the response headers in your browser’s developer tools, or run:
curl -sI https://example.com/ | grep -i x-softminal| Header value | Meaning |
|---|---|
HIT | The page came from the cache. |
STALE | An older copy was served while a fresh one is built (only with stale while revalidate on). |
MISS | The page was built now and stored for the next visitor. |
BYPASS: reason | The page is not cached on purpose. The reason tells you why, for example logged-in, cookie or shop. |
The header is shown when Show cache status in headers is on (Cache tab, Browser and server card). It is on by default.
Logged in as admin? You will always see BYPASS. Editors and administrators are never served cached pages, so you always see your latest changes.
Use the debug log
For more detail, turn on the Debug log on the Tools tab. It records each HIT, MISS, BYPASS, STORE and PURGE, and switches itself off after 24 hours.