Wordpress LScache Plugin: Optimize latest images, first?
Last Updated on: Wed, 15 Apr 2026 00:00:02 Is there any way to prioritize image optimization? I have a client with a news/blog website from early 2000s. Weve been on the LiteSpeed server for nearly 2 weeks now and were only 41% done with image optimization. While many of the older images have already been optimized with the previous optimizer, the image optimization crawler has A LOOOOOONG way to go to catch up to the most recently uploaded images which havent been optimized at all. Is there any way to prioritize the optimization of the latest uploads? In all honesty, with the small amount of folks who even look at the older content, it really isnt optimal to optimize the older images first. It makes sense to me why itd naturally crawl through from the beginning to end (oldest to newest), but that really doesnt make sense for the majority of the use cases out there. Any ideas? Hi, it is doing from newest to oldest if you check the source code https://github.com/litespeedtech/lscache_wp/blob/30b85ae31fe407c2eb4f8dfa6c94e86166a16a98/src/img-optm.cls.php#L140 you will see it queries from newest to oldest Best regards, I was actually running through the recent files (uploads/2021/10) and noticed that there were .webp and .bk.jpg files, but that only a small fraction was actually touched. Its most likely that I havent stumbled upon the proper info page on how to update/restart/fix this. Or, more likely, that I have a misunderstanding of what some of the functionality actually does. So, can you recommend what my next step should actually be, to reset the starting point? Heres a screenshot of: $ wp litespeed-image status Im sorry ? the screenshot shows it has optmed like 40% of your images already yeah, but its skipped over everything uploaded after the images optimization was started. yes , you need to wait for current batch (already gathered data ) finishes , and then it will gather again the ones newly uploaded e.g. you have 1000 images so far , it gather images number 500 ? number 1000 , and is running optm , then you upload another 500 images , lets say number 1001 to 1500 , these 1000-1500 wont be touched , until number 1000 to number 1 are optimized will clicking on Destroy All Optimization Data restart the process from the most recent uploads? yes , but its not exactly a good idea just for doing this ? maybe you should just wait it out ? that would be my inclination (waiting it out), but this site has several editors/contributors. theyre typical folks, with limited understanding on how this works. bottom line, theyre losing money with every 2-5mb image that theyre uploading. the homepage is the only page that they really care about, because of all of the obvious reasoning behind that. ?I wish there was a middle ground solution. for the time being, Ive upped their quick.cloud to 2000/pull and their quota to 20,000 images. hopefully this will resolve this for them faster. Off question, but does image optimization convert 300dpi to 72dpi? Today, I discovered that theyve been uploading 300dpi resolution images :/ No, it wont resize images. whatever pixel it has before, will remains after
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference