I see loading="lazy" on the images, so I think Lazy loading is working, or do you mean something else?
How to reproduce the issue?
EWWW IO doesn’t use loading="lazy". It uses the class lazyload, which it replaces with lazyloaded after loading the image and adds lazyautosizes if that option is enabled, along with manipulation of the sizes attribute.
What you see is likely done by WordPress core, because the LiteSpeed Cache setting for lazy loading is disabled.
Either way, this is a live site, and I couldn’t have it with missing images, so for now, the EWWW IO lazy loading setting is disabled.
I was hoping to get some guidance in troubleshooting this, because it’s only happening on this one site. I’m happy to temporarily enable lazy loading and capture the code, but I’ve compared it with other sites and it seems to be intact, just not working. Seems like it’s conflicting with something, but only when viewing cached pages, which is weird.
Where else should I be looking?
Plugin Support
qtwrk
(@qtwrk)
is this hapenning on home page ??
because on homepage it seems only 2 or 3 images loaded by CSS, rest are directly by html tag, not going through any lazyload ?
It happens on the home page when the EWWW IO lazy loading is enabled. Except the first IMG tag on the page, none of the images load.
When lazysizes is disabled, they occupy the correct amount of space, but show the inline placeholder image. When lazysizes is enabled, it’s like there’s nothing there.
Again, to clarify, EWWW IO lazy loading is now disabled. What I’m asking at this point is how I can isolate the problem, given that I’ve tested disabling page tuning and saw no difference, but the uncached page is correct.
