https://mozilla.github.io/arewefastyet-speedometer/2.0/
i5-3570k, 16 GB RAM, x64 browsers, i didn't look at memory usage
started with clean Profile each time, except as noted
didn't particularly limit my actions, but didn't necessarily
also sit on the test window the full time, exception noted
i guess you do need to understand the test :about, in particular
if you go comparing against other browsers or browser versions
Code: Select all
Firefox:
45 25.90 45.0.2 "dirty"
45 35.39 45.0.2 clean
56 46.94 56.0.2 clean
56 22.73 56.0.2 + noscript 5.1.7, temp.allow.github
Iteration 1 46.43 runs/min background actions ongoing
Iteration 2 45.86 runs/min window did not have focus
Iteration 3 10.14 runs/min i opened a different browser
Iteration 4 5.514 runs/min [not FF] session & was
Iteration 5 5.496 runs/min posting a thread on a board
Iteration 6 5.463 runs/min don't know why the iterations
Iteration 7 5.467 runs/min go as they did ?
Iteration 8 11.25 runs/min 40-40-10-5-5-5-5-10-40-40 ?
Iteration 9 44.96 runs/min i only went back to the test
Iteration 10 46.75 runs/min when it was appropriate for me,
so not necessarily when it finished
56 45.28 56.0.2 + noscript 5.1.7, temp.allow.github,
2ND.RUN, in forground, no other actions ongoing,
note: same results as with "56 clean"
56 42.02 56.0.2 + noscript 5.1.7 + uBlock Origin 1.4.16
57 53.67 57.0 clean
57 52.35 57.0 + noscript 10.1.2, temp.allow.github
57 47.80 57.0 + noscript 5.1.7 + uBlock Origin 1.4.16
SeaMonkey:
249 25.44 2.49.2
256 36.25 2.56a1
Well, per the test, 57 > 56 > 45 ~= SeaMonkey 2.56a1
Now, what does that mean - in the real world.
A world where "fast" is not an end-all.
A world where extensions are used, & do matter.
A world where people do care about the look of "their"
browser & how they're able to change it & make it look &
react the way "they" want it.
So, arewfastyet?
Hardly.
Do we gain by giving up.
No.