Monday, September 14th, 2009

BrowserScope: UAProfiler++, Crowd source browser tests

Category: Browsers, Performance, Testing

<>p>We are good friends with Steve Souders, but his UA Profiler just got beaten by something much better: BrowserScope. Fortunately for him, he and a new team are the ones who beat it :)

Lindsey Simon says it best:

Browserscope is an open-source project for profiling web browsers and storing and aggregating crowd-sourced data about browser performance.

The goals are to foster innovation by tracking browser functionality and to be a resource for web developers.

Browserscope is based on Steve Souders’ UA Profiler, and his original tests have been preserved here as the Network test category. Other test categories include Ian Hickson’s Acid3 test (ported by Jacob Moon into Browserscope), Annie Sullivan’s Rich Text Edit Mode tests, and John Resig’s Selectors API Test Suite (ported by Lindsey Simon into Browserscope).

This one more evolution, and more is to come:

  • Visualize test result trends over time
  • Wall of fame, up-and-comers, Billboard top 50
  • More test categories – cookies, security, reflow
  • More contributors
  • Tagged/personalized test results
  • Normalize time-based results across platforms
  • User agent parsing library

The guys are on hand to announce BrowserScope at The Ajax Experience this week!

Related Content:

3 Comments »

Comments feed TrackBack URI

Chrome comes up trumps pretty much everywhere. And IE bombs. Of course :)

Comment by willbo — September 14, 2009

“Chrome comes up trumps pretty much everywhere.”

By matching Safari on almost everything? These are the only two differences on any of the tests:

Chrome 4 vs Safari 4

- Network
– Chrome: Cache Redirects

- Rich Text
– Chrome: Un-Apply Formatting

I’m not sure what the test of cache redirects entails, but I would say that taking it literally, I’m not convinced that caching redirects is a positive thing. Particularly when you’re changing and testing server configuration.

Regarding un-apply formatting, this being the only renderer difference is no surprise at all. The likelihood is that Google is more aggressive about adopting WebKit updates than Apple’s Safari releases.

Either way, I’d say that it’s overall a testament (like all of these browser comparisons tend to be) of the strength of the WebKit project. In a relatively short time, WebKit has progressed to be one of the two de facto standard renderers, and has continuously pushed the other vendors to improve, and pressed ahead of them.

Comment by eyelidlessness — September 14, 2009

It is obvious that IE is not a browser!

Comment by stoimen — September 14, 2009

Leave a comment

You must be logged in to post a comment.