WordPress automatically adds Lazy-Loading to all images, whether the specific property is toggled in Cwicly or not.
We have found ourselves in quite a few situations where we needed to deactivate this automatic feature (with a code snippet), thus explaining why Cwicly does provide this property if you manage Lazy-Loading yourself.
The more I dig into Cwicly the more I think need to be created a more indepth documentation that could include a lot of the tips and philosophy/principles you put in place. Some are expressed in this discourse some in videos (including your lives), which is not always easy to find when in needs. I realize it is not so easy to put in place as a lot has to do with principles of css rather than directly Cwicly.
Agree or could even come as a setting in order to use it that would take control of WP lazyloading as, as it is, this setting can’t been used.
And yes the library of snippets and stylesheets is exciting!
automatic lazy load is stupid, because the photo that is in the initial viewport can’t have lazy load it’s supposed to have the opposite, i.e. preload like something!
lazy load applies to everything below the scrolling screen.
So, considering that we can use WP lazyload, what about an option to disable lazyload for an image by adding loading=“eager” instead of “lazy”? For instance for images above the fold.
It works by manually adding an attribute, but a shortcut would be nice
