: Best practices when loading images for improving page loading speed I am working on optimizing a page's loading speed. Here are some analytics: Notice how the images, although only accounting
I am working on optimizing a page's loading speed. Here are some analytics:
Notice how the images, although only accounting for 65% of the total size (1.1MB), are by far the slowest loading assets: 96% of time.
I'd like to know which are the recommended practices on optimizing loading speed, only taking images into account.
Some of the techniques we are already applying:
image compression
images hosted on cookieless domain and CDN
spriting everything that can be sprited
http headers: keep alive and Expires to one year.
Disclaimer: I have gone through the available documentation, I think by focusing on image loading optimization I am not creating a duplicate or a subjective question.
More posts by @Jessie594
3 Comments
Sorted by latest first Latest Oldest Best
1st: optimize images: decrease size, combine them, or remove them if possible
2nd: server images from CDN
3rd: server images from multiple domains, better not the subdomain of the site to avoid cookie
4th: use "lazy loader", load images on scroll
Serve only scaled images. Images could be scaled down to multiple sizes on server side and then serving the scaled image according to the need. WordPress is a well known example for this type of image handling.
Although the tools at pingdom.com gives you somewhat pretty accurate data, you have to remember that the tests pingdom performs wont give you accurate data, as it in the end boils down to the end-users browser. Browsers just handle this stuff differently.
To address the question directly; You leave out details regarding where and how your images are stored. I have experienced that if images are stored on a CDN, your test results will improve dramatically. Like really really much.
I must admit that i fail to understand why your images are 1MB in total, what kind of insane website is this? With a properly optimized and compressed png file averaging at around 20kb, you must have a shitload (pardon my french) of images that you need loaded.
A very common mistake, when it comes to images on websites, is that designers have this belief that the images absolutely must be saved with a minimum of compression (think FLAC for music). Let me illustrate with images.
This image is saved at "100% quality" being 171KB in size.
This image is a optimized version saved at "60%" quality being 42KB in size.
Personally, i cant see any differences, but yet you save 75% of the bandwidth by using a proper optimized+compressed version. These images are in jpg, but it is pretty much the same across all formats.
You can, within 5 minutes find at least 10 websites that have this issue. It is said that the danish newspaper BT.dk improved their loading times by 50% by optimizing their images (and they have loooooads)
If you are interested further in this topic, heres a great article about it.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.