jmarantz commented on issue #1663: Chrome's Native Lazy Loading URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1663#issuecomment-532190963 > "why don't we [use PageSpeed Beacons] when other lazyload method is present? It's hard to boil the ocean. PageSpeed's mission is to take a website that is not yet optimized and improve it. It is much harder to take one that is already optimized but with fatal mistakes, such as lazy-loading an above-the-fold images, and fix it. In contrast, I think it is within the mission to use the best possible option to optimize a page, and I am definitely sold that if Chrome's lazyload method is available, that is superior to building it via JavaScript. > we determine that a image is in the viewport, we can set the attribute loading = eager that load the image (or iframe) immediately That sounds good. > the distance on where the images are pre-loaded changes with the type of connection, for a 2G connection the distance is bigger than for a 4G, so maybe we interfere with these feature. How would we interfere with that feature if we integrated the Chrome lazyloading technique when applicable?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
