PageSpeed Insights not seeing my mobile site

[Robert Buehler]

I am using WP Touch Pro (version 3.4.5) to render a mobile optimized site for my users.  When I run pagespeed insights, it only analyzes my desktop site, even on the mobile tab.

I assume the problem is that WP Touch doesn't recognize the googlebot User Agent as mobile. 

Two questions:

1)  WP Touch allows me to enter a custom User Agent to make sure it displays the mobile site.  What User Agent string should I use for this?  None of the following seem to do the trick:

Mozilla/5.0 (iPhone; CPU iPhone OS 6_0_1 like Mac OS X) AppleWebKit/537.36 (KHTML, like Gecko; Google Page Speed Insights) Version/6.0 Mobile/10A525 Safari/8536.25

Mozilla/5.0 (iPhone; CPU iPhone OS 6_0_1 like Mac OS X) AppleWebKit/537.36 (KHTML, like Gecko; Google Page Speed Insights) Version/6.0 Mobile/10A525 Safari/8536.25 GoogleBot/2.1

Googlebot/2.1 (+http://www.google.com/bot.html)

Mozilla/5.0 (compatible; Googlebot/2.1; +http://import.io)

Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

2)  I know Google partly bases SERP results on mobile performance.  Is there a different user string I should enter to make sure Google is giving me "credit' for having a properly optimized mobile site, but still seeing the desktop version correctly?

Thanks, Rob

[Dave Mankoff]

Howdy Robert. Answers are inline below.

-dave mankoff

man...@google.com

On Thu, Aug 7, 2014 at 10:07 PM, Robert Buehler <r...@goldenservices.com> wrote:

1)  WP Touch allows me to enter a custom User Agent to make sure it displays the mobile site.  What User Agent string should I use for this?  None of the following seem to do the trick:

Mozilla/5.0 (iPhone; CPU iPhone OS 6_0_1 like Mac OS X) AppleWebKit/537.36 (KHTML, like Gecko; Google Page Speed Insights) Version/6.0 Mobile/10A525 Safari/8536.25

Mozilla/5.0 (iPhone; CPU iPhone OS 6_0_1 like Mac OS X) AppleWebKit/537.36 (KHTML, like Gecko; Google Page Speed Insights) Version/6.0 Mobile/10A525 Safari/8536.25 GoogleBot/2.1

Googlebot/2.1 (+http://www.google.com/bot.html)

Mozilla/5.0 (compatible; Googlebot/2.1; +http://import.io)

Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

The user agent for PSI should always contain "Google Page Speed Insights". Other elements of it may be subject to change. For instance, PSI currently masquerades as an iPhone; how it is not impossible that we will switch to an Android at some point. You should be able to find our current, full user agent in your logs when using PSI. 

 

2)  I know Google partly bases SERP results on mobile performance.  Is there a different user string I should enter to make sure Google is giving me "credit' for having a properly optimized mobile site, but still seeing the desktop version correctly?

Google's Webmaster documentation provides details about this: https://developers.google.com/webmasters/smartphone-sites/

Our user agents are specifically listed here: https://developers.google.com/webmasters/smartphone-sites/googlebot-mobile. Again, note that this will change over time.

I would lastly note that doing user-agent detection is generally discouraged. This is talked about here: https://developers.google.com/webmasters/smartphone-sites/redirects

Responsive, adaptive, and other forms of design that deliver the same content to all clients is Google's general recommendation: https://developers.google.com/webmasters/smartphone-sites/details

[Rick Steinwand]

On Friday, August 8, 2014 9:15:41 AM UTC-5, Dave Mankoff wrote:

I would lastly note that doing user-agent detection is generally discouraged. This is talked about here: https://developers.google.com/webmasters/smartphone-sites/redirects

Responsive, adaptive, and other forms of design that deliver the same content to all clients is Google's general recommendation: https://developers.google.com/webmasters/smartphone-sites/details

This ^^^^^^^^

Exactly what I was going to suggest. (You're overthinking the problem.) 

[Carlos Lizaga Anadon]

User agent is discouraged to be used for redirects to a different content for mobile themes but keep in mind that you can still use it to detect things like screen size...etc so you can still use it to increase your user experience. Of course, without redirects.

Regards.