Google says some pages have mobile usability issues

Hi there,

So I ran a Google Mobile-Friendly search on your website for myself, and I didn’t encounter the issues you stated previously. I’d try running the search on a different browser as you may have extensions installed that could possibly be conflicting with the results.

All page resources were loaded without any problems according to the user agent, however, the only problem was loading JavaScript content via an HTTPS connection (which won’t affect the optimization as they are only warnings).

If you still encounter this problem on another browser, please take a screenshot of the results so I may see why this is happening.

Thanks,
Tyler

• This reply was modified 5 years, 7 months ago by Marius L. J.. Reason: Removed signature

Thanks for your message. I ran the test with another browser, but it doesn’t make any difference. Live page is mobile friendly. It is just Google Search Console which says it is not.

I think the problem is that the page Google indexed is not mobile friendly. Inspection from Google index says it is not mobile friendly. Inspection from live url is mobile friendly. I’m talking about my landing page. Indeed there was an issue with mobile 14 days ago. But I fixed that.

Maybe I just need to wait a bit more. What is confusing that the last crawled date is from today.

Hi there,

Google will index the entire site and will return any rendering issues it had on the way there. Google could be indexing a cached version of your site, so if you have any caching plugins installed or use a hosting provider that utilizes caching then flush the cache and see if the issue persists. The landing page is the first result that Google will respond with, and that doesn’t appear to have any issues on my side. I have manually tested each page on the site and haven’t encountered any issues from Google.

Once you have flushed the cache please try the test again and see if the messages are still being displayed. If they are still being displayed, could you please take a screenshot of them and attach it in your next response?

Thanks!
Tyler

• This reply was modified 5 years, 7 months ago by Marius L. J.. Reason: Removed signature

Thanks – I appreciate that you are taking the trouble to find out with me what is going on.

Here are the steps with a link to my website for screenshots.

– First I go to Google Search Console, click Mobile Usability, screenshot 1
– I click “Text to small to read” and it will list all pages with issues
– I click my landing page a window open at the right
– I click the Inspect button, see screenshot 2
– I click button Test Live URL, see screenshot 3, page looks mobile friendly. So page from Google Index is not mobile friendly, but it is from Live URL
– I click the refresh button next to “tested…” in the Live test view.
– I go back to the Google Index, screenshot 4 and click the “request indexing” button

https://edywerder.ch/mobile-usability/

I requested reindexing last night for all 10 pages which shows issues. I guess it takes a bit time. I use the W3 Total cache plugin and Bunny CDN. I cleared the cache several times in the plugin and clear cache on Bunny CDN.

I’m not sure reindexing will help. See screenshot 5, last crawled date was from yesterday afternoon. At this time the page was already mobile friendly.

Thanks
Edy

Hi Edy,

Thank you for posting those screenshots. If this issue still persists, even though it looks like the latest indexing was yesterday approximately, then I’d go ahead and address the issues Google is reporting back with. I will help address the two issues being shown.

So, it looks like the first problem in the mobile layout is “Text too small to read”. My first recommendation might be redundant, but it might still be relevant to this issue at hand. You might try increasing the font size, which WordPress does offers options to increase the font sizes across the website. You can also test this on larger screens to ensure it won’t break any original features.

Mobile devices have much more densely packed pixels on their screens. This means that something should as 20px on a desktop/laptop could appear to be 10px on mobile devices. This is why most responsive designers don’t use pixel-based font measurements, as it shows to be inaccurate according to the respective screen sizes. Sometimes you can get this error even if the site’s design is responsive, but someone could have written text in the WordPress text editor which appended the styling information (including the px font size), which is then inlined and overriding your old CSS style rules).

As for the issue regarding, “Clickable elements too close together”. Could you try looking at the page loading issues in the Google mobile-friendly tool, you should be able to see some CSS stylesheet URLs blocked by robots.txt – Please try unblocking those.

Thanks!
Tyler

• This reply was modified 5 years, 7 months ago by Tyler.
• This reply was modified 5 years, 7 months ago by Marius L. J.. Reason: Removed signature

Thanks Tyler

When I run the mobile friendly test and look at the details there are a lot of Javascript console error. Mixed content with loading paged HTTPS and HTTP. I use a CDN and W3 Total Cache. If I disable W3 Total Cache, there are absolutely no errors.

I think the problem could be related to the Cache Plugin. I posted a question here in the plugin forum.

Cheers
Edy

Hi Edy,

Yes, this makes sense, as WordPress caching plugins tend to cache elements that were previously found in the site that Google views as not being mobile-friendly. This is why I asked earlier if you were in fact using caching because the actual plugin within WordPress is probably still caching outdated CSS stylesheets that are resulting in this incompatibility with Google results. You might consider reaching out to them and ask why it’s still adding reminiscing files/stylesheets even after the cache is being flushed out, as this is resulting in the errors from Google.

Thanks!
Tyler

• This reply was modified 5 years, 7 months ago by Marius L. J.. Reason: Removed signature

Hi Tyler

Thanks for your message. It really looks there is a problem between BunnyCDN and W3 Total Cache. As a further test I disabled in the cache plugin CDN. Ran the mobile friendly test again and i had no problem.

So in a summary Mobile friendly test has absolutely no issues when
– only CDN is enabled
– only W3 Total Cache is enabled
– has lots of issues with http and https content when W3 Total Cache uses BunnyCDN.

Thanks,
Edy