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

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.

Snappy vs Purge Cache for CloudFlare