Chrome 10 v. Firefox 4: Open Source Browser Battle

by Mr. Keir Thomas Keir Thomas – Thu Mar 10, 1:41 pm ET

I decided to take a look at the two open source browser platforms to see which is best for business users. My examination was decidedly unscientific, and we shouldn't draw too many conclusions. If nothing else, pitting a release candidate against a final release might be a little unfair, although at this stage we can expect Firefox 4 to be ready for the public, barring a few small bugs here and there.

For my test bed I opted for a low-powered computer--an old Intel Core 2 Duo processor laptop with 2GB of RAM, running 32-bit Windows Vista. The Net connection was 6GBit DSL. I created a fresh Windows account for testing purposes too, to avoid performance being impacted by "cruft."

Screen Real Estate

Mobile workers require a browser that doesn't eat up screen space with user-interface elements, especially if they're using netbook computers. A criticism of the 3.x releases of Firefox was that its navigation buttons were a little too large. Well, that's been fixed in version 4, which overhauls the interface arguably for the better. The program has also switched to a status bar at the bottom of the screen that disappears when it's not needed, just like Chrome.

As you can see from the screen shot below, both browsers are pretty much neck-and-neck when it comes to space taken up by tabs and controls. Perhaps Firefox is a pixel or two greedier but that won't make any difference in the real world, and Firefox also has a "small icons" setting which saves a little space. For some reason Chrome opts for a much larger font to display URLs. I like this, but it's down to personal preference and it makes no actual difference to the space taken up by the controls.

Both Firefox and Chrome had easily accessible full-screen modes that slid the interface elements and Windows taskbar out of the way and dedicated the entire screen to web pages. Sadly, neither lost the right-hand scrollbar, which could easily have disappeared in the same way the status bar does, only reappearing when it's moused over.

Web App Performance and Compatibility

Looking at compatibility with HTML standards, along with Javascript performance, the aim is to judge how effectively the browser runs Web applications not only today, but also those that might arrive in the future.

I used various test Websites and thereby wandered into a minefield. No test is perfect, or representative, and in some significant ways these results should be taken with a pinch of salt. However, to the best of my knowledge, we currently lack "real world" benchmarking. We can't yet test performance in Google Docs, for example.

First, I gave both browsers a run-through with the Acid3 test, which tests overall compatibility with HTML and Javascript standards. Both are vital to the correct functioning of Web apps.

Chrome was the winner here, with a score of 100/100, although the Firefox release candidate was close behind with 97/100.

Next, I ran the browsers through The HTML5 Test, which tests compatibility with the forthcoming HTML5 standard. HTML5 aims to revolutionize Web applications, although it's very much a work in progress.

Again, Chrome was the winner with 288 points, plus 13 bonus points out of a potential total of 400 points. Firefox lagged behind with 240 points, plus 9 bonus points.

Finally, I ran the Sunspider 0.9.1 benchmark, which tests out-and-out Javascript performance. Because this is a performance test, I made sure only one tab was open in each browser, and closed any other open applications. I also ran each test three times consecutively, noting only the best score achieved.

Chrome scored 375.4ms, but, with lower scores being better, Firefox was the winner, finishing the test in 345.7ms. However, the scores are so close as to be practically indistinguishable.

Next page: Working across multiple computers, and proxy friendliness

through a proxy server, depending on how your network administrator likes to run things. Mobile workers might also do this to prevent others from snooping on their Wi-Fi traffic.

Google Chrome has no proxy controls of its own. Instead, it obeys the overall Windows settings, and clicking the proxy configuration option within the Under the Hood settings dialog simply opens the Windows networking dialog box.

Firefox has its own proxy settings, which you can access via the Network tab of the Advanced section within the Options dialog box. However, it can still obey the overall system proxy settings, just like Chrome.

I prefer Firefox's approach because it gives me the freedom to alter settings without having to jump through the hoops of Windows User Account Control dialog boxes, or cause problems for other applications that need Net access, such as chat programs.

There's a range of extensions and add-ons for both Mozilla is pushing hard to get Firefox onto non-computer devices, such as tablets, with its Mobile Firefox project. At present Google is limiting Chrome to the mainstream desktop operating systems: Windows, Mac OS X, and Linux. Mobile Firefox includes the Weave function, which brings syncing to portable devices, so despite the difficulty of getting things working, I'm tempted to chalk up this category as a win for Firefox.