Hi @lsphoto
The size of 229kB is WebP size. I guess you use picture tag method to display WebP, as it will not work for background images. It seems to be a case here.
You might consider using rewrite rules method as it would fetch background images as well. The only thing to have in mind is that it would not work with CDN/Cloudflare.
About the image quality issue, if it happens even when using Normal compression level, can you activate “Keep EXIF data” option in Imagify settings and let me know if it looks better?
If not, can you send us the problematic image (not optimized) so we could check it?
Best Regards
Hi, thanks for your reply !
If you mean by ‘tag method’ the <picture> method instead of make changes to .htaccess, yes, it’s the case. I don’t use CDN.
About the quality, I already keep the metadata (exifs). Where can I send you the picture please ? With a calibrated screen, I can see a big difference (I can imagine most people not, but photographer well…). As well with saturation (it’s a sunset), and with a (big) loss in details (sand, even two (far away) little persons are ‘blured’..
Tahnks for your support !
Hello @wp_media
Could you please give me the right mail to send you the image for quality loss ?
I’ve double checked with a test with you online tool, primary redimentionned to 1200px (big side) and compressed to 85% in Photoshop, and exported as sRGB jpg file.
When I do use of your “compare before/after”, it’s the same result, lack of details (shadows get faded..), loss of saturation are the biggest issues.
In Imagify, treated as “Normal”, with exifs.
(and so no other solution for background images?)
Thank you !
Hi @lsphoto
Thanks a lot for your patience!
Just in case you still didn’t, feel free to send this via contact [at] imagify.io and just send a reference to this thread so we could know what is it about.
Using this way for communication we usually get back to you much quicker.
Best Regards
