A third of Google's image size is this thing: <a href="https://ssl.gstatic.com/s2/oz/images/notifications/spinner_32_041dcfce66a2d43215abb96b38313ba0.gif" rel="nofollow">https://ssl.gstatic.com/s2/oz/images/notifications/spinner_3...</a> which is basically a loading icon that is rarely seen.<p>How does HTTP compression factor into image optimization? Is it possible to optimize an image but the HTTP compressed size ends up being greater?<p>You should release a monthly report with this same algorithm. You should also put in a column for competitors algorithm (not the just ones you beat, all of them).<p>Don't forget that some images are loaded after the page and content load, so they have very little impact on user experience (and all these sites make heavy use of CDNs).
Hm, tested the field/mountain comparison from kraken.io first page on JPEGmini - 184kb on jpegmini vs 242kb on Kraken.io<p>Seems their solution is both cheaper and better?<p><a href="http://www.jpegmini.com/" rel="nofollow">http://www.jpegmini.com/</a>
I don't know much about the technical side of things, but as someone studying SEO and UX this seems like a huge win. Not only by cutting down on page load size / speed but so much better fo rUX.