codyarsenault

@kevinweber awesome! I think that did the trick. Thanks so much!

This actually only happens when I’m logged in and editing the post. I’ve been able to replicate it on a test site if you’d like me to provide the credentials to that?

Figured it out.

Any ideas? This is still happening.

I also get the following message in the “Responsive” section of the plugin: Your table has legacy responsive functionality. While it is still supported, enabling newer responsive system will override it. If this is not what you want, do not enable newer version.

However, I don’t see anywhere that I can enable the newer responsive system.

I ended up having to select more of the custom image sizes in the plugin to convert to retina. All working now.

The latest version of Firefox supports WebP however IE doesn’t. If you have the WebP option enabled in Cache Enabler your images should fall back to their original format for non-supported browsers.

Have you reached out to the developers of the Finale – WooCommerce Sales Countdown Timer & Discount plugin to see if it is compatible with caching plugins?

We cover this error in more detail here: https://www.keycdn.com/support/optimus/error-codes it is recommended to enable WP’s Debug feature to gather more information.

Thanks for passing this along. I will send this over to the developers to take a closer look at.

Cache Enabler is completely bypassed for logged in users. This is to avoid caching issues when an admin is making changes. I would recommend taking a look at other ways to optimize your WordPress site such as the ones mentioned in this guide: https://www.keycdn.com/blog/speed-up-wordpress

I will alert our developers about this. Can you please provide me with the website URL you are experiencing this issue on?

Can you try running the regenerate thumbnails plugin on an image that isn’t working and once the thumbnails have been regenerated try optimizing the image for WebP again with Optimus.

Can anyone experiencing this issue please provide their site URL as well as a screenshot of the error in Google Search Console?

Thanks for your feedback, I will pass this along to the developers.