Pretty useful. I did some quick mods and went from a 89 to 98 pretty quickly which isnt too bad.
Only complaint is that I had to click to expand out the page speed problems. You might want to add a horizontal triangle or some other visual indicator there is more to look at. Either that or expand them all by default but allow people to close them.
Only issue was that it suggested I could minify my JS and gain a 0% reduction in a few cases.
There is always a fair amount of noise which I just tend to ignore. YSlow always penalises me for not using a CDN for example.
Something useful to add would be links for the compressed images you use to work out how compressing the images could save space. A side by side comparison would be pretty useful so I could see how the compressing changes the look of the page.
Just for fun I ran it over http://duckduckgo.com which comes back with 100. Google comes back with 98. Interesting.
Comments
Pretty useful. I did some quick mods and went from a 89 to 98 pretty quickly which isnt too bad.
Only complaint is that I had to click to expand out the page speed problems. You might want to add a horizontal triangle or some other visual indicator there is more to look at. Either that or expand them all by default but allow people to close them.
Only issue was that it suggested I could minify my JS and gain a 0% reduction in a few cases.
Wow, 98 is a great score (higher than Google!)
You're right, there's a lot of noise in the results. If the size reduction is small, like a few bytes, there's no need to show that.
There is always a fair amount of noise which I just tend to ignore. YSlow always penalises me for not using a CDN for example.
Something useful to add would be links for the compressed images you use to work out how compressing the images could save space. A side by side comparison would be pretty useful so I could see how the compressing changes the look of the page.
Just for fun I ran it over http://duckduckgo.com which comes back with 100. Google comes back with 98. Interesting.