4 ms·
images and everything else bc client-side rendering... not sure how this is an argument for not lazy-loading images though
by connorelsea 8y ago
images and everything else bc client-side rendering... not sure how this is an argument for not lazy-loading images though
- anothergoogler 8y agoAs an end user it feels slow. If I hold my space bar on a website created in 1995, I can scan the entire page contents.
- connorelsea 8y agoYou'd still have blank spaces where large images are as they're loading on a slow connection
- anothergoogler 8y agoI'm talking about lazy loading that waits until the image enters the viewport. An HTML page created in 1995 loads the images eagerly.
- stereobooster 8y agoWhat you are talking about is more like graceful degradation. If server side rendering is used you will be able to see content ASAP, but not able to scroll, because interaction is blocked by JS. But if you will visit page with JS disabled you will get what you want, because component generates img in noscript tag and you will be able press space to scan the page
- anothergoogler 8y agoActually pages that use a component like the one in this submission typically show a blurry "beer goggle" version of the image, waiting for JS to replace them with a hi-res version. So with no JS you get a page of beer goggle images (BBC does this for instance).
- stereobooster 8y agoBut not this component. This component will load images without JS. Test it yourself https://stereobooster.github.io/react-ideal-image-experiments/ https://stereobooster.github.io/react-ideal-image-experiment...
- ec109685 8y agoBecause images won’t even start loading until JavaScript fully downloads and executes versus loading in parallel with other activities in the page.