All 33 NimbleCache answers

See every answer

Answer

How do I know it is actually working?

Updated NimbleCache 1.7.0Tested with WordPress 7.1

The Dashboard answers this at the top. Green means pages are being served before the plugins load.

To check a specific page, put its address into Diagnostics. It fetches the page twice and tells you what the server did. The second fetch saying HIT is the proof.

You can also open the page in a private window and view the source: a cached copy ends with <!-- NimbleCache … -->. Signed in, you always get a freshly built page, so look while signed out. Your browser's developer tools show the same thing in the X-NimbleCache response header — HIT, MISS, or BYPASS and the reason.

Still stuck? Ask the developers who wrote it. We aim to reply within one business day.

NimbleCache

Serve your pages before the plugins load — and never touch a setting to do it.

From $19 a year · every feature · 30-day refund

Buy NimbleCacheSee the plugin

The NimbleCache dashboard in WordPress admin. A green notice reads The cache is on and pages are served before WordPress loads. Four cards show 11 pages cached (2 MB), an average build of 229 ms, a 12 hour page lifetime and preloading off. A Fast Path panel ticks off advanced-cache.php installed and current, WP_CACHE switched on in wp-config.php, the cache directory writable and compressed pages. An Exclusions panel lists what is never cached, and a Clearing Log lists recent full clears with the plugin that probably caused each.