3 ms·

Sure, I'd love browser improvements too, but at the end of the day, you can't automatically optimize everything from the browser. The browser can't magically fi

• pcwalton 11y ago
  > Sure, I'd love browser improvements too, but at the end of the day, you can't automatically optimize everything from the browser. The browser can't magically fix a 1MB JS file in <head>, or serving 2000px wide images to iPhones. Sure, I agree that many of the optimizations suggested are good practice. (Note, though, that serving 2000px wide images to iPhones is fixable in the browser, with downscale on decode.) :) > A cynical answer is that Google released this because web authors haven't done a good enough job making fast pages. It's not cynical—that's the exact motivation of AMP. My point is that it cuts both ways: we need to keep improving the browser, as there are still massive opportunities for performance improvements.
  • arohner 11y ago
    > (Note, though, that serving 2000px wide images to iPhones is fixable in the browser, with downscale on decode.) :) From a rendering perspective, yes. From a "make this page load faster", no, because the network download time is 10x-100x larger than the processing time.