Mike Bricknell-Barlow

<p>This plugin helps to increase site speed, and helps to improve scores in Google’s Pagespeed Insights tool by addressing the common recommendation “Serve next-gen image formats”.</p>
<p>For the best speeds, Google recommends using new image formats such as .webp, which offer smaller file sizes than common formats such as .jpg or .png with no visible loss in quality. However, not all internet browsers support the .wepb image format, so only using that format would result in broken images in older browsers.</p>
<p>This plugin addresses that problem, and allows your site to use .webp images when it can. This plugin will convert images from .jpg or .png automatically, and save .webp versions of the image alongside the original. When a user visits the site in a compatible browser, they will be shown the .webp versions of all images, making your site load faster and improving your scores in Google Pagespeed Insights. Users on older browsers that aren’t compatible with .webp images will be shown the .jpg or .png versions of the images instead.</p>
<p>When first installing the plugin, run the Bulk Converter to convert all your existing images. See the Installation section for instructions.</p>
<p>After installation, any .jpg or .png image uploaded to the Media Library will be automatically converted.</p>
<h3>Settings</h3>
<ul>
<li>
<p>Conversion quality – Controls the level of compression on the generated .webp images. The lower the value, the smaller the file size of the generated images, but the more chance there is of a visual degradation of quality. The quality value to be entered is a percentage – by default, this is set at 80%. Most users won’t need to change this.</p>
</li>
<li>
<p>HTML Output Buffering – This allows the plugin to perform a find-and-replace on the HTML that WordPress has generated for output to the browser to replace image tags. This tends to perform the image tag replacement more reliably, but can cause issues with some themes. Users are advised to have this setting turned on, but they should check that the site is displaying as it should, and turn this option off if any issues arise.</p>
</li>
<li>
<p>Exclude pages from HTML output buffering – To specify pages that should be excluded from the HTML Output Buffering settings</p>
</li>
<li>
<p>Lazy loading – This improves the site speed further by not loading images that are further down the page until the user has scrolled down to them. This saves time downloading images that the user hasn’t got to yet, or might not get to at all. Users are advised to have this setting turned on, but they should check that the site is displaying as it should, and turn this option off if any issues arise.</p>
</li>
<li>
<p>Exclude image classes from lazy-loading – To specify images, by class name, that should not have the lazy-loading applied</p>
</li>
</ul>
<h3>Developers</h3>
<p>If using Simple Webp Images with your custom themes or plugins, there’s a couple of filters you can use, as below.</p>
<ul>
<li><code>simple-webp-images-exclude-from-output-buffering</code> filter</li>
</ul>
<p>Use this to exclude pages or posts from the HTML output buffering via <code>apply_filters</code>, using any critera you need. Call the filter, run any checks you need, and return ‘true’ to exclude the current page or post from the buffering.<br />
Example:</p>
<pre><code>apply_filters( 'simple-webp-images-exclude-from-output-buffering', 'exclude_page_with_id_100_from_output_buffering' );
function exclude_page_with_id_100_from_output_buffering( $is_excluded ) {
    if( get_the_id() == 100 ) {
        return true;
    }

    return false;
}
</code></pre>
<p>The example code could be placed in your <code>functions.php</code> file.</p>
<ul>
<li><code>simple-webp-images-exclude-from-lazy-loading</code> filter</li>
</ul>
<p>Use this to exclude pages or posts from the image lazy loading via <code>apply_filters</code>, using any critera you need. Call the filter, run any checks you need, and return ‘true’ to exclude the current page or post from the lazy loading.<br />
Example:</p>
<pre><code>apply_filters( 'simple-webp-images-exclude-from-lazy-loading', 'exclude_page_with_id_100_from_lazy_loading' );
function exclude_page_with_id_100_from_lazy_loading( $is_excluded ) {
    if( get_the_id() == 100 ) {
        return true;
    }

    return false;
}
</code></pre>
<p>The example code could be placed in your <code>functions.php</code> file.</p>


Simple Webp Images

Generates webp images from uploaded images, and outputs webp images in content in compatible browsers. Optionally provides lazy-load functionality.

John Teague

<p>Autoptimize is a popular performance plugin for WordPress. Among other features, Autoptimize creates and builds cached versions of optimized asset files descreasing page loading times.</p>
<p>But left unchecked, those cached files can become very large. That can slow page loading, increase web server load, and use unuecessary amounts of disk space.</p>
<p>This companion plugin provides a way to set the maximum allowable cache file size for your site and, if that size is exceeded, automatically clears your Autoptimize cache and allows it to rebuild itself. That’s good.</p>
<h3>Plugin Settings</h3>
<ol>
<li>Navigate to WordPress admin dashboard -> Settings -> Autoptimize Cache Settings</li>
<li>Select from one of the available <code>Maximum cache file size</code> options from the select menu and press the <code>Save Changes</code> button</li>
<li>Please note: You obviously must have Autoptimize plugin installed for this plugin to work</li>
</ol>
<h3>Roadmap</h3>
<ul>
<li>Release first stable versions</li>
<li>Add a time based WP_Cron setting that will clear cache every few days, week, month, etc.</li>
<li>Internationalization improvements</li>
</ul>


Autoclear Autoptimize Cache

My finger can now rest from clicking "save changes and empty cache" in autoptimize.

Great! Thanks

Automatically clear Autoptimize cache if it grows larger then the allowed option.

Simple Webp Images vs Autoclear Autoptimize Cache