Any website should be fast. No one likes waiting and images are one of the major slowdowns online. So, you should always optimise your images. Here are some ways to do it.
Find some links explaining color depths, bits, alpha channels and it’s relation to file size.
Responsive images and svgs
In our retina-filled mobile world there are more devices and screen sizes than we could possibly list. This means our designs and layouts need to be flexible and always look sharp. To do this we want to convert all older assets (icons) to the SVG format which scales as needed.
Another aspect is that we want all images to be crisp and high quality. To do this we need to deliver images that fit perfectly to the user’s device. But of course we should not force a 3000px image down on a mobile phone. Responsive images alleviate this issue by delivering the image size best suited (dimensions and network) to the user’s device.
Images served by a global content delivery network (CDN)
To avoid resizing one-billion images ourselves and we want to implement an image CDN like imgix or cloudinary. With any of these services you upload a master image in the highest possible quality. The service then resizes, crops and gives you back whatever image size you need, served from a global CDN.
Optimizing PNGs with pngcrush
$ brew install pngcrush $ pngcrush -rem alla -nofilecheck -reduce -m 7 (YOURFILE).png (OPTIMIZEDFILE).png
Should help a lot
Daan Jobsis shared the following premise: when considering a jpeg image’s file size, the level of compression makes more of a difference than its physical dimensions. In other words, given two identical images that are displayed at the same size on a website, one can be dramatically smaller than the other in file size if it is both highly compressed and dramatically larger in dimensions than it is displayed.