All 33 NimbleCache answers

See every answer

Answer

Why is a page with a query string still cached?

Updated NimbleCache 1.7.0Tested with WordPress 7.1

Because it should be. Tracking parameters — utm_*, gclid, gad_source, srsltid, fbclid and the rest — are stripped before the lookup, so an advert click or a Google Shopping result gets the same cached page as a direct visit. Real parameters like sorting and pagination are kept, so those cache separately, and they are cleared along with the page they belong to: changing a product clears /shop/page/2/ and /shop/?orderby=price as well as /shop/.

Most caching plugins treat any query string as uncacheable, which quietly turns off caching for most of a shop.

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.