I’ve used a ton of caching plugins during the life of this site, but Breeze stands out for being a simple and decently powerful one..


Breeze is the caching plugin made by Cloudways, a managed VPS hosting company. I’m pretty sure it’s intended use is on their servers, but it’s open source so anyone can use it on any host. It supports not only file-based caching in WordPress, but also offers Varnish integration to make your site extremely fast. You don’t need Varnish, as it has it’s own caching mechanisms if it detects the absence of Varnish.

What it can do

Breeze is an amazing combination of WP Super Cache, and Autoptimize. It has the simplicity of just enabling a few options, like WP Super Cache, but can also minify your CSS, Javascript, HTML, and inline Javascript and CSS. This means that instead of using two separate plugins: WP Super Cache for caching and Autoptimize for minifying, or W3 Total Cache which can become complicated pretty quickly, you can just use the Breeze plugin.

Quick Setup

To enable the plugin, all you need to do is install it, and check the “Cache System” checkbox. You can set how long the cache will live by default by changing the value in the “Purge cache after” textbox. Then, check the checkboxes for what you want to minify. I recommend trying CSS first, and if it doesn’t break your site, then Javascript, and if you’re site still looks normal, then activate HTML. Finally, if you’re site still looks normal and functional, then you can enable the inline CSS and inline Javascript options. However, be warned that this can break your website, depending on how it’s built.

Other settings

Under the advanced settings tab, you can specify what pages you don’t want to cache(i.e. the login page), whether or not to group files, the CSS to exclude, the Javscript to exclude, move Javascript to the footer, and Javascript that you would like to defer. I recommend just enabling the options to group files, and leaving everything else the default, unless you have a login/registration plugin, in which case, exclude those URLs from being cached.

You can also clean up your WordPress database in the Database tab. Simply select what you’re fine with deleting, and press “Optimize”. I personally don’t like deleting post revisions because I think I might need them some day, although that has never happened. From my understanding, nothing bad happens from removing transients from the database, but whenever you remove anything from the database, there is a chance you might delete something you want.

Who is this for?

I would recommend this for people who need more than just WP Super Cache, but don’t want the complexity of W3 total cache.