A while back I enabled lazy loading for images on Liliputing in an attempt to help reduce the amount of time it takes to load the website. What that means is that when you first visit a website, your browser doesn’t need to render all the content on the site at once — images that aren’t “above the fold” will only be loaded when you scroll down the page.
Plenty of websites do this… but it’s generally been up to web developers to enable lazy loading.
Now Google is building the feature into its Chrome web browser — future versions of Chrome will automatically lazy load images and iframes by default, unless a web developer includes code that tells the browser to do something different.
Basically Google is adding support for a new “loading” attribute which will let web publishers choose from one of three values:
- lazy – Content is a good candidate for lazy loading
- eager – Content should be loaded right away.
- auto – The browser should determine whether to lazy load content or not.
If the website doesn’t specify a value, Chrome will default to auto, which means that odds are the browser will automatically lazy load images on many of the billions of websites that are already out there (and which are unlikely to be updated with the new attributes anytime soon).
Hopefully that means faster page load speeds across the board.
The new behavior could be included in Chrome 75, which is scheduled for release in May, and it should be available for Windows, Mac, Linux, Chrome OS, and Android versions of the web browser as well as other web browsers that use the Blink rendering engine.
So far no other browsers (such as Firefox or Safari) have announced plans to support the new loading attribute, but that could change in the future.
via Android Police, Techdows, and blink-dev Google Group
I’d like to see a way to stop videos from automatically playing on Yahoo. Graphics are bad enough, but video content is what really loads down my browser.
In Firefox, there are some options to disable all automatic video playback (media.autoplay.default, media.autoplay.allow-muted). There may be something similar in Chrome
Is this based on a web standard or is it Chrome specific?
Is there a difference, lol? On a serious note, I believe Chrome implemented it as a site-specific preference first. In the past people would code their own lazy-loading scripts.
If it’s not a standard, then we’re going to be reverting back the old days of web devs only targeting IE with it’s IE only features except it’s Chrome now.
Except the difference here is that this isn’t a proprietary feature. Other browsers can look for that code in a website, and implement an identical feature. Sure it would be ideal if it was implemented into the HTML standards, but we’re never going to get anywhere with innovating if we wait around for a consortium to standardize things before we start using them.
About time really. Page prefetching is another data vampire.
Comments are closed.