andreyk

<p>On first request to a given URL whole html code of a page is being stored in<br />
the SQLite database. On next requests to the same page WordPress core will<br />
not be loaded at all but the content of a page will be retrieved from the<br />
the SQLite storage therefore duration of PHP execution decreases in dozen<br />
of times.</p>
<p>Many sites on the same webserver may use common SQLite storage.<br />
Compatible with WordPress Multisite. Requires PHP SQLite PDO.</p>
<p>In comparison with plugins generating static html pages this plugin does not<br />
create multiple directories and html files but stores all generated pages<br />
in one file. Moreover, many wordpress sites on the same webserver may use<br />
common SQLite storage. Keeps 404, 301, 302, 304 HTTP statuses, optionally<br />
supports ETag, Expires, Content-Length, Content-Type (with charset) headers.</p>
<h4>As the cache script doesn’t load the WordPress core where does it save it’s settings?</h4>
<p>To get the plugin working you need to define the SQLite storage location in<br />
the <code>index.php</code> of the wordpress installation directory (note, not in wp-config.php<br />
but index.php). Besides of the SQLite file, this directory contains general<br />
settings file (compression setting) and a subfolder for per domain settings.<br />
In the admin area (plugin setting page) and to remember after deactivation where<br />
the cache located, <code>litecache_path</code> WordPress option is used.</p>
<h4>How the plugin handles URLs with and without `www.` prefix?</h4>
<p>The presence of <code>www.</code> prefix is defined in <code>Settings</code> – <code>General</code>.<br />
The plugin stores <code>with_www</code> parameter in <code>domains/yourdomain.ini</code> file in the<br />
cache directory and redirects requests correspondingly; these redirects are<br />
being processed before cache usage.</p>
<h4>Is it WordPress Multisite compatible?</h4>
<p>Yes, but for subdomains mode only (blogname.example.com), not for<br />
example.com/blogname. A superadmin of a multisite network has access to<br />
the first setting form (cache location), blog admins have access to the<br />
second form and purge form.</p>


SQLite Cache

Provides SQLite cache storage that applied before WordPress core load. Doesn't create multiple html files but stores all pages in one file.

enomoto celtislab

<p>This plug-in stores the Page HTML / REST json data that dynamic WordPress blog has been generated as a output cache by SQLite. After the cache, it can respond to the request to the ultra-high speed by using a cache without starting the WordPress of processing.<br />
In the case of REST API, caching is also performed for internal requests made by logged-in block editors, etc.</p>
<h4>Simple Setup</h4>
<ul>
<li>Enable the cache, select the cache expiration.</li>
</ul>
<h4>Cache exclusion condition</h4>
<p>Pages</p>
<ul>
<li>Login user</li>
<li>Home/Front_page, Fixed Page, Post, Custom Post and WP embedded content card only. Other than this page does not cache.</li>
<li>Page you want to exclude from the cache, you can specify from the edit screen of the meta box.</li>
<li>Pages that are protected by a password does not cache.</li>
<li>PHP error (excluding E_NOTICE, E_STRICT, E_DEPRECATED) occurred page does not cache.</li>
</ul>
<p>REST API</p>
<ul>
<li>REST method is other than GET or OPTIONS</li>
<li>REST no data response</li>
<li>REST route endpoint you want to exclude from the cache, you can specify from the edit screen of the meta box.</li>
<li>REST error response</li>
<li>PHP error (excluding E_NOTICE, E_STRICT, E_DEPRECATED) occurred page does not cache.</li>
</ul>
<h4>Cache Clear</h4>
<ul>
<li>Clear the cache of automatically corresponding post in the articles and editing changes and the like of the comment.</li>
<li>The cache is a plugins and widgets such as a change is not clear. If you make these configuration changes, etc., should be cleared to use “Cache Clear” button.</li>
</ul>
<h4>Log</h4>
<ul>
<li>When you activate the log, you can easily check the behavior and execution time of the cache. (slower only a little)</li>
<li>SQLite database keeps logs for one week.</li>
</ul>
<h4>To further speed-up</h4>
<p>Page cache processing of this plugin is processing in PHP and SQLite.<br />
You can also use a faster Expert mode. To use Expert mode you need to edit ‘php.ini’ and add auto_prepend_file.<br />
Or you can edit the .htaccess file and use mod_deflate and mod_expires or mod_pagespeed etc to make it faster.<br />
If you do .htaccess edit, edit from the well studied. Do not forget that you back up your .htaccess file.</p>
<p><a href="https://wordpress.org/plugins/plugin-load-filter/" rel="ugc">plugin load filter</a> is also recommended for speed you do not use the cache.</p>
<p>For more detailed information, there is an introduction page.</p>
<p><a href="https://celtislab.net/en/wp-yasakani-cache/" title="Documentation" rel="nofollow ugc">Documentation</a></p>


YASAKANI Cache

It's good for cheap and low performace host / shared hosting server :). Definitely better than W3TC.

Many thanks to the developer!

Simple to use yet powerful

Simpler but faster or equal to other cache plugins. Especially on slow servers.


Simple and efficient

Easy to use and speeds up your site without any effort.

Great little cache plugin!

Simple ! Easy !! Ultra-high-speed !!!. Definitive edition of the page cache. And Bot and Security Utility.

SQLite Cache vs YASAKANI Cache