Brendigo

BrenWP Cache speeds up WordPress by serving cached HTML pages to anonymous visitors. On a cache miss, WordPress renders the page normally; BrenWP Cache captures the final HTML output and stores it as a file. On subsequent requests, the cached HTML is served early, reducing server load and improving response times.
This plugin is intentionally minimal, transparent, and WordPress.org-friendly: 
* No telemetry, no tracking, no “phone home” 
* No external services or dependencies 
* Admin UI assets are strictly scoped to this plugin’s pages
<h3>Key features</h3>
Full-page file cache for anonymous visitors 
* Caches full HTML documents for GET requests only. 
* Designed for the common “public pages” scenario where most traffic is anonymous. 
* Avoids caching in common non-cacheable contexts such as admin, AJAX, REST, feeds, previews, searches, and similar endpoints.
Rules to prevent caching personalized or dynamic content 
* Exclude logged-in users (recommended; enabled by default). 
* Exclude URLs (one per line): 
 – Prefix rules (e.g. <code>/checkout</code>) 
 – Wildcards (e.g. <code>/cart*</code>) 
* Exclude by cookies (useful for ecommerce/session cookies). 
* Exclude by user agent (bots, scanners, special clients). 
* Bypass query parameter: when present (e.g. <code>?nocache=1</code>) caching is bypassed for that request. 
* Optional 404 caching (disabled by default; enable only if your 404 output is safe and static).
Tools and automation 
* One-click Purge cache tool in WP Admin. 
* Optional auto-purge when posts are updated (useful for content sites that publish/edit frequently).
Security and WordPress.org compliance 
BrenWP Cache is built to meet WordPress.org review expectations: 
* Capability checks + nonces for state-changing admin actions 
* Strict sanitization/validation of input and late escaping for output 
* Cache directory is constrained under <code>wp-content/cache/brenwp-cache</code> with path safety guards 
* Cached HTML is served as a full document (not escaped) and is integrity-verified with an HMAC signature; unsigned/invalid cache is treated as a miss 
* No obfuscation, no remote calls, no dangerous execution patterns
<h3>Recommended usage (important)</h3>
A full-page cache should never store private/personalized output. For best results: 
* Keep “Exclude logged-in users” enabled. 
* Add exclusions for dynamic endpoints such as: 
 – <code>/checkout</code>, <code>/cart</code>, <code>/my-account</code> (WooCommerce) 
 – Any pages that show user-specific data, pricing, currency switching, or session-based content 
* If a page sets cookies or sends <code>Cache-Control: private/no-store/no-cache</code>, it will not be cached.
Developed by Brendigo LTD.
<h3>Privacy</h3>
BrenWP Cache does not collect personal data and does not send telemetry. Optional Preload requests only your own site URLs. 
Caching is file-based on your server, stored under your WordPress content directory, and controlled by your configuration.

BrenWP Cache

Lightweight, privacy-friendly file-based page caching with a modern, strictly scoped WP Admin UI.

Jose Mortellaro

Update Page Cache flushes and generates again the page cache.
The actual version supports <a href="https://wordpress.org/plugins/w3-total-cache/" rel="ugc">W3 Total Cache</a>, <a href="https://wordpress.org/plugins/wp-fastest-cache/" rel="noopener ugc">WP Fastest Cache</a>, <a href="https://wordpress.org/plugins/wp-super-cache/" rel="ugc">WP Super Cache</a>, and <a href="https://wordpress.org/plugins/wp-optimize/" rel="ugc">WP Optimize</a>.
When you modify a page and save it, usually caching plugins automatically clear the cache of that page, but you need to visit again the page to generate again the cache.
Update Page Cache adds a button on every single page, post and custom post type that you can click to automatically clear and regenerate the cache of that page. Be careful, you will not see the button if you have Fullscreen mode active.
When you edit a single page, if you click on the “Update Page Cache” button, the cache of that page will be automatically updated without the need to visit that page.
In the main settings you can set for each post types if the plugin should automatically clear the page cache when that single post type is saved.
You can also decide which page caches should be updated after saving a specific post type. 
In the example shown in the screenshot of the main settings, when a single blog post is saved Update Page Cache updates the cache of the blog page and homepage. When a contact form is saved, Update Page Cache updates the cache of the page Contact.
<h3>Backend Speed Optimization</h3>
Is your dashboard slow? We optimize admin performance by improving queries and reducing plugin load. 
Read <a href="https://josemortellaro.com/backend-speed-optimization/" rel="nofollow ugc">Backend Speed Optimization Service</a> for more information.

Update Page Cache

I'm the author of this plugin, but I'm also a user. I'm installing it on the websites where I use caching plugins and I love it. I love my own plugin, I think it does what is written in the description and make save time. So even though I'm the author, I give it 5 stars.

Author and user

Update Page Cache flushes and generates again the page cache. Compatible with W3 Total Cache, WP Fastest Cache, WP Super Cache, WP Optimize.

BrenWP Cache vs Update Page Cache