All 33 NimbleCache answers

See every answer

Answer

Can pages open the moment somebody clicks?

Updated NimbleCache 1.7.0Tested with WordPress 7.1

Yes. Choose Settings → Open Pages Before the Click → When the pointer rests on its link, or press Switch it on where the Dashboard offers it. The visitor's browser then fetches a cached page as the pointer rests on its link, so the page is already there when they click. Browsers that read these rules, Chrome and Edge among them, do this; the rest open pages as usual.

It never fetches the cart, the checkout, account pages or anything your Rules exclude, and it gives nothing to signed-in visitors or to a shopper with something in their cart, so resting on Cart never makes your server build a page nobody opened. Changing the choice empties the cache once, because the choice is written into every stored page.

If it seems to do nothing: the Settings screen says when caching is off or the Rules cache only some pages, which makes it fall back to fetching as a link is pressed, and it needs pretty permalinks. With the Speculative Loading plugin active, that plugin decides instead.

Cloudflare's Speed Brain adds rules of its own, fetching a link as it is pressed, and answers those fetches only from what Cloudflare has cached. The two work side by side, and you do not need to switch either off.

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.