Running Cache Enabler + Breeze

Cache Enabler is a lightweight page caching plugin. This means a static HTML page is generated, saved to the server disk, and then delivered to your visitors instead of having to generate that page on each request. Currently this plugin doesn’t add or modify the Cache-Control and Expires response headers, which are responsible for browser caching.

To set these I’d recommend checking out this Fix Leverage Browser Caching Warning article.

The Cache Enabler plugin shouldn’t be used in conjunction with another page caching plugin.

Thank you Corey for your reply. I have disabled Breeze and added both of those to the htaccess files. Tests results are promising.

Can Cache Enabler be used in conjunction with Autoptimize? We use it to combine and minify js + css.

Hey Corey, I have done some testing and it looks like manually enabling cache-control and expires does get rid of the pagespeed warnings but TTFB slowed way down using just this method. I can only surmise that Breeze also add some other benefits to getting TTFB to as low as it can go.

I have confirmed the higher TTFB using both GTMetrix and Webpagetest. Odd but the results are clear in my testing.

Any other ideas?

I should follow up on this. How can I use Cache Enabler to just display Shortpixel-created webp files without using Cache Enabler caching so I can run Breeze as well?

Yes, the Cache Enabler plugin works perfectly with Autoptimize. The Cache Enabler is only able to deliver WebP images because it creates a separate cached page that contains the WebP images.