How fast is your favorite browser?

[Krome]

Hey guys.  I tested my favorite browser against Internet Explorer 11.  Here's the result

IE11 Results

 

Waterfox x64 results

 

Test your browser and show results.

 

[_neutrino Veteran]

Here is mine

[123456789A]

IE11 - 3020

Firefox - 4338

 

Since IE11 only has 5/7 of the "capabilities", does it just not get points at all in those categories, because if that's the case I'd say it's competitive in speed.

[riceBox]

[+virtorio MVC]

Chrome 39 running on OS X 10.10.1

[adrynalyne]

It should be noted that these scores are hardware dependent.

[Krome]

Wow you guys got the score up so high... I got a 6 core with hyperthread which amounts to 12 processor count... and yet my score is low... not fair at all...

 

You guys above that show your result, can I asked your hardware spec please...?

 

I have Core i7 980 3.33GHz and 24GB of RAM... GeForce GTX 560 Ti (with 2GB)

 

[Boo Berry]

Wow you guys got the score up so high... I got a 6 core with hyperthread which amounts to 12 processor count... and yet my score is low... not fair at all...

Try a different browser like Chrome/Opera or Maxthon. Anyways, here's mine (using Chrome Canary 41.0.2215.0);

 

[Kelxin]

 

[blade1269]

Any one using Gloubus from the front page in the software section ? Looks interesting.

[Draconian Guppy]

Opera 1790 Points

 

Version info Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.111 Safari/537.36 OPR/25.0.1614.68 Comment  

Suite

Result

Rendering

8.39

 

renderGrid01

20.32 fps

 

renderGrid02

1.00 fps

 

renderGrid03

11.79 fps

 

renderPhysics

20.62 fps

 

HTML5 Capabilities

7/7

 

webglSphere

Yes (26.86 fps)

 

videoPosterSupport

Yes

 

videoCodecH264

Yes

 

videoCodecTheora

Yes

 

videoCodecWebM

Yes

 

workerContrast01

Yes (10082.17 ops)

 

workerContrast02

Yes (29951.06 ops)

 

gamingSpitfire

Yes (49.90 fps)

 

HTML5 Canvas

4.43

 

experimentalRipple01

19.40 fps

 

experimentalRipple02

1.01 fps

 

Data

71327.67

 

arrayCombined

15139.50 ops

 

arrayWeighted

336050.50 ops

 

DOM operations

22164.14

 

domGetElements

1835216.50 ops

 

domDynamicCreationCreateElement

26028.83 ops

 

domDynamicCreationInnerHTML

33339.00 ops

 

domJQueryAttributeFilters

10377.00 ops

 

domJQueryBasicFilters

2918.50 ops

 

domJQueryBasics

8291.00 ops

 

domJQueryContentFilters

4177.50 ops

 

domJQueryHierarchy

14829.20 ops

 

domQueryselector

52106.50 ops

 

Text parsing

312837.45

 

stringChat

101225.21 ops

 

stringDetectBrowser

969746.25 ops

 

stringFilter

65852.53 ops

 

stringValidateForm

1301207.00 ops

 

stringWeighted

356228.00 ops

[Kelxin]

If anyone is wondering:

 

i7 4790 @ 3.6 Ghz

32 GB DDR3 @ 2400 Mhz Dual Channel

Samsung XP941 SSD @ 1.2 GB/s 

EVGA Nvidia GTX 760 Superclocked

ASRock Z97 Extreme 9

[Krome]

6167... can't believe my eyes... that's almost double my score... :/

[Hum]

After some tweaks, I managed to go from 1741 to 1793. -->  Firefox

 

Oh dear -- must build faster desktop.

 

Here are some tweaks that work with Firefox, up to version 21.0 -- above that, I do not know.

 

You might want to set a Restore point before you tweak ...

 

 

Here's something for broadband people that will really speed Firefox up:

1.Type "about:config" into the address bar and hit return. Scroll down and

look for the following entries:

network.http.pipelining network.http.proxy.pipelining

network.http.pipelining.maxrequests

Normally the browser will make one request to a web page at a time. When you

enable pipelining it will make several at once, which really speeds up page

loading.

2. Alter the entries as follows:

Set "network.http.pipelining" to "true"

Set "network.http.proxy.pipelining" to "true"

Set "network.http.pipelining.maxrequests" to some number like 30. This means

it will make 30 requests at once.

3. Lastly right-click anywhere and select New-> Integer. Name it

"nglayout.initialpaint.delay" and set its value to "0". This value is the

amount of time the browser waits before it acts on information it receives.

If you're using a broadband connection you'll load pages MUCH faster now!

 

 

 

Safari for Windows surprise -- only scored 1295.

 

IE 10 scored 1427.

 

Firefox had the best score for me. :p

[The_Decryptor Veteran]

woohoo!

 

After some tweaks, I managed to go from 1741 to 1793. -->  Firefox

 

Oh dear -- must build faster desktop.

 

Here are some tweaks that work with Firefox, up to version 21.0 -- above that, I do not know.

 

You might want to set a Restore point before you tweak ...

 

 

Here's something for broadband people that will really speed Firefox up:

1.Type "about:config" into the address bar and hit return. Scroll down and

look for the following entries:

network.http.pipelining network.http.proxy.pipelining

network.http.pipelining.maxrequests

Normally the browser will make one request to a web page at a time. When you

enable pipelining it will make several at once, which really speeds up page

loading.

2. Alter the entries as follows:

Set "network.http.pipelining" to "true"

Set "network.http.proxy.pipelining" to "true"

Set "network.http.pipelining.maxrequests" to some number like 30. This means

it will make 30 requests at once.

3. Lastly right-click anywhere and select New-> Integer. Name it

"nglayout.initialpaint.delay" and set its value to "0". This value is the

amount of time the browser waits before it acts on information it receives.

If you're using a broadband connection you'll load pages MUCH faster now!

The majority of these tweaks do nothing (Pipelining is hard limited to 8, and doesn't help much), and the only one that has any effect (Paint delay) actually slows things down, so don't do this.

[Hum]

The majority of these tweaks do nothing (Pipelining is hard limited to 8, and doesn't help much), and the only one that has any effect (Paint delay) actually slows things down, so don't do this.

 

 

1741 to 1793 ..... something worked for me. ;)

[The_Decryptor Veteran]

That's noise, so no.

And pipelining only helps when loading data off the network (Reuses a connection to avoid TCP slow start), so it isn't going to help a CPU benchmark in the slightest. Lowering the paint delay causes more CPU contention since it's trying to redraw the page as data comes in (While if it waits a bit, it has the data so can do less work)

[Alwaysonacoffebreak]

WebM test? Since when is that an standard for browsers to use?

 

2200 on Windows 10 on IE11

[The_Decryptor Veteran]

WebM VP8/VP9 is as much a standard as H.264 is.

Most benchmarks just test if they work, don't actually award a score because of it.

[FiB3R]

[simonlang]

It should be noted that these scores are hardware dependent.

 

indeed. this has nothing at all to do with a browser-benchmark. if i would have known what i was in, i would have at least closed a few tabs and programs before running this piece of ... you know... 

[nosense]

[Avijit]

:woot: Opps... its 3146!! How to make it fast ...then   :s

[Max Norris]

I always take these with a grain of salt.. speed can be subjective and the results can be wildly inconsistent.  Chrome usually takes the lead for the synthetic benchmarks (although Firefox is getting reeealy close now), but more often than not day-to-day "feels faster" seems to be with Firefox.