Wordpress LScache Plugin: LiteSpeed Cache image optimization vs WordPress default image optimization
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, correct me if Im wrong, but as far as I know, WordPress also performs image optimization by default to the image thumbnails. I think it only applies to the thumbnails, not to the original image. For example for JPG images when generating the different media sizes, WordPress uses the 82% quality setting, right? But then LiteSpeed Cache optimizes the images and thumbnails as well. Two questions: 1) Does LiteSpeed Cache turn off the default WordPress image optimization? 2) If not, should I turn it off to avoid double-optimizing image files? Hi, when you upload an image to WP , itself does not optimize image ,the main image remains same and that 82 is only apply to when it generates resized image or, thumbnails , this isnt exactly identify as image optimization so 1) , no , since they are not same thing 2) since there isnt a real optimization from WP , so this question doesnt form up. Ok, but on the LiteSpeed Cache Image Optimization ? [2] Image Optimization Settings tab, there is an option: WordPress Image Quality Control ? The image compression quality setting of WordPress out of 100. Recommended value: 82 Value range: Smaller than 100 What is this? Is this the level of the default WordPress image compression? Or is it the level of the LiteSpeed Cache image compression? You said that WordPress already applies the 82% quality for thumbnails, but then if LiteSpeed Cache applies the 82% quality again, wont it cause over-optimization? Hi, no , that is WP image quality control , is what you said in your first post , about WP resizing images , not LSCWP quality control Best regards, I see! So after WordPress core has applied the 82% quality setting to image thumbnails, then the LiteSpeed Cache plugin will not apply the 82% quality setting yet again? Hi, Correct, LSCWP has its own quality control value , you can choose lossy or lossless Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference