Web Guy

<a href="https://github.com/webguyio/snappy/issues" rel="nofollow ugc">💬 Ask Question</a> | <a href="mailto:webguywork@gmail.com" rel="nofollow ugc">📧 Email Me</a>
Caching for a snappier website.
When a WordPress page loads normally, it goes through:
<ol>
<li>PHP execution</li>
<li>Database queries (often 20-50+ queries)</li>
<li>Theme processing</li>
<li>Plugin execution</li>
<li>HTML generation</li>
</ol>
With Snappy file-based caching, it skips all that and just serves a static HTML file.
Estimates for performance improvement:
<ul>
<li>2x faster is conservative and achievable for most sites</li>
<li>5x faster is realistic for database-heavy sites</li>
<li>10x faster is possible for poorly optimized sites with many plugins</li>
</ul>
<h4>Advanced Version</h4>
Snappy is fully capable with its core caching capability, but if you want or need additional optimization and control, advanced settings are available at <a href="https://snappywp.me/" rel="nofollow ugc">snappywp.me</a>.
<ul>
<li>HTML, CSS, and JavaScript minification</li>
<li>GZIP compression</li>
<li>Lazy loading for images and videos</li>
<li>Video embed optimization (YouTube/Vimeo facades)</li>
<li>Font preloading</li>
<li>Database cleanup (spam, revisions, transients)</li>
<li>Automatic weekly database optimization</li>
<li>Cache preloading from sitemap</li>
<li>Defer JavaScript with exclusions</li>
<li>Critical CSS extraction and inlining</li>
<li>WordPress Heartbeat control</li>
<li>Resource hints (preload, prefetch, DNS-prefetch)</li>
<li>Browser caching headers via .htaccess</li>
<li>Security headers (X-Frame-Options, CSP, etc.)</li>
<li>Cloudflare integration with optimized settings</li>
<li>CDN integration with URL rewriting</li>
<li>Settings import/export</li>
<li>Self-hosted update system</li>
</ul>

Snappy

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.

Snappy vs BrenWP Cache