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.

Web Guy

<p><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></p>
<p>Caching for a snappier website.</p>
<p>When a WordPress page loads normally, it goes through:</p>
<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>
<p>With Snappy file-based caching, it skips all that and just serves a static HTML file.</p>
<p>Estimates for performance improvement:</p>
<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>
<p>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>.</p>
<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>


mi13 сache vs Snappy