4 ms·
The Guardian is 4MB because the front page has a dozen+ hi-res images. Turn them off if you want to optimize for size. Not every site has to be a static wall of
by paxys 6y ago
The Guardian is 4MB because the front page has a dozen+ hi-res images. Turn them off if you want to optimize for size. Not every site has to be a static wall of text.
And why is 512KB acceptable but 4MB a problem? Yes the web is a bloated mess, but there's no point drawing random lines on meaningless metrics. Just focus on providing a good user experience. A few bytes of bad JavaScript can mess up your site's performance, while several well-optimized MBs can make it accessible and useful.
- kevq 6y ago> The Guardian is 4MB because the front page has a dozen+ hi-res images. That's incorrect. If you analyse the structure of the site (link below), ~800KB of the 4.4MB uncompressed homepage is images. 1.3MB is JavaScript, another 1.2MB is HTML (how is that even possible?) https://gtmetrix.com/reports/www.theguardian.com/xSnIUn3X/ https://gtmetrix.com/reports/www.theguardian.com/xSnIUn3X/ > And why is 512KB acceptable but 4MB a problem? Um, because it's an 8th of the size and there are still many people in the world that don't have fast internet access. > A few bytes of bad JavaScript can mess up your site's performance, while several well-optimized MBs can make it accessible and useful. Agree with the JS, but not the images. Well omptimised imaged should hit multiple megabytes unless its some kind of gallery with many images. Using srcset to load resized images is a much better way of doing this.