Industry


Ads by TechWords

See your link here


Subscribe to our e-mail newsletters
For more info on a specific newsletter, click the title. Details will be displayed in a new window.
Computerworld Daily News (First Look and Wrap-Up)
Computerworld Blogs Newsletter
The Weekly Top 10
More E-Mail Newsletters 
John Brandon's picture
John Brandon

Web 2.0 Watcher

Review: Firefox 3.1 Beta 1 no speed demon, lags behind Chrome

Something went horribly wrong between the alpha of Firefox (called Shiretoko) and the first real Firefox 3.1 beta. I'm not too impressed so far. Compared to Chrome, in testing my most frequently visited sites, Firefox 3.1 now lags well behind Chrome. It seems Mozilla has not included beefed up JavaScript V8 support in this release, and it really shows.

IGN.com loaded in 45 seconds over a 2 meg connection this morning, compared to 28 seconds in Chrome. Gamespot.com loaded in 27 seconds in Firefox 3.1, compared to 20 seconds in Chrome (the site doesn't have quite as much rich content today -- no sprawling ads). Disney.com (not one of my favorite sites but a good test of load speed) took 30 seconds to load in Firefox 3.1 and 25 seconds in Chrome.

Adrian Kingsley-Hughes pointed out that Google has a benchmark app available online for testing JavaScript. Chrome scored 2887 compared to a Firefox beta 1 score of only 334. (Higher numbers are better.) That's a massive difference -- Chrome users, you can enjoy a major speed perk.

The Firefox 3.1 beta includes a new feature for tab switching. It's kind of lame. When you press CTRL-Tab, you see large thumbnails of your tabs, but they look sort of munged. And how much tab switching do we really need? It's easier to just click the tab.

There's also support for CSS 2.1 and 3.0 properties, which is a little "heh" so far. I haven't noticed any major compatibility advantages, and -- in fact -- the 3.1 beta seemed to get confused by Disney.com.

The awesome bar -- which allows you to search through visited sites -- adds a few key commands for the true techies. You can restrict searches to only bookmarks by using *, or only search your history by using ^. LifeHacker goes into much greater detail on these minor syntax perks.

ReadWriteWeb has a good summary of the code enhancements. I'm not really jumping up and down about any of them. There's a new way for developers to access GPS data from mobile devices (using a geolocation API) for geo-location services. For example, a Web app could conceivably know that you are near a coffee shop with Wi-Fi and let you know the pricing options.

So does this mean Chrome is the speed champion? Yes, for now. Shiretoko showed that Mozilla knows how to make a fast browser, but I figure the 3.1 beta is a test for compatibility, not speed. The final 3.1 release, with tweaked JavaScript support, could blow Chrome out of the water and negate the main reason people have switched browsers.

What People Are Saying

"Disney.com (not one of my

"Disney.com (not one of my favorite sites but a good test of load speed) took 30 seconds to load in Firefox 3.1 and 25 seconds in Chrome."

Whoa, those are seriously high load times, I'm on a college campus, mid afternoon on a rainy weekend, and Disney.com loads in, on average, 3.7 seconds over four trials. I'm using Firefox 3.1, too.

If it's taking you 30 seconds to a load a webpage on a 2 meg connection you've got some bloatware issues dude.

I realize my rig is very sick but 30 seconds? Really?
Core i7 920 on Asus P6T Deluxe
NVIDIA 8800GT
3gb RAM
500GB WD HDD SATA

Not my experience

In my experience FF 3.1 beta works as fast and perhaps even faster than Chrome. Something must be wrong on your side. BTW, on my computer at least, gamespot.com loads in about 2.5 seconds from hitting the enter key.

Give Firefox a chance to show its speed

As Mozilla had always prioritize reliability and compatibility over speed and features, it has disabled its more-than-lightning speed TraceMonkey JavaScript engine.

You can turn it by changing the value of javascript.options.jit.content to True in about:config

Apple's SunSpider (from WebKit) shows that Firefox 3.1b1 is 3.6 times faster than Chrome after enabling the TraceMonkey engine.

that is when Firefox is fully-featured browser while "Krom" is a stripped-down browser.

Chrome? Please

Try Loading nba.com on chrome and then you would realise that speed is not everything. Chrome is still work in progress so really comparing it to FireFox 3.1 beta is like comparing two faulty printers.

Firefox 3.1 beta

Yes, I agree Firefox is slower in compare to Chrome. But another fact is, Chrome is in very early mode 0.2. In Chrome 1.0 lots of new feature will be introduce. Also we use lots of addons in Firefox.

We want features first, if 2 product gives the same features then we go to compare its speed but as of now Chrome is not full featured browser. It is a preview of actual Chrome 1.0.

A couple of points. "It

A couple of points.

"It seems Mozilla has not included beefed up JavaScript V8 support in this release"

V8 is the name of Google's JavaScript technology so you shouldn't expect it to be included in Firefox. :)

Mozilla's equivalent is called TraceMonkey (TM), it's disabled by default in this beta. You can enable it by going to about:config and filtering on "jit" then enabling those two properties.

"Adrian Kingsley-Hughes pointed out that Google has a benchmark app available online for testing JavaScript."

TM doesn't currently work on this benchmark (AFAIK it will before 3.1 final), to compare V8 to TM you can try Apple's benchmark suite (where TM does work if you've enabled it):

http://www2.webkit.org/perf/sunspider-0.9/sunspider.html

"There's also support for CSS 2.1 and 3.0 properties, which is a little "heh" so far."

Many people have been pushing for browsers to adopt the latest web standards (especially allowing custom fonts on web pages) so seeing you so casually dismiss this is a little annoying.

Thanks.

3.1b2

Beta 2 is out, please update article.

beta 2 is still a PRE-RELEASE

Yes, PRE-release of beta 2 has been out for since they freezed the code for the beta 1 a week or two back. But, let me caution that these are nightly builds and are pretty unstable.

As a word of advise, I would just suggest everyone to wait until beta 2 next month before switching to 3.1 for daily use. A lot of features and performance are still not optimized, and popular addons have not had time to update their codes. True, you can bypass the compatibility to force them to work with 3.1, but I have found at least one of mine to be causing problems.

As for these speed test results, I would take them with a grain of salt at this point. This is only beta 1. If the past is any indication, Mozilla does not squeeze out all of the performance until beta 3.

Where?

I don't see it here:

ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/

the new firefox sucks.. i

the new firefox sucks.. i used to be able to have like 9 tabs open, all running fast.. i could switch between em no problem. the new firefox though eats up so much resources its disgusting. anything over 3 tabs open and its lagggggy as f**k. oh and if you're trying to watch movies, video clips, or even stream music- best of luck. I will be switching over to chrome tonight, i have had enough of the firefox bullshh with this release. oh and before it gets mentioned i went into the about config and its set up for max speed, still sucks.