Wordpress LScache Plugin: ANY Images
Last Updated on: Wed, 15 Apr 2026 00:00:02 Following on from the previous thread concerning .webp images, Im now having problems with optimising ANY images via Litespeed. Im in the Image Optimisation section, where it says send optimisation request and occasionally but not always, theres an option to pull images. Im either getting a Message from LiteSpeed image server: Notified images not pulled yet. error, or on clicking the Send Optimisation Request Im getting a Failed to post via WordPress: Previous requests that optimized but not pulled: 16 error. Im going to make a quick suggestion here: This Litespeed cache system shows some excellent speeds but to configure anything within it is a nightmare ? Ive never camped out in a support forum so much. Ive already mentioned that there is something terribly wrong with the CSS and JS minifying too, and that together with the image optimisation ? which only works when the next cronjob activates, means that you need to wait for WordPress to perform the image optimisations rather than doing it yourself and seeing immediate results. So to the suggestion: Would it be possible to take WP cron out of the loop and be able to see immediate results? There is some issues as I can see on several installations that I have on Pro Medium server at https://www.proisp.no , they inform that there seems to be an issue with the LiteSpeed image server. I get The scheduled event, litespeed_img_placeholder_trigger . A quick workaround is to Destroy unfinished data and send new optmimization request if its urgent. BTW They have a Slack-group you should check into. Hi @simonskaar If it were not for the excellent speeds it achieves, and the fact that my host recommends them and dumps litespeed cache on all of their new websites, Id be long gone by now. Just woke up and found that all my images have now been optimised which is totally unrealistic actually ? its like waiting for the plumber to arrive. Hi, Apologize for the inconvenience you have experienced, we are always actively working on improvement. if you want to have quicker and faster pull , you can disable WP-cron , and create up your own cron with wget or curl command e.g. wget -q -O - https://your-domain.com/wp-cron.php?doing_wp_cron this way you can have a faster cron job be triggered instead of waiting for WP itself to perform cronjob. I will also talk with our developers to seek the possibility to make it more immediate. Best regards, Not meaning to sound dubious here, but optimising images should not be done via cronjobs in the first place, whether they be from WordPress or a real cronjob. As I said earlier, it seems to be working now, so Ill wait until I need to reset the settings back to default and then re-enter my own settings before I come back to complain about it. Hi, Well, in most of cases, PHP has run time limits , like 30 seconds or something , in particular for the resources-limited-shared-hosting . so the cron job is probably the most suitable and reasonable way to progressively pulling back image to avoid hitting max_execution time limits. Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference