NimbleCache documentation

Setting it up, and how each part works: 19 sections, free to read before you buy.

  1. Getting startedInstall and activate.
  2. Multisite networksActivate it on one site or across the whole network.
  3. What actually happensOn a cached page, WordPress never runs.
  4. What is never cachedWhatever the settings say: Signed-in visitors. No setting changes this: one stored copy of a page is served to everybody, so a page built for somebody signed in would show the…
  5. Pages built but not storedWhen the Dashboard shows far fewer pages cached than your site has, the Pages Not Stored panel says why.
  6. How long a page is keptNimbleCache keeps a cached page until something changes it, and never longer than its Page lifetime, which is twelve hours by default.
  7. Throwing pages awayChange a post and the plugin purges that post, the front page, its categories and tags, its author archive, its date archives, the post-type archive and the feeds.
  8. RulesTwo questions on one screen, because they are the same question from both ends: which pages are worth caching, and which must never be.
  9. Warming pages upOff by default.
  10. Opening pages before the clickSettings → Open Pages Before the Click decides when a visitor's browser starts loading the page they are about to open.
  11. Disk limitSettings → Maximum cache size is off by default, because a cache is meant to grow.
  12. IntegrationsA screen that reports rather than asks.
  13. DiagnosticsGive it an address.
  14. From the command lineWP-CLI is a convenience, never a requirement — everything is available in the admin.
  15. For developers// Refuse to cache a page, with a reason that shows in Diagnostics.
  16. Speed and privacyNimbleCache fetches nothing from anywhere.
  17. UninstallingDeactivating removes the drop-in, takes WP_CACHE back out of wp-config.php and clears the cache.
  18. Moving your settings to another siteSettings → Import / Export.
  19. An admin without page loadsMoving between the plugin's screens does not reload the page, and neither does saving.

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