Depending on how many images you have. Doesn't that mean that it has to download each image and then re-upload them? Could be quite a cost for minimal savings if you have a large number of images to store.
Edit: I'm talking about 20,000+ product images, not the images or files associated with a layout.
I just used Smush.it to optimise a couple of images on http://lanyrd.com/ (the logo and the background image) and it knocked a good 5KB off the page load - not too bad at all.
Our filenames are generated from the truncated SHA1 hash of the file contents, so logo.png becomes logo.16c7e567.png - which means we can safely set a far-future expires header and serve through Amazon CloudFront without worrying about changes to the images, JavaScript or CSS not propagating to the live site.
12 comments
[ 4.2 ms ] story [ 39.8 ms ] threadI think I'm in love.
Edit: I'm talking about 20,000+ product images, not the images or files associated with a layout.
Could be, could be a large saving for minimal investment in time+money. depends on how much downloading of the images occurs normally.
For me this isn't about saving money, it's about load time.
Our filenames are generated from the truncated SHA1 hash of the file contents, so logo.png becomes logo.16c7e567.png - which means we can safely set a far-future expires header and serve through Amazon CloudFront without worrying about changes to the images, JavaScript or CSS not propagating to the live site.
A mirror of your logo: http://homepages.inf.ed.ac.uk/imurray2/tmp/logo.16c7e567.png
A smaller file: http://homepages.inf.ed.ac.uk/imurray2/tmp/logo.squish.png
My notes on squishing images: http://homepages.inf.ed.ac.uk/imurray2/compnotes/squish_imag...
There's a bunch of others on Github but this is the only one I've personally used.