
Ever since we did a browser comparison test last year there have been a lot of emails and comments asking if we were going to update the article to reflect new releases. I thought about adding in the new browsers as they came out, but decided against it for one reason or another. Instead I thought it would be better to just do a fresh article, and include even more stats than last time.
The main reason that I thought this was worthy of its own article was because a lot has changed in the last year. Since March 2008 we’ve seen major milestone releases from each of big browser makers, and to top it off Google Chrome has come onto the scene. These browsers have also shifted focus from adding nifty new features to diving deep into the code trying to squeeze out every last ounce of performance.
We’ve got a lot in store for you today ranging from JavaScript speed tests to memory usage comparisons, and we’ll even throw in some Acid 3 coverage. Lets go ahead and dive right in.
Notes about testing:
- All of these tests were performed on the same Windows XP SP3 machine that is wired into a network to eliminate the effects of wireless disturbances.
- All browsers started with a clean profile and no add-ons/extensions were installed.
- All browser data, including caches, were cleared before each test was run.
- Only one browser was open at a time, and no other applications (other than standard XP services) were running.
- Internet Explorer 8 was used in the native rendering mode (”standards compliant mode”).
- No plug-ins (Flash, Java, etc…) were installed on the machine to ensure that slow performance wasn’t due to the loading of a plug-in.
–JavaScript Tests–
The main speed test that everyone seems to use for JavaScript is SunSpider. Last year we compared the browsers with the SunSpider test prior to writing our first comparison, and so we wanted to try something different. That’s when we turned to the MooTools SlickSpeed Test. It tests various operations against a lot of common JavaScript libraries including MooTools and JQuery.
So which one did we go with this year? Well, we did both. We ran each test, SunSpider and SlickSpeed, a total of three times each. Then we averaged the results together to get the pretty little graphs you see below. For both of them the goal was for the browser to complete the tests as fast as possible, and so a lower number is better.
Copyright © 2009 CyberNet | CyberNet Forum | Learn Firefox
Browser Comparison: Memory Usage, Speed, Acid 3 Test
Related Posts:
- Standalone Versions Of Internet Explorer 3, 4, 5, and 6
- Microsoft: Firefox/Chrome are Insecure, Difficult to Use, and Unreliable
- Firefox Experiences Continued Growth With More than 15% of the U.S. Market
- Where is the Browser Market Headed?
- Is Firefox Going To Pick Up After Microsoft’s Mistake?
Recent Comments