The AchieVer Posted April 6, 2019 Share Posted April 6, 2019 After Chrome, Firefox will also support off-screen image lazy loading Built-in support for image lazy loading coming to Firefox. Google already testing feature in Chrome Image: Mozilla Mozilla engineers plan to add support for "lazy loading," a mechanism to defer the loading of images if they are not visible on the user's screen when a website is first loaded. Work on adding this feature in Firefox started last month. Google has already been testing a lazy loading mechanism in Chrome for over a year, since January 2018. HOW LAZY LOADING WORKS Lazy loading has been a part of the web development scene for more than a decade. It was initially created as a concept for JavaScript libraries. Developers figured out that by delaying the loading of non-visible images, they could significantly improve a website's page load time, a crucial search engine optimization (SEO) criteria, and, hence, obtain a better position in Google search results. The concept spread quickly, and by the early 2010s, there were hundreds of libraries and plugins that provided easy ways to implement a lazy loading mechanism on websites, regardless of underlying programming language or content management system (CMS). GOOGLE WANTED TO SUPPORT LAZY LOADING AT THE BROWSER LEVEL The first step to moving lazy loading from the website level to the browser level was taken in January 2018, when Google published a design document outlining how Chrome would support the lazy-loading of images and iframes that are outside a page's visible section. Chrome flags were later implemented, which are currently available in the Chrome stable version, and which users can enable and have websites load faster. With Google's backing, the feature also became attractive to other browsers, whose developers realized the benefits it could bring to improving page load times, if enabled. Over the past year, Safari engineers have, too, expressed interest in supporting lazy loading. With Firefox putting its backing behind the feature as well, this means that all major browser rendering engines will soon support lazy loading -- WebKit (Safari), Blink (all Chromium browsers), and Gecko (Firefox). We excluded EdgeHTML, as Microsoft Edge will soon move to a Chromium codebase. Source Link to comment Share on other sites More sharing options...
Image: Mozilla Mozilla engineers plan to add support for "lazy loading," a mechanism to defer the loading of images if they are not visible on the user's screen when a website is first loaded. Work on adding this feature in Firefox started last month. Google has already been testing a lazy loading mechanism in Chrome for over a year, since January 2018. HOW LAZY LOADING WORKS Lazy loading has been a part of the web development scene for more than a decade. It was initially created as a concept for JavaScript libraries. Developers figured out that by delaying the loading of non-visible images, they could significantly improve a website's page load time, a crucial search engine optimization (SEO) criteria, and, hence, obtain a better position in Google search results. The concept spread quickly, and by the early 2010s, there were hundreds of libraries and plugins that provided easy ways to implement a lazy loading mechanism on websites, regardless of underlying programming language or content management system (CMS). GOOGLE WANTED TO SUPPORT LAZY LOADING AT THE BROWSER LEVEL The first step to moving lazy loading from the website level to the browser level was taken in January 2018, when Google published a design document outlining how Chrome would support the lazy-loading of images and iframes that are outside a page's visible section. Chrome flags were later implemented, which are currently available in the Chrome stable version, and which users can enable and have websites load faster. With Google's backing, the feature also became attractive to other browsers, whose developers realized the benefits it could bring to improving page load times, if enabled. Over the past year, Safari engineers have, too, expressed interest in supporting lazy loading. With Firefox putting its backing behind the feature as well, this means that all major browser rendering engines will soon support lazy loading -- WebKit (Safari), Blink (all Chromium browsers), and Gecko (Firefox). We excluded EdgeHTML, as Microsoft Edge will soon move to a Chromium codebase. Source
stylemessiah Posted April 6, 2019 Share Posted April 6, 2019 An open letter to Chrome and Firefox devs.... I really struggle to see how this a "feature", let alone one you would want Personally i think theyre just looking for things to do to say "look we have a new feature that x browser doesnt" Think how you actually read most web pages these days, especially those with picture content, common sense will tell you that if theres a picture on the page your attention is drawn to it, now factor in that most text starts part way down the page, factoring in that theres a header, a menu system/login box etx...so whats my point? Well exactly this: Youre probably already going to scroll to get a goodly amount of text to read, as it generally starts offset down the screen, at which point your probably going to pull up a photo....and if that picture isnt there when you scroll youre going to be on the browsers support page asking why your x browser is broken because your pictures are delayed since you updated ot the latest version of x browser I hear you saying well ive got Gb fibre, in your smug 1st world way, and so any "delay" will be negligible, but even in Australia we have half assed internet infrastructure (thanks to a flat earther liberal government who hobbled the planned national broadband network). For those on unprivileged first world networks, all youre doing is breaking a browser behaviour thats been there since the beginning, by adding yet more gubbins to screw with peoples traffic Nonsense! This is on the same level as spending youre time on themeing your browser etc Google/Firefox, its twaddle, and it needs to stop Stop the nonsense, spend more time on actually important things like security - you know like plugging holes you sometimes leave there for years unclosed... This crud will be literally the first thing i disable upon install.... Absolute rubbish Link to comment Share on other sites More sharing options...
spudboy Posted April 6, 2019 Share Posted April 6, 2019 2 hours ago, stylemessiah said: This crud will be literally the first thing i disable upon install.... Absolute rubbish Have you tried it with Chrome to see if what you're saying actually applies? I installed Chrome (I'm a Firefox user), set the lazy loading flag to enabled, and used NetLimiter to limit all Chrome traffic to 5 Mbps . There was zero noticeable difference in the loading time of off screen images when scrolling down long pages at full speed. So unless a persons internet speed is slower than that, I don't think anyone is going to see a negative difference in the way you are stating. I would recommend anyone with an internet speed of 5 Mbps or higher to have lazy image loading enabled. Under 5 Mbps disabled, as I did see a noticeable difference when I went down to 2 Mbps. But whether or not a person enables/disables it also depends on an individuals own situation and browsing habits. Link to comment Share on other sites More sharing options...
masterupc Posted April 6, 2019 Share Posted April 6, 2019 Lazy loading can be achieved by css + js... I work with that in a daily basis... Link to comment Share on other sites More sharing options...
steven36 Posted April 7, 2019 Share Posted April 7, 2019 All there is is Chromium and Firefox forks anymore mostly . Open source Chromium forks suffer not having any drm playback . Firefox forks like Waterfox have drm but suffer from bugs from having and outdated engine . Only reason i use waterfox is i can use old addons with it but i have openwith addon for pages that have reCAPTCHA I just open with Firefox and it always works good, you to have change your user agent with a addon to even to get to work right in Waterfox . Even with the latest update they pushed using Firefox EsR user agent so i guess the bug is in Firefox EsR as well , i use the latest version of Firefox for and it's fine. https://old.reddit.com/r/waterfox/comments/b0bwqu/recaptcha_functionality_broken_in_56271/eirc365/ Link to comment Share on other sites More sharing options...
stylemessiah Posted April 8, 2019 Share Posted April 8, 2019 On 4/7/2019 at 3:34 AM, spudboy said: Have you tried it with Chrome to see if what you're saying actually applies? I installed Chrome (I'm a Firefox user), set the lazy loading flag to enabled, and used NetLimiter to limit all Chrome traffic to 5 Mbps . There was zero noticeable difference in the loading time of off screen images when scrolling down long pages at full speed. So unless a persons internet speed is slower than that, I don't think anyone is going to see a negative difference in the way you are stating. I would recommend anyone with an internet speed of 5 Mbps or higher to have lazy image loading enabled. Under 5 Mbps disabled, as I did see a noticeable difference when I went down to 2 Mbps. But whether or not a person enables/disables it also depends on an individuals own situation and browsing habits. Read my post again, my exact point was for people using slower internet.... Link to comment Share on other sites More sharing options...
spudboy Posted April 9, 2019 Share Posted April 9, 2019 23 hours ago, stylemessiah said: Read my post again, my exact point was for people using slower internet.... I read it, no need to re-read it. You didn't specify what you would consider to be slow or what your own speed is. Your post had no reference to go on whatsoever. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.