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.

Raul P.

<p>HTML, CSS & JS optimization plugin for developers and advanced users. Note you need to look into the HELP tab after installing the plugin and manually configure it for your site. Each site is different, so the default recommendations may or may not work for you and you will need to test and find out how to adjust your settings.</p>
<p>Minification is done on the frontend during the first uncached request. Once the first request is processed, any other pages that require the same set of CSS and JS files will be able to reuse the same generated static CSS or JS file.</p>
<p>If your cache is growing significantly, this could mean one of your CSS or JS files is dynamic and changes on every pageview. In that case, you would need to add the file to the ignore list, else the cache would grow indefinitely (because obviously the original files themselves are dynamic and when you minify, the plugin sees a different file).</p>
<p>Kindly read the HELP section after installing the plugin, about possible issues and how to solve them.</p>
<h4>Additional Optimization</h4>
<p>I can offer you additional <code>custom made</code> optimization on top of this plugin. If you would like to hire me, please visit my profile links for further information.</p>
<h4>WP-CLI Commands</h4>
<ul>
<li>Purge all caches: <code>wp fvm purge</code></li>
<li>Purge all caches on a network site: <code>wp --url=blog.example.com fvm purge</code></li>
<li>Purge all caches on the entire network (linux): <code>wp site list --field=url | xargs -n1 -I % wp --url=% fvm purge</code></li>
</ul>
<h4>How to customize the cache path ?</h4>
<p>You need a public directory to store and serve minified cache files. If you need to customize the path and url, you need to edit your <code>wp-config.php</code> and add both <code>define('FVM_CACHE_DIR', '/absolute/path/to/example.com/your/public/directory');</code> and <code>define('FVM_CACHE_URL', 'https://example.com/your/public/directory');</code> .</p>


Fast Velocity Minify

But the new version is not as good as I expected. 

The complicated setting interface does not work from time to time.
Strange CDN settings(not work neither), supports that do not solve problems.

I want the old version back, please.

Was the best

Maximize GTmetrix, PageSpeed and enhance Web Vitals by minifying CSS/JS, lazy loading scripts, optimizing images, and improving load speed overall.

Simple Webp Images vs Fast Velocity Minify