Lazy Load Error/Bug – It simply doesn’t work!

I have a bug or error with lazy loading in Foogallery Pro which I’m sure didn’t used to be the case. Version 2.2.44

This screenshot highlights the essence of the problem, with the conflicting code circled. Basically, every image is forced to loading=”eager”, despite my settings requesting lazy load. The conflicting code “lazy”:true is also circled.

Here’s the background information:

1. Lazy load is NOT disabled in my Foogallery global settings.
2. Lazy load IS enabled for each of my galleries at the gallery level.
3. Enable html cache IS disabled in the Foogallery global settings, as per your advice as I’m using a caching plugin (more information below)
4. My Foogallery images are served as WebP using Ewww Easy IO and this is working fine.
5. This is achieved by explicitly adding the path /public_html/wp-content/uploads/cache/ to EWWW as per their instructions for Foogallery specifically on this page.
6. Ewww Easy IO has its own Lazy Load feature at the CDN level. This error with Foogallery occurs regardless of if this setting is on or off.
7. My caching plugin is Litespeed cache. This Foogallery error occurs with this plugins own Lazy Load feature on or off. I am not using minify or combine of any JS with this plugin, but I am using JS defer.
8. I have no other plugins with any form of Lazy loading that might be causing a conflict.
9. Yes I’ve tried every combination I can think of, and I’ve cleared all my caches between each experiment.

This screenshot confirms how PageSpeed Insights throws this up as an error, as do other similar resources.

I’ll submit a pro support ticket too, as this is urgent.

Please help!

• This topic was modified 2 years, 10 months ago by Ray.
• This topic was modified 2 years, 10 months ago by Ray.
• This topic was modified 2 years, 10 months ago by Ray.

The page I need help with: [log in to see the link]