-
Notifications
You must be signed in to change notification settings - Fork 85
Change the score scale from 140 to 100? #401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I don't think we want to do this for 3.0. For 4.0, it's too early to say one way or another. |
I've got feedback from several people that they'd wish just a steady ever-increasing score between releases. While a bit arbitrary, it makes talking about the score quite a bit more intuititve. |
What do you mean by "more intuitive"? |
Comparing devices with a score of let's say 300 meant roughly the same thing with v2.1. With the v3.0 release, all of a sudden the printed score was 10x "slower" and thus purely from a publicity standpoint, the device might be perceived slower. Also with folks who are not dealing with speedometer on a frequent basis we see that there is an implicit assumption of where we are, and how much progress we made based of the score. If we drastically change the score between versions this vague notion is lost. Agreed, this is all a bit fuzzy, and with new releases we're technically not providing the same benchmark. So, comparing scores between versions is definitely not scientifically correct. |
As someone who originally started this post, I agree with the previous poster. The disruption has already been made and the scores 'reset' going from v2 to v3. I do not think that needs to be addressed any more. What I think should be done is to make current scoring future proff so that another 'reset' is not needed again. People want 'stability' and predicatability. One thing I would also suggest: calibrating a score in such way that 1 represents score of a 'reference machine/browser'. This can be anything - pick a commonly used piece of hardware and the browser ti shipped with. Something people would be able to relate to. So then a score of 100 would mean 100x faster than reference. Will help tell good stories. |
Current scale is inherted from Speedometer 2. Where browser went up to 500 in score.
Now max score I've seen is about 35. It makes sense to change the scale and make the max lower, maybe 100, or even 50.
The text was updated successfully, but these errors were encountered: