A year back, Google included lazy loading support for pictures in Chrome 76. As of late, ChromeEng manager Addy Osmani announced that the team has included the postponed loading of iframes as a standard feature to the Chrome browser and Chromium browser.
This feature defers the loading of the iframe outside the window until the user looks over the website page to a close-by area. This can save data, speed up the loading of the different parts of the page, and reduce memory utilization.
The Chrome team’s research shows that lazy iframe loading can save 2-3% of the median data volume, 1-2% of the first content rendering, and 95% of the location can save 2% of the first input delay (FID).
Currently, the loading has supported three attribute values:
lazy: Ideal for lazy loading.
eager: Load immediately (ideal for non-lazy loading).
auto: The browser decides whether to delay loading.
Osmani said that when it loads embedded content on YouTube, it saves 10 seconds of interaction time on mobile devices. Instagram and Spotify will still process embedded content during initial loading but save >100KB and 514KB respectively after compression.
And, all Facebook social plug-ins now support the native browser to delay loading iframes. It finally concluded that the support for lazy loading of iframes will allow users to greatly easily improve the performance of web pages.
It is worth mentioning that Chrome for Android will still automatically delay loading pictures and iframes outside the window in Lite mode. For more details, please check the official blog.