Is your feature request related to a problem? Please describe.
When a bulk optimization is started, Imagify starts with the newest upload and progresses towards older ones. Well, at least 2.0 seemed to do so, I don't know about 2.1's async bulk optimization. Bulk optimization can take a loooong time (if you have many images). So uploading a new file seems to have it queued at the end, which can take a loooong time until it's optimized.
The "issue" I see here is that we do this for user experience, well let's be honest, mostly for SEO purposes. So not having a newly image optimized until some bulk job is done means that Google would get the version of images that WordPress generated and well this "could" hurt SEO. Certainly it loses you points on Pagespeed (because Google does not seem to care if the JPG is actually smaller than the webp, it still wants "modern" file formats).
Describe the solution you'd like
When a new file is uploaded, the job to optimize said file should be priorized, i.e. be put at the beginning of the queue. So the newly uploaded file gets optimized first. Or rather, next, when the system would take the next file.
Describe alternatives you've considered
I have tried to click the optimize button for newly uploaded images manually but it does not seem to work. After it says "Optimizing..." forever, it just reverts to the "Optimize" button. I'd assume that is the queue of bulk image optimization then.
Is your feature request related to a problem? Please describe. When a bulk optimization is started, Imagify starts with the newest upload and progresses towards older ones. Well, at least 2.0 seemed to do so, I don't know about 2.1's async bulk optimization. Bulk optimization can take a loooong time (if you have many images). So uploading a new file seems to have it queued at the end, which can take a loooong time until it's optimized.
The "issue" I see here is that we do this for user experience, well let's be honest, mostly for SEO purposes. So not having a newly image optimized until some bulk job is done means that Google would get the version of images that WordPress generated and well this "could" hurt SEO. Certainly it loses you points on Pagespeed (because Google does not seem to care if the JPG is actually smaller than the webp, it still wants "modern" file formats).
Describe the solution you'd like When a new file is uploaded, the job to optimize said file should be priorized, i.e. be put at the beginning of the queue. So the newly uploaded file gets optimized first. Or rather, next, when the system would take the next file.
Describe alternatives you've considered I have tried to click the optimize button for newly uploaded images manually but it does not seem to work. After it says "Optimizing..." forever, it just reverts to the "Optimize" button. I'd assume that is the queue of bulk image optimization then.
Additional context n/a