Distance-from-viewport thresholds #Īll images that are above the fold-that is, immediately viewable without scrolling-load normally. It would likely be fetched with a high priority in this case anyway, so this combination should not really be needed nor used. Note that an image with loading="lazy" and fetchpriority="high" will still be delayed while it is off-screen, and then fetched with a high priority when it is nearly within the viewport. If you want to increase the fetch priority of an important image (for example the LCP image), then Priority Hints should be used with fetchpriority="high". eager just implies the usual eager queueing browsers use by default. It does not imply that the image is loaded any quicker than another image without the loading="eager" attribute.īrowsers prioritize resources based on various heuristics, and the loading attribute just states when the image resource is queued, not how it is prioritized in that queue. The eager value is simply an instruction to load the image as usual, without delaying the load further if it is off-screen. Relationship between the loading attribute and fetch priority # Images that are highly likely to be in-viewport, and in particular LCP images, should not be lazy-loaded. While this is the default, it can be useful to explicitly set this if your tooling automatically adds loading="lazy" if there is no explicit value, or if your linter complains if it is not explicitly set. eager: Default loading behavior of the browser, which is the same as not including the attribute and means the image is loaded as soon as possible, regardless of where it's located on the page.lazy: Defer loading of the resource until it reaches a calculated distance from the viewport.Here are the supported values for the loading attribute: You can use the loading attribute to completely defer the loading of offscreen images that can be reached by scrolling: Images below the viewport are loaded with a lower priority, but they're still fetched as soon as possible. The loading attribute #Ĭhrome loads images at different priorities depending on where they're located with respect to the device viewport. Browser-level lazy loading also ensures that deferred loading of images still works even if JavaScript is disabled on the client. With lazy loading supported directly by the browser, however, there's no need for an external library.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |