2. Those were the reported numbers, but it's not like that was the only data point discussed in the article. Every single photo had deeper analysis and included subjective evaluation. He even directly made the point that you did about the last photo.
3. Loading megabytes of photo data into folks browsers by default doesn't seem worth the benefit (the page is already sluggish). If you're interested, the originals are available for download.
More info on the issues with this type of benchmark from Jason Garrett-Glaser (a.k.a. Dark Shikari), an x264 developer: http://x264dev.multimedia.cx/?p=458
--Babbage (1864), Passages from the Life of a Philosopher, ch. 5 "Difference Engine No. 1"
You can't reasonably use an encoder optimized for PSNR and then "ding" it for producing output with bad SSIM, or vice-versa.
Further, my understanding of Google's intent with webp is that it is being offered as a replacement to jpeg. In that case, even if it's optimized for one thing, it's not just fair but necessary to see how it works under all other things.
Besides, I don't see why you need megabytes of photo data, regular internet photo data would have sufficed (for which the authors say they have developed webp anyways).
I agree with your point that he included subjective evaluation, though.
Further, image quality is measured in terms of mean RGB or value difference, which is very technical and does not matter to the human eye (a lot). For example, in the portrait, the last picture, the JPEG artifacts in the person's face really hurt more than the blurring of webp, yet both have about the same statistical mean values.
Last, without the original lossless image (at hand), it is hard to tell which lossy encoder is better. Again with the portrait picture as an example, you have to download the provided lossless image to see that webp blurred the face too much.
Still, better than other quick-and-dirty 'analysis' I've seen so far.