mi13

<p>Mi13 Cache is a simple and effective plugin for caching WordPress pages. It saves HTML pages as files and serves them on subsequent requests, significantly speeding up site loading.</p>
<p><strong>Key features:</strong></p>
<ul>
<li>Line-by-line caching of HTML pages.</li>
<li>Flexible settings: select which page types to cache.</li>
<li>Automatic cache clearing when content is updated.</li>
<li>Cache status displayed as an HTML comment at the beginning of the file.</li>
<li>Cache statistics: file size and number of files.</li>
<li>Security: access permission checks and filtering of system pages.</li>
<li>Compatibility with custom post types.</li>
</ul>
<h3>Usage</h3>
<p>After activation:</p>
<pre><code>Go to Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Mi13 Cache.

Configure the settings:

    Select page types to cache (home page, posts, pages, categories, archives, custom types).

    Set the cache lifetime (in seconds; default is 86 400 s / 24 hours).

    Clear the cache manually using the Clear Cache button (if needed).

Save the settings.
</code></pre>
<p>You can check the cache status in the page source code:</p>
<pre><code>Open the page source code (press Ctrl+U or right-click <span aria-hidden="true" class="wp-exclude-emoji">→</span> “View Page Source”).

Look for a comment at the very beginning of the HTML file, like this: <h3>Settings</h3>
Page types — select which content types to cache.

Cache lifetime — the interval in seconds after which the cache expires.

Clear cache — a button to manually clear all cached files.<h3>HTML comment format</h3>
</code></pre>
<p>The plugin adds an HTML comment with information to the beginning of each cached file: </p>
<h3>Limitations</h3>
<p>Caching does not apply to:</p>
<pre><code>authenticated users;

the admin panel;

404 pages;

search pages (?s=...);

RSS feeds (/feed/);

AJAX requests;

POST requests;

URLs with GET parameters (except paged for pagination).<h3>Troubleshooting</h3>
</code></pre>
<p>Issue: the cache is not created.<br />
Solution: make sure that:</p>
<pre><code>define('WP_CACHE', true) is present in wp-config.php;
WordPress has write permissions for /wp-content/cache/mi13-cache/.
</code></pre>
<p>Issue: pages do not update after editing.<br />
Solution: manually clear the cache on the settings page.</p>
<p>Issue: access permission error when clearing the cache.<br />
Solution: check file permissions in the cache directory.</p>
<h3>Security</h3>
<pre><code>Permission check (manage_options) before clearing the cache.

Caching disabled for authenticated users.

Exclusion of system pages (404, search, feed, etc.).

Use of the secure WordPress API for file system operations.<h3>Directory structure</h3>
Cached files are saved in: /wp-content/cache/mi13-cache/

Each file has the .html extension and a name corresponding to the page URL.
</code></pre>

mi13 сache

A lightweight plugin for line-by-line caching of WordPress pages. Speeds up site loading by saving static copies of pages.

Brendigo

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


BrenWP Cache

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

mi13 сache vs BrenWP Cache