Dumb SEO Questions

(Entry was posted by David Jones on this post in the Dumb SEO Questions community on Facebook, Wednesday, January 21, 2015).

New warnings from Google regarding mobile usability for sites

I have been reading about the new warnings from Google regarding mobile usability for sites, right now I have no direct warnings from Google in WMT about my sites but decided to check some that I have deployed a new responsive theme to with the mobile usability tool.

I have this new theme on 4 sites and 3 have no or very few warnings (less than 10 out of thousands of pages) but one site Forevergeek DOT com it says that 1, 296 pages have problems with `content not sized to view port` and `touch elements too close`. The former part definitely is not true as this theme was built with mobile in mind and works perfectly on mobile and tablets and is fully responsive, I also tested some of these pages that Google said were a problem using their own page insights tool and they all got 99/100 scores for UX.

However they also all got very poor scores of less than 50/100 for page speed issues but this is nothing to do with the two warnings given in WMT for mobile usability.

Im going to try and improve the page load times but what should I do about the other warnings regarding content size for viewports and touch elements? I dont see how I can improve things any more on this site in question.

Also these are 3 other sites all running the exact same theme but when I tested these for mobile usability Google said only a handful of pages had problems or that they were all fine...

socialnewsdaily dot com
thedailymind dot come
celebrific dot com?

This question begins at 00:25:27 into the clip. Did this video clip play correctly? Watch this question on YouTube commencing at 00:25:27
Video would not load
I see YouTube error message
I see static
Video clip did not start at this question

YOUR ANSWERS

Selected answers from the Dumb SEO Questions G+ community.

  • David Jones: I have been reading about the new warnings from Google regarding mobile usability for sites, right now I have no direct warnings from Google in WMT about my sites but decided to check some that I have deployed a new responsive theme to with the mobile usability tool.

    I have this new theme on 4 sites and 3 have no or very few warnings (less than 10 out of thousands of pages) but one site Forevergeek DOT com it says that 1,296 pages have problems with 'content not sized to view port' and 'touch elements too close'. The former part definitely is not true as this theme was built with mobile in mind and works perfectly on mobile and tablets and is fully responsive, I also tested some of these pages that Google said were a problem using their own page insights tool and they all got 99/100 scores for UX.

    However they also all got very poor scores of less than 50/100 for page speed issues but this is nothing to do with the two warnings given in WMT for mobile usability.

    Im going to try and improve the page load times but what should I do about the other warnings regarding content size for viewports and touch elements? I dont see how I can improve things any more on this site in question.

    Also these are 3 other sites all running the exact same theme but when I tested these for mobile usability Google said only a handful of pages had problems or that they were all fine...

    socialnewsdaily dot com
    thedailymind dot come
    celebrific dot com
  • Mark Steenbakkers: Hi , do you use different plugins, extensions on this particular site? I checked your website in the W3C HTML Validator and CSS Validator and both reports show a lot of errors. I recommend fixing these errors and check if you still get the same warnings.

    W3C CSS Validator


    W3C HTML Validator:


    PS: It looks like your using <b>Lazy Load</b> or a similar plugin to load your content. Content loaded via Ajax does not get index by Google directly, you need to create HTML snapshots in order to get your content indexed.

    

View original question in the Dumb SEO Questions community on Facebook, Wednesday, January 21, 2015).

Reference Links