NimbleCache Documentation

Two questions on one screen, because they are the same question from both ends: which pages are worth caching, and which must never be.

Cache these

By default, everywhere. The alternatives are the front page only, shop and product pages, or only what I choose below — which opens the detail:

• Places — the front page, the blog index, search results, the 404 page, and the shop page if you run one.
• Kinds of content — posts, pages, products, and any custom post type your other plugins register. New types are cached by default rather than waiting for you to notice them.
• Archives — the listing pages for any public taxonomy: categories, tags, product categories.
• And also these particular pages — search for individual pages, posts or products by name when ticking a whole kind of content is more than you meant.

The basket, the checkout and the account pages are deliberately absent from this list. They are never cacheable whatever anybody ticks, so offering them would be offering a switch that does nothing.

Never cache these

The same control backwards: quick ticks for the places most often left out, a search box for naming individual pages, and a box for address patterns.

Addresses never to cache takes a path or part of one, one per line. stands for anything, so /members/ covers everything under it. These are the one exclusion applied before WordPress loads — everything else on this screen is decided after the page is built, and simply stops it being stored.

The admin, login, REST API, basket and checkout are already excluded and do not need listing.

Never cache for these cookies takes cookie names. Logins, sessions and baskets are already handled.

Query parameters to ignore is the one worth understanding. Parameters listed here are stripped before the cache is looked up, so an advert click and a direct visit share one cached page. Everything not listed is kept, so a filtered product list or page two of an archive still caches separately — which is what most caching plugins get wrong by treating any query string as uncacheable.

A trailing covers a family: utm_.

Saving this screen empties the cache, because a page stored under the old rules is one the new rules would have refused.