Benjamin Intal

Thanks for the report @christinablust! Glad it’s working now!

Yes this is expected behavior. There’s a chance that optimized image results in a bigger filesize especially when Cimo is set to only optimize without any resizing settings. This doesn’t happen a lot, but we noticed it really depends on the image and the quality setting (by default we set it to 80% quality), there’s a small overlap between the JPG and WEBP compression algorithms where at just the right image, the JPG can still have a smaller filesize. This may happen more if the image was already optimized prior to uploading. In those scenarios where the resulting WEBP file is bigger, Cimo just lets the original image go through.

However, we are working on what we call “smart optimization” that would further increase optimization rates and would visually yield the best optimized version.

Hey @lincolncristiano , how are you performing the image upload in WooCommerce? What steps are you doing in order to upload an image? I want to replicate how you’re doing it

Thank you for reporting back that it works!

I would think that more or less it should work because Cimo mostly works during the uploading process.

You would have to make sure that other features should not overlap, or you might get unexpected results. This applies more for the premium features of Cimo that might have some overlaps, for example LQIP images.

Hey @alyxp, @junior-mint and @christinablust version 1.2.3 fixes some issues with dropped images not being converted and optimized. Please update to version 1.2.3 and see if that fixes the issue!

Hey @btetraulttpc version 1.2.3 fixes some issues with dropped images not being converted and optimized. Please update to version 1.2.3 and see if that fixes the issue!

In 1.2.1 we added this: “New: If the resulting optimized image is bigger than the original image, the image is now skipped and the original image is kept.” I’m thinking it’s possible this is what’s causing the issue.

Would you be able to check whether the optimized file you uploaded while using 1.2.0 resulted in a larger webp file? Starting 1.2.1, when this happens we halt the conversion if it resulted in a larger image and the original one is uploaded instead.

If you can confirm this is happening, you can decrease the quality for the conversion, right now we have it set by default to 80% quality. But you can decrease it to 70%.

Hey @cbdgum, we would appreciate it if you can let us know what stopped working for you. I’m sure we can quickly fix this with an update. No need to do a 1-star rating, especially for something that worked perfectly but now just encountered a bug. Version 1.2.2 has been out for a month and we have not gotten reports similar to yours.

You can also download previous versions of Cimo from our plugin page, scroll down a bit and under Advanced Options you should see a dropdown with all the older versions available to download: https://ww.wp.xz.cn/plugins/cimo-image-optimizer/advanced/

A new plugin like ours have a few ratings, and a 1-star rating really hurts our visibility and standing. I do not believe a bug would warrant such a bad rating.

Some questions:

1. What version did you upgrade from?
2. What action did you perform that stopped working?
3. Which page were you in when you uploaded the image?