I decided to end 2008 by looking at the developments in the browsers world. I decided to take the 3 most popular browsers (in terms of market share) and run them through a few tests that test areas that users generally find to be the most important. Things like page load time, memory usage, and JavaScript performance will be covered here. I must say I got some surprising results.
Each browser is running on the exact same machine so that the comparisons are accurate. If you do the test on your own machine you will definitely get different results for each specific browser (because your computer may be faster or slower than mine), but what you need to remember with these tests is that the results are all relative to each other. This means that the relationship between test results of different browsers should stay the same on your computer.
Notes:
- All of these tests were performed on a Windows Vista SP1 machine that was wired into a network to minimize the effects of wireless disturbances.
- All browsers started with a clean profile and no add-ons/extensions installed.
- Caches were cleared before each test was run.
- Only one browser was open at a time and no other applications (other than standard Vista services) were running.
Test 1: How Fast Do The Pages Load?
Some of the browsers show how long it takes for a page to load, but I wanted an independent verification that could be used with all of the browsers. I figured that sitting here with a stop watch just wouldn’t work :-).
After some research I came across the Numion Stopwatch. It is a fantastic tool for measuring how long it takes for a page to load. It uses Java Script to notify you how long it takes a website to load. From what I can tell it does a great job.
I ran the page load test 3 times on 3 different sites so that we could really see what the results were like. I wanted to use some of the most popular sites on the internet that had a lot of content so that there was actually something to measure (no point of measuring the millisecond difference in load time of Google.com). I used Yahoo.com, CNN.com and digg.com as the test subjects.
For each test I started the browsers with a cleared cache, and the three results were averaged together to get a single overall load time (measured in seconds).

Average Browser Page Load Time
The faster the load time the better, so in these tests Google Chrome turned out to be the winner. The surprising result to me was that FireFox 3 was beaten by IE7. There was a time when I mostly used IE (back when we had IE6) because as a web developer I need to use what most of my users are using. Then IE7 came out and people started switching to IE7, but I just couldn’t. The thing was so bloated and slow I couldn’t believe they realeased such an atrocity, so I switched to FireFox and have been using it since (I might re-evaluate that after these tests though). Since then the folks at Microsoft finally came around and fixed up IE7 (although a little late because a lot of people switched to FireFox since then). For those who are interested in raw data here are the averaged resutls for each of the 3 sites:
| Load Time |
CNN.COM |
Yahoo.com |
digg.com |
| FireFox 3.0.5 |
9.163 |
2.8 |
6.16 |
| IE7 |
6.827 |
1.905 |
3.451 |
| Google Chrome 1.0.154.36 |
4.434 |
0.871 |
3.258 |
Test 2: JavaScript Speed
I wanted to pick a JavaScript test that resembled the use of websites you visit everyday. That’s why I decided to go with the MooTools SlickSpeed test which runs the browser against different JavaScript libraries like: Dojo, JQuery, MooTools, YUI Selector and Prototype.
A lot of websites use these libraries. By running the browsers through the SlickSpeed test, I was able to find out exactly which ones will give you better JavaScript performance (and that’s what really matters on a day to day basis).
All of the browsers showed some errors when running these test, and so I’m only going to compare speed. I ran each of the tests 3 times, averaged the runtime (measured in milliseconds) for all five libraries, and then averaged the results.

Browser JavaScript Performance
Lower score is better. Again Google Chrome turned out to be the winner by slightly outperforming FireFox. It looks like folks at Microsoft have a lot of work to do to get IE up to par in terms of JavaScript performance.
Test 3: Memory Usage
Memory usage is a big concern these days as I’ve seen some browsers use up enormous amounts of memory. Although switching from IE6 to FireFox felt great switching from FireFox to FireFox 2 did not (exactly because of the memory usage problem). So I decided to compare how each browser performed in this area.
I ran the test by opening a list of sites that are extremely popular. Places like MySpace, YouTube, CNN, and others were all included as I went through and recorded 4 different memory usage readings:
- I started the browser, and took a memory usage readings from the Task Manager.
- I loaded ten predetermined websites in tabs, and took a memory usage reading after all the sites finished loading.
- Loaded ten more predetermined websites in tabs (totaling twenty websites), and took a memory usage reading after all the websites finished loading.
- I then let each browser sit for fifteen minutes with the twenty tabs open, and then took a memory usage reading.
The table below lists the browsers and the result from each test mentioned above:
|
At Startup |
10 Webites |
20 Websites |
20 Websites After 15 Minutes |
| Firefox 3.0.5 |
20.2MB |
110.8MB |
191.6MB |
198.8MB |
| IE7 |
16.4MB |
177.4MB |
267.2MB |
269.3MB |
| Google Chrome 1.0.154.36 |
9.6MB |
204.9MB |
383.6MB |
386.6MB |
Right now it’s clear that Firefox 3 walks away as the clear winner. After swtiching to FireFox 3 from FireFox 2 at least to me it was appearant that they finally fixed it up in terms of memmory consumtion. I must also note that although Google Chrome turned out to be the looser in this test (being the one using the most memmory) it was to be expected as it creates separate processes for each new browser tab you open. There’s definetly a memmory overhead for creating new proccesses, but I think it’s worth it because it makes it more stable and it runs faster on multi-core processors (which are on most computers today).
Browser Test Conclusion
It took me about eight hours to compile all of the results that you see here. I’d love to hear any comments you might have regarding theseresults, but remember that what you’ll see on your computer will likely be different from what I saw (but relationship of the results should stay the same). After running these tests I am definitely considering using Google Chrome more. I hope it gets the same kind of community going as FireFox.