|
|
|
|
|
by zeveb
3214 days ago
|
|
> If the web page has some sort of carousel without lazy loading, it wouldn’t take long to use up 10% of somebody’s 1GB allowance. If you do use lazy-loading, please be sure to do so in a way which works without JavaScript enabled (sadly, this is very uncommon). Mobile users are free to use browsers which load images on demand (indeed, I remember that approach from the 1990s), or perhaps browsers could agree on a standard for different resolutions of images, but breaking the Internet (which is what requiring JavaScript to view content is) to save some people some bandwidth is IMHO a bad idea. https://www.robinosborne.co.uk/2016/05/16/lazy-loading-image... looks like a nice technique. > Render as much server-side content as you can. > Reduce/remove the third party dependencies you have on your pages. > Lazy load images whilst maintaining page layout. > Stop hacking fixes for your mistakes with Javascript. All good advice, particularly the last bit. |
|