4 ms·
I don't understand. Why not simply use PageSpeed where it tells you exactly what to fix to improve each aspect? https://developers.google.com/speed/pagespeed/i
by Jugurtha 10y ago
I don't understand. Why not simply use PageSpeed where it tells you exactly what to fix to improve each aspect?
https://developers.google.com/speed/pagespeed/insights/ https://developers.google.com/speed/pagespeed/insights/
- shakna 10y agoThey seem to be in the process of replacing PageSpeed. First: > PageSpeed Insights has moved the User Experience test for mobile pages into the Mobile Friendly Test And then a bigger launch about this fancier version.
- Jugurtha 10y agoMobile Friendly(MF) is worse than PageSpeed Insights(PSI) in every possible (perceivable) way: - PSI is fast. MF is slow. - PSI is general (mobile and desktop). MF is, well, for mobile. - PSI just asks for the site, gives you results. MF checks if you're a robot, you check a site, and checks again you're not a robot if you want to use it again. - PSI gives you exactly what's wrong with your site, which rules were broken, and how to fix them. Which lines to add to your CSS. Where to add them (deferring loading CSS if you want to, adding JavaScript), and gives you a score for each thing, if you change stuff you can look at your score improve. It then orients you to resources for additional reading. MF is binary: good, not good. Doesn't give you info. Doesn't give you actionable info. Gives you basically nothing. I don't see any reason to use MF (or for it to even exist under its current form and non-features) and every reason to use PSI. Then again, every time I discover a Google product, after a few days I have the misfortune of seeing a red warning telling me it'll be discontinued. It's happened many times.