Site logo

Archived topic

Google finds page not mobile friendly

5 replies · Started by Bijaya on February 7, 2021

Viewing posts 1–6 of 6

Hi there,

After the recent update I find these messages in search console stating that my page is not mobile friendly:

Clickable elements too close and text too small to read.

I am going ahead and adding the screenshot which according to Google shows the part of the page that is not mobile friendly: https://imgur.com/a/HeUtpHa

I have not used any page builders and only GeneratePress and the pages come off as "not mobile friendly". Can you please check and help me fix this?

Thanks,
-Swadhin

Hi David,

Thanks so much for the reply. :)

I went ahead and tested the page using Chrome's inspect tool and on mobile. I saw that I have that a sidebar menu (with different items in menu than the desktop version). They are also large enough and well spaced.

But in the screenshot provided above, Google shows my desktop menu as my menu on mobile menu and reports that it has the two issues (small text and close text).

Would you please mind checking the URL (that I have shared earlier) and see if there is any issue.

I have previously ignored false positives by Google but this time it shows when trying to index those URLs and hence I fear will affect their rankings too.

I can share the login information with you in case you want to see what's going on. I'll appreciate it if you could do that please.

Best,
-Swadhin

So - based on your screenshot its a simple case that Google didn't complete the resource requests to load the necessary stylesheets/scripts - which results in the broken preview and those errors.

Sometimes this is purely down to Googles test servers being overburdened. To reduce the chances of this occurring requires better optimization of the site.

Anything you can do to reduce the number of requests, or make smaller requests, will lighten the load on Googles servers and minimize the chances of it failing to load properly.

Things that can be done:
1. Look at cutting back on 'unnecessary' resources, for example your site is loading 3 separate icon fonts - FontAwesome ( 2 x requests ), Icomoon and Social Snap. Thats 4 requests and around 280kb of data for what is probably just a handful of icons.

2. 3rd Party requests, any request being made front to a 3rd party server requires additional DNS lookups and their network request time is out of your hands. You can use a plugin like Flying Scripts to defer those 3rd party requests.

Hi David,

Thanks so much!

As always, you're really kind to help and see that me (or GP users) actually solve their issues and get benefitted even if that doesn't involve the theme's area.

These insights that you gave me opened up my eye! My site is over 7 years young now and so over time these things accumulated. I always knew I had to optimize my site for speed but your insights on these font family issue is something that shows how badly i need to optimize.

Thanks again for these tips, I'm working on fixing them.

Glad to be of help!

This archived topic is closed to new replies.