I'd like to ask you a question about mobile friendly.
Which barometer can ensure that a webpage is recognized as fully mobile-friendly one by google?
There are many sigals/tools Google offer for mobile-friendliness.
1: "Mobile-Friendly" label on SERPs
2: "Mobile Friendly Test" tool
3: "Mobile Usability Report" in GWT.
4: PageSpeed Insight
As long as I've learned from you and other Googlers, 1/2/3 are based on similar or the same mechanism using Googlebot, and 4 is different using more user-like setting.
But in some cases, results of 1/2/3 can be inconsistent.
In forum, there are feedbacks that pages passed MFT got mobile usability warning message on GWT, or can't get "Mobile-Friendly" labels.
Which one is most suitable checkpoint to confirm that a webpage is recognized as a perfectly mobile-friendly page by Google?
e.g. Forum threads reporting inconsistency.
2 plus ones
Shared publicly•View activity
- That's a good question :). We should be a bit cleaer. The mobile-friendly label in search is based on the mobile-friendly test, so that's at least connected directly. The messages sent out are based on all URLs from a site, and it's possible that some sites have a mobile-friendly homepage, but not all sub-pages are. Page Speed Insights adds a bunch of technical measurements which are equally relevant for the webmaster and their users. Does that help?
For what it's worth, I'd expect these criteria to evolve over time (maybe more factors, maybe simplified), but they'll also converge a bit. The Page Speed Insights one will probably remain separate, because it is really focused on the UX more than on search.Mar 5, 2015
- Thank you for clarifying most of the points,! It really helped me.
But I still have one question.
As they don't report details in JP examples, it is possible that they checked their homepages, not the specific URLs.
But in EN example, the webmaster clearly reports that he got Mobile Usability error message on URLs which passed MFT.
Isn't it inconsistent?
https://productforums.google.com/forum/#!searchin/webmasters/WNC-451500%7Csort:date/webmasters/Fi4M1pCjItI/dXezoCNDkhAJMar 5, 2015
- Their robots.txt file changed significantly recently, that would be my guess. If css/js is blocked from crawling, we can't see the page as mobile-friendly. If you change that, it'll still take a while for all of that to update. Not mentioning these kinds of changes in the thread doesn't really help.Mar 5, 2015
- I got it! It seems that they made the change after Jan 24 this year.
I appreciate a lot for your sincere lectures.Mar 5, 2015
- And another feedback and question to you.
A JP webmaster reports that he failed in mobile friendly test due to number of CSS.
He used 20 CSS on a page when failed, and as he compressed it into 10 the page passed the test.
Are there maximum number of CSS googlebot can read?
https://productforums.google.com/forum/#!category-topic/webmaster-ja/wlc8xW9bX90Mar 5, 2015
- No, Googlebot will cache the CSS files and keep trying until it has them all. However, the testing tool times out after a certain time, and that's probably what's happening here. Fewer CSS files is always good, especially on mobile sites - each additional file takes a lot of time to download on a phone. However, it's not required in this specific case.Mar 6, 2015
- Ah timeout, it is quite reasonable.
So that's the same reason as some interstitial popups are not reflected to rendered images if they are displayed at certain time after landing.
Thank you a lot, John!Mar 6, 2015
- Very useful discussion！Mar 13, 2015