Wordpress LScache Plugin: Optimized images to Quic.Cloud
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi I have already optimized images for my website with shortpixel plugin, is it possible to send them to quic.cloud without re-optimzing them with the cache plugin ? what would be the configuration ? This topic was modified 11 months ago by freddyee. Hi, you can send it as normal , the node will check if the image can be further optimized or marked it as previously optimized already and skip it Best regards, I wouldnt chose to optimize more, that can reduce quality, I need to send them as is. Right now the photos are optimized at a specific level(some photos more than others) with shortpixel. what would be the configuration in the cache plugin to send them to Quic.Cloud as is ? https://snipboard.io/oSf37e.jpg they are being sent as they are I still hasnt sent any image to Quic.Cloud, they are just optimized and converted to .webp format with shortpixel plugin. considering that I desire to keep them in .webp format and with the level of optimization of shortpixel, which should be the configuration in the cache plugin ? Hi, I dont understand ? the images have been already optimized by other plugin , you still want to optimize it again with our plugin or something ? No, I dont want to optimize them again, I just want to send them to Quic.Cloud as-is and for them to appear in .webp format on my website. Hi, then you need to run through the image optimization that provided by our cache plugin inn order to obtain the webp files best regards, So, Id need to re-optimize the images on the cache plugin ? that optimization would be over the original images or the optimized images by shortpixel ? what would be the configuration on here ? https://snipboard.io/1wWzLu.jpg toggle create webp version it will optimize whatever it sees in database , which is same what you see in Media page Hi @freddyee, if you dont mind, could you explain how you resolved this? I couldnt quite understand @CacheCrawlers answers.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference