Hey @alriksson – thanks for your message and for suggesting us native lazyload! 🙂
We’re currently considering adding this feature but ShortPixel Adaptive Images(SPAI) needs its own lazyload implementation in order to be able to serve properly-scaled images.
Regards,
Alex
Thread Starter
Rookie
(@alriksson)
Okay, not fully understanding why but thanks anyway. Why can’t you just add loading attribute to the images once they are properly scaled?
SPAI’s lazyload script replaces the images’ URLs with placeholders. And only loads the images, at the proper size, when they are (about to be) visible.
From our perspective we could easily add that attribute but it would be completely useless 🙂
If you feel we’re missing something here please let me know.
Thanks,
Alex
Thread Starter
Rookie
(@alriksson)
hmm maybe you´re right. But how do you replace the placeholders? Same technic as lazyloading and why can not this we swapped to native for browser supported (chrome) and then fallback? Or am I missing something here?
lazyload script tends to be heavy for the rendering as well-meaning we have things to win on devices with less computing power (mobile) and 3G/4G networks.
We see a lot of gains since WP rockets dedicated lazy load plugin swapped to native.
@alriksson – SPAI needs lazyload to also figure out the right image size.
If it just used the native support then the images won’t be scaled but instead just optimized and served from CDN.
We’re fully into gains but I’m not sure what else we could do here…