Track lazyloaded images with JS above the fold #9
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Description
According to the 2022 Web Almanac, 9.8% of mobile pages with image-based LCP set loading=lazy on them. And 8,8% use custom lazy-loading.
The current snippet only tracks lazy-loaded images using the native
loading="lazy"
attribute. Hence, it's only useful for 52% of mobile pages using any lazy-loading approach on LCP images.Proposed solution
With this update, the snippet also tracks lazy-loaded images via JS, looking for "data-src" attributes.
I've also updated the return statement to return an array with all the lazy-loaded elements or
false
if no image above the fold was lazy-loaded.