Hacker News Reader

This seems to be comparing data URIs to an essentially un-optimized page. It would be more valid, I think, to compare the load time for different levels of optimizations which are more browser-compatible: e.g. CSS sprites, using different image domains, etc.

That said, I understand that any browser/HTTP performance testing is kind of a pain, so thanks for this result.

View on HN

I agree that a comprehensive test would include the optimized scenarios that you mentioned. In this case the intent was to show that even when comparing two extremes - a very unoptimized page and a super-optimized page - the results were not as disparate as we'd expect. Scenarios involving sprites and domain sharding we'd probably expect to fall somewhere in the middle. Thanks for your comments.

Reply on news.ycombinator.com