Milan Dinić

<a href="http://blog.milandinic.com/wordpress/plugins/purge-cache-for-cloudflare/" rel="nofollow ugc">Plugin homepage</a> | <a href="http://blog.milandinic.com/" rel="nofollow ugc">Plugin author</a> | <a href="https://shop.milandinic.com/downloads/purge-cache-for-cloudflare-plus/" rel="nofollow ugc">Premium Version</a> | <a href="http://blog.milandinic.com/donate/" rel="nofollow ugc">Donate</a>
Purge Cache for CloudFlare is a simple plugin that uses CloudFlare® API to purge cache of full HTML pages when a new post is made.
This free version is only indended for basic usage. If you want to use it in full capacity, consider buying <a href="https://shop.milandinic.com/downloads/purge-cache-for-cloudflare-plus/" rel="nofollow ugc">premium version</a>.
It works by purging front page, post’s page, and main RSS feed. This should work for most sites. However, there are of filters, actions, and methods that provide full customizability and extensibility.
Note that this plugin also sets cache to 30 minutes for all frontend pages. This means that if you use default option in CloudFlare, it tells them to revalidate page cache after that time, so it means that cache for any page expires on CloudFlare servers after that time.
You can change this limits by using filters from you code. If you want user interface in your admin, use <a href="https://shop.milandinic.com/downloads/purge-cache-for-cloudflare-plus/" rel="nofollow ugc">premium version</a>.
You should create new CloudFlare page rules to set proper caching. It is your responsibility to set this properly.
First page rule should exclude certain paths from caching. Recommended value for this is <code>wp-</code>. This excludes admin pages and default <code>.php</code> pages. Example of URL pattern: <code>*example.com/*wp-*</code> This value can also set via filter or via admin in <a href="https://shop.milandinic.com/downloads/purge-cache-for-cloudflare-plus/" rel="nofollow ugc">premium version</a>.
Second page rule should sets caching. You need to set “Custom caching” to “Cache everything”. Recommended value for “Edge cache expire TTL” is default, “Respect all existing headers” which means that CloudFlare revalidates after 30 minutes, while for “Browser cache expire TTL” is also 30 minutes. Example of URL pattern: <code>*example.com/*</code>
This plugin is on <a href="https://github.com/dimadin/purge-cache-for-cloudflare" rel="nofollow ugc">GitHub</a> too.
Purge Cache for CloudFlare is in no way affiliated with CloudFlare. It is only using CloudFlare API to purge page cache of certain URLs. 
CloudFlare is registered trademark of CloudFlare, Inc.

Purge Cache for CloudFlare

Simple full HTML page cache purger for CloudFlare.

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.

Purge Cache for CloudFlare vs BrenWP Cache