Wednesday, September 10th, 2008
“Steve, have you done a performance analysis on Google Chrome?”
Steve Souders did one better. Rather than just running some tests, he wrote a UA Profiler that allowed him to point a browser and let it roll through the tests:
Browser UA Profiler
Chrome 8/11 Firefox 2 7/11 Firefox 3 8/11 IE 6,7 4/11 IE 8 7/11 Opera 9.5 5/11 Safari 526 8/11
Getting back to where I started, let’s look at Chrome’s performance profile. It’s nice to see that Chrome is at the top right out of the shoot, having 8 of the 11 performance attributes tested, tied with Firefox 3 and Safari 526. The three performance features Chrome is missing are loading scripts and other resources in parallel, not blocking downloads when a stylesheet is followed by an inline script, and support for prefetch links. Looking at the Chrome user agent string we can see it’s based on Safari 525. If Chrome incorporates Safari 526 improvements, it’ll fix the most important performance trait – loading scripts in parallel. The detailed results show that Chrome has one improvement over Safari: caching redirects that have an expiration date in the future.
Steve is keen to add more tests, so what would you like to see? I think that there is room to tests for non-performance related features too. For example, tests such as “does the browser support postMessage” would be nice to see. There are a bunch of “is there window.Foo” at the shallow level, and then going deeper. CSS and selector tests could be added too.
Posted by Dion Almaer at 9:07 am