Improved UX for the numbers

[sindresorhus]

I have no idea what these numbers means:

Leverage browser caching                   | 9
Minimize render blocking resources         | 24
Optimize images                            | 2.82
Size tap targets appropriately             | 0.01

[PaulKinlan]

I believe these are rule impact.... It should be in the psi docs :)

On Sun, 11 Jan 2015 11:56 Sindre Sorhus notifications@github.com wrote:

I have no idea what these numbers means:

Leverage browser caching | 9
Minimize render blocking resources | 24
Optimize images | 2.82
Size tap targets appropriately | 0.01

—
Reply to this email directly or view it on GitHub
#41.

[PaulKinlan]

However even then it makes little sense as they don't really relate to each
other

On Sun, 11 Jan 2015 11:57 Paul Kinlan paul.kinlan@gmail.com wrote:

I believe these are rule impact.... It should be in the psi docs :)

On Sun, 11 Jan 2015 11:56 Sindre Sorhus notifications@github.com wrote:

I have no idea what these numbers means:

Leverage browser caching | 9
Minimize render blocking resources | 24
Optimize images | 2.82
Size tap targets appropriately | 0.01

—
Reply to this email directly or view it on GitHub
#41.

[sindresorhus]

https://developers.google.com/speed/docs/insights/v1/getting_started

The PageSpeed Score (0-100) indicates how much faster a page could be. A high score indicates little room for improvement, while a low score indicates more room for improvement.

Maybe it would make more sense to show those number as percentage?

[PaulKinlan]

Its not a percentage, because the other scores aren't linear.

On Sun, 11 Jan 2015 12:03 Sindre Sorhus notifications@github.com wrote:

https://developers.google.com/speed/docs/insights/v1/getting_started

The PageSpeed Score (0-100) indicates how much faster a page could be. A
high score indicates little room for improvement, while a low score
indicates more room for improvement.

Maybe it would make more sense to show those number as percentage?

—
Reply to this email directly or view it on GitHub
#41 (comment).

[sindresorhus]

So then, how would I as a user know what 2.82 means? The PageSpeed doesn't AFAIK say anything about that.

[PaulKinlan]

You are correct in that the documentation is no help. We should help on
that. Let me talk to the team on that.

On Sun, 11 Jan 2015 12:11 Sindre Sorhus notifications@github.com wrote:

So then would I as a user know what 2.82 means? The PageSpeed doesn't
AFAIK say anything about that.

—
Reply to this email directly or view it on GitHub
#41 (comment).

[silvenon]

So 0.01 is extremely bad then, right?

I'm just gonna slap the good ol' 👍

[johnbburg]

I believe under some rules, lower is better. But yes, I have no way of knowing what any of these mean, and the documentation doesn't discuss specific rule values from what I've found so far.

[marcofugaro]

👍 I didn't understant what are those numbers either

[faresite]

Can't understand the numbers either. 😢