NiroCache – Simple Page Cache, Preload and Speed Optimization

Keep Standard, which is already selected. It adds preloading and minification on top of safe page caching. Choose Basic for membership or highly dynamic sites, or if anything looks wrong after minification. Aggressive also defers and delays JavaScript and caches approved query strings; try it if you are happy to test your key pages afterwards, because some sites need exclusions.

Changing any setting that a preset controls switches you to Custom, and NiroCache asks before it does. Nothing changes on your site until you save. Your last Custom combination is remembered, so you can go back to a preset and return to your own setup later.

Logged-in users always get freshly generated pages, so nobody ever sees someone else's personal content. Click Run cache test on the dashboard, or open your site in a private browser window, to see what visitors get.

Click Run cache test on the dashboard. It requests your home page twice and reports whether the second request was served from the cache, or why it was not. You can also turn on debug headers under Settings, Advanced, and look for X-Niro-Cache: HIT in your browser's developer tools while logged out. The dashboard charts show how many pages are served from the cache each day.

Use the On/Off switch next to the Dashboard title. Off pauses everything NiroCache does to your site and clears cached pages; your settings are kept, and turning it back on restores everything. It is the quickest way to check whether a problem comes from NiroCache.

Minified files are copies kept in the cache folder; your theme and plugin files are never modified. Defer and delay are only on in Aggressive mode, and payment, checkout and consent scripts are never delayed. If something looks wrong, add the script to the JavaScript exclusions under Settings, Optimization, or switch back to Standard or Basic.

Yes. Cart, checkout and account pages are never cached, shoppers with items in their cart always get fresh pages, and product pages are cleared when their stock or price changes. Easy Digital Downloads, EasyCommerce and NiroCommerce checkout and account pages are excluded too.

Any server that runs WordPress: Apache, Nginx, LiteSpeed and others. The early cache works everywhere with no server configuration. On Apache and LiteSpeed, NiroCache can also add browser caching, compression and direct delivery rules to .htaccess; on Nginx, the Server screen shows a configuration snippet you can add if you want Nginx to deliver cached pages itself.

Running two page caches at once causes unexpected behavior, so NiroCache warns you when it detects another page cache or optimization plugin. It never overwrites another plugin's advanced-cache.php or object-cache.php. The Server screen also detects hosting caches such as LiteSpeed, Varnish, Cloudflare and managed hosts, and recommends what to do.

Tick Don't cache this page in the NiroCache box of the page editor, or add its path under Settings > Exclusions > Never cache these URLs. Use /members/* to exclude a section and everything below it. You can also exclude cookies, user agents and post types there.

WordPress form security tokens expire after 12 to 24 hours. Keep the cache lifespan at 10 hours (the default) or lower on sites with forms.

Preloading requests your pages one at a time in small batches, with a pause between pages. You can lower the batch size or lengthen the pause under Settings > Preload, or turn sitemap preloading and cache warming off.

Yes. Each site keeps its own cache and settings. Super admins can clear every site's cache at once from the admin toolbar.

Deactivating removes the early-cache file, the WP_CACHE line and the .htaccess block NiroCache added, and deletes cached pages; your settings are kept. Deleting the plugin also removes its settings, statistics and the whole cache directory.