<\/p>\n Addy Osmani<\/a> says it’s coming in Chrome 75:<\/p>\n The I’ll probably end up writing a WordPress content filter for this site that adds that attribute for every dang image on this site. Hallelujah, I say, and godspeed other browsers.<\/p>\n Easy lazy loading of images<\/em> will have the biggest impact on the site as a whole, but lazy loaded iframes<\/em> will be even bigger for the individual sites that use them. I’m into it.<\/a><\/p>\n Yes yes whatever native lazy loading of images but lazy loading of iframes is gonna be a goddamn game changer for ad tech: https:\/\/t.co\/ADGc1UsVBf<\/a><\/p>\n — Laurie Voss (@seldo) April 8, 2019<\/a><\/p><\/blockquote>\nIntersectionObserver<\/code> has made lazy loading a lot easier<\/a> and more efficient than it used to be, but to do it really right you still gotta remove the src<\/code> and such, which is cumbersome. It’s definitely not as easy as:<\/p>\n<img src=\"celebration.jpg\" loading=\"lazy\" alt=\"...\" \/><\/code><\/pre>\n\n
loading<\/code> attribute allows a browser to defer loading offscreen images and iframes until users scroll near them. loading<\/code> supports three values:<\/p>\n\n
lazy<\/code><\/strong>: is a good candidate for lazy loading. <\/li>\neager<\/code><\/strong>: is not a good candidate for lazy loading. Load right away.<\/li>\nauto<\/code><\/strong>: browser will determine whether or not to lazily load.<\/li>\n<\/ul>\n<\/blockquote>\n\n