Fumiki Takahashi

Hametuha INC.

<p><a href="https://cloudflare.com" rel="nofollow ugc">CloudFlare</a> is a popular CDN service. They caches static files like <code>.jpg</code>, <code>.css</code> or <code>.html</code>, but they doesn’t cache dynamic pages generated by WordPress without <a href="https://www.cloudflare.com/features-page-rules/must-use-page-rules/" rel="nofollow ugc">Page Rule</a>.</p>
<p>Once Page Rules are set, for exmple, <code>https://examle.com/article/*</code>, every single page will be cached(of course, your permalink structure should be like <code>https://example.com/article/2019/01/01/POST_ID</code>).</p>
<p>This plugin <strong>hamecache</strong> provides cache control feature. If you update your article, hamecache automatically flush related caches  on cloudflare edge location.</p>


hamecache

Page cache plugin by Hametuha. Use cloudflare for distribution.

TMM Technology

<p>Visits website pages to warm (create) the cache if you have any caching solutions configured.</p>
<h3>Settings</h3>
<ul>
<li>Configure cache warming entry points and the depth of the warming;</li>
<li>Add all public site posts as entry points;</li>
<li>Add entry point sites sitemaps as entry points;</li>
<li>Select which types of assets to load, with 4 checkboxes: scripts, styles, images, fonts;</li>
<li>Set custom URL params (?foo=bar);</li>
<li>Set custom user agent;</li>
<li>Set custom request headers;</li>
<li>Set custom cookies;</li>
<li>Set connection timeout;</li>
<li>Set speed limit (pages to visit per minute);</li>
<li>Autorun Interval: to run the warming each N minutes;</li>
<li>Exclude pages (by substring or regex);</li>
<li>Rewrite URLs to HTTPS;</li>
<li>Visit pages second time without custom URL params (if they are set);</li>
<li>Warm-up posts (on their publication and edit (Can be seen in Logs -> Triggered)):
<ul>
<li>Set custom posts warming interval.</li>
</ul>
</li>
<li>Use object cache for tree storage, when it’s available.</li>
</ul>
<h3>Additional</h3>
<ul>
<li>Adds a graph to your dashboard with page load time before and after the warming (2 lines) per day.</li>
<li>Cleans up Action Scheduler log after itself (older than 30 days for failed actions, and older than 2 days for completed actions).</li>
</ul>
<h3>External services</h3>
<ul>
<li>Connect to paid service for warming from external global servers.</li>
</ul>
<h3>Run from code</h3>
<ul>
<li>Start: <code>\Cache_Warmer\AJAX::start_warm_up( false );</code></li>
<li>Stop: <code>\Cache_Warmer\AJAX::stop_warm_up( false );</code></li>
</ul>
<h3>Run from WP CLI</h3>
<ul>
<li>Start: <code>wp cache-warmer start</code></li>
<li>Stop: <code>wp cache-warmer stop</code></li>
</ul>
<h3>Required PHP extensions</h3>
<ul>
<li>json</li>
<li>simplexml (optional)</li>
</ul>
<h3>Bug reports / Questions / Suggestions</h3>
<p><a href="mailto:wp@tmm.ventures" rel="nofollow ugc">wp@tmm.ventures</a></p>


Cache Warmer


Developer is helpful and responsive.If you have a sitemap, click the option for this, set depth to 1, decide your update interval (match it to the default cache expiration time) and you're good to go.I use this alongside NGINX page caching and Redis object caching.


Does the job!

Visits website pages to warm (create) the cache if you have any caching solutions configured.

hamecache vs Cache Warmer