Windows Desktop Browser Compatibility Comparison - ECMA JavaScript Tests

This page documents a comparison of desktop browser performance in how each of them fares against the suite of JavaScript tests compiled by ECMA. The goal in this comparison is primarily to assess JavaScript compatibility of desktop browsers, and not their execution speed.

The results are given below for the browsers I tend to use. All the tests were run on an ACER Aspire 4730Z, Pentium Dual-core CPU T4200 @ 2.00 GHz with 3GB RAM and Windows Vista Home Premium Service Pack 2, 32-bit:

Latest Public Version as of October 12, 2011

Tested Version on October 1, 2011

Time to run (min.)

Passed tests

Failed tests

Did not load

Tested version on September 1, 2011

Time to run (min.)

Passed tests

Failed tests

Did not load

Tested Version on August 7, 2011

Time to run (min.)

Passed tests

Failed tests

Did not load

Tested version on July 1, 2011

Time to run (min.)

Passed tests

Failed tests

Did not load

ECMA Test Suite Version

11016, ES5, 

  25 September 2011  

11016, ES5,

25 September 2011

10927, 0.7.5.3,

18 July 2011

10927, 0.7.5.3,

18 July 2011

10934, 0.7.5.1,

30 June 2011

14.0.835.202

14.0.835.187

12

10,591

425

0

13.0.782.218

21

10,446

481

1

13.0.782.107

24

10,4462

481

1

12.0.742.112

55

10,427

507

0

7.0.1

7.0.1

15

10,829

187

0

6.0.1

13

10,718

209

0

5.0.1

13

10,627

255

0

5.0

42

10,662

262

0

9.0.8112.16421 (9.0.3 update)

9.0.8112.16421 (9.0.2 update)

20

10,694

322

0

9.0.8112.16421

20

10,634

300

0

9.0.8112.16421

18

10,629

298

0

9.0.8112.16421

20

10,634

300

0

11.51 (1087)

11.51 (1078)

19

7,266

3,750

0

11.50 (1074)

46

6,995

3,873

66

11.50 (1074)

18

7,064

3,863

66

11.50 (1074)

46

6,995

3,939

66

5.1.1 (7534.51.22)

5.1 (7534.50)

Crashes after 1,4921

1,481

9,535

9,524

5.1 (7534.50)

Crashes after 1,7781

1,773

9,154

9,149

5.1 (7534.50)

Crashes after 1,7781

1,773

9,154

9,149

5.0.5 (7533.21.1)

Crashes after ~300

~2,500

~8434

~8,414

1WebKit2WebProcess.exe stops working after being responsible for nearly 90% of the more than 70% of consumption of my PC's memory; I suspect there is a memory leak in this program. 

2Failed tests include those that did not load.