Google Pagespeed Test Fails Itself on Mobile
11–20 of 33 posts
Re: Google Pagespeed Test Fails Itself on Mobile
#12Re: Google Pagespeed Test Fails Itself on Mobile
#13Re: Google Pagespeed Test Fails Itself on Mobile
#14Re: Google Pagespeed Test Fails Itself on Mobile
#15If Google make a developer oriented tool then it is no surprise that it works brilliantly on the desktop and slightly sub-optimally on the mobile phone. I am quite useless at web design yet I can game Pagespeed to get 95% or higher in the score. Of course the javascript will be mashed into some black hole that can't be un-minified and the way things load will not be well suited for the visitor seeing more than one page (using cached things). I can't believe someone at Google could not have done what I do to 'game' Pagespeed. The fact that they haven't is good, you should never let scores from things like Pagespeed or YSlow determine how a web page is delivered, it is like using a 'defeat device'.
I do wish they would do something to Pagespeed as they have changed what it does over the years and the latest iteration didn't excite me, I preferred the previous one, in part because you could run it against 'localhost'.
Re: Google Pagespeed Test Fails Itself on Mobile
#16Anyway, the PSI 'score' is only a rough guide to help point you to problems. It can be kind of useful, in that if you get something like 97-100 then you can be pretty sure it's a very fast page... but it's also probably a page that doesn't do much beyond displaying something. With a more serious web app that does more interesting things, the score becomes a less useful indicator – it's often possible to make code changes that improve perceived performance but actually reduce the PSI score.
For example, it's impossible for PSI to really know if inlining a script is going to generally improve or worsen performance, because it doesn't know your site's usage patterns, or which parts of your UI need to render first for a user to feel that the your UI 'is fast', whatever that means. UI performance is a subtler art than, say, algorithmic performance, and much less quantifiable. That's why many people prefer webpagetest.org, which comes with much smarter tools to record and analyse how the page loads, so you can actually improve UI performance.
Re: Google Pagespeed Test Fails Itself on Mobile
#17This is a nice tool to give you suggestions about things you might want to change but it's hard to use it as a predictor of page quality.
Re: Google Pagespeed Test Fails Itself on Mobile
#18cnn.com gets 95/100 on mobile user experience which must be a joke of some kind. My own page (the development version) gets a similar score in spite of loading much must faster. reddit.com also almost fails the desktop test. This is a nice tool to give you suggestions about things you might want to change but it's hard to use it as a predictor of page quality.
https://developers.google.com/speed/pagespeed/insights/?url=...
Re: Google Pagespeed Test Fails Itself on Mobile
#19Re: Google Pagespeed Test Fails Itself on Mobile
#20[1] https://developers.google.com/speed/pagespeed/insights/
[2] https://developers.google.com/speed/pagespeed/insights/?url=...