-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new_audit: flag if a resource is both preloaded and lazy-loaded #9516
Comments
Sounds good to me. We don't know how common this is, but seems nice to have as a doublecheck. @yoavweiss can you think of any valid reason to preload something that's set to loading=lazy? |
Not really. Seems fair to warn against it |
Does the same principle apply on a JS resource which is pre-loaded but at the same time uses 'defer'? Live example on https://groceries.asda.com/
|
I wouldn't think so @rockeynebhwani. |
Consider:
This is probably a developer mistake as it indicates both to preload and to defer the loading of the content which is contradictory, should Lighthouse care to warn in this case?
Currently lazy-loading is only applicable to
<img>
and<iframe>
but I suspect other things will be added in the future, perhaps background-images, videoposter
, SVG<image>
and<portal>
.The text was updated successfully, but these errors were encountered: