These are two of the most common mobile usability alerts raised by Google search console or a Mobile-Friendly Test are Text too small to read and Clickable elements too close together. However, they are often false negatives, and many clients find themselves at a loss on how to resolve the issue.
The potential reasons for these errors are:
- The text is too small to read and or clickable elements are too close together.
- The website needs optimising to make it easier for Google to perform a valid test.
- They are a false negatives due to crawling and testing of sites when Google server resources are low. See point 2.
Perform a visual check
If you receive an alert, the first thing is to check the affected pages on a real mobile device. Use an Incognito / Private browsing session to eliminate viewing a cached version of the page instead of the latest version.
Note: some routers and ISPs also cache pages so you may want to also check on a different network. If in doubt, ask me to check for you.
My page looks a horrendous!
If your site looks broken it’s likely missing styles, in this case these alerts are just symptoms of a more significant issue. It’s more likely related to caching or the server not completing the necessary requests resulting in 404 or 500 errors. The first step in diagnosing an issue is to disable any cache or optimisation plugins temporarily. Then review the site again.
If you’re finding you need to pinch-zoom to read the text easily, then your text is too small to conform to legibility guidelines. Whether Google alerted you or not, increase your font-sizes and line-heights (if necessary) to remedy this issue. I recommend a minimum body font size of 16px.
You should be able to click an element without your fingertip overlapping a neighbouring clickable element. If that’s not the case, then look at increasing its size.
If your having difficulty identifying an issue then run a Chrome developer tools Lighthouse report:
My site passed all of the tests, so why am I still receiving these alerts?
- Blocked by Robots.txt
- Other error
To find out which ones are the cause run a mobile-friendly test:
Blocked by Robots.txt
You’ll need to enlist my services to help you sort this one out.
This somewhat ambiguous error means your website exceeded Google’s server resource limit. The number of network requests your site required or the time it took to complete them.
There are many factors in how the Google resource limit is calculated when it crawls and fetches your site. But it also varies considerably depending on how busy its servers are at the time.
To eliminate the possibility that Google is extremely busy, take a break and come back later and perform another Mobile-Friendly Test. Remember running continuous tests of your site will place more strain on their server’s resources and increase the chances of more failed tests.
Continual mobile usability alerts or Mobile-Friendly Test Fails
If your site continues to fail its test due to the Other issue, your site could probably do with some optimisation. The better your site performs, the less likely it will exceed Googles available resources.
Optimisation is a complex task that varies from site to site. However, one of the main issues I see is websites making a large number of network requests. You can get a quick summary of this by using many online testing tools such as GT Metrix.
If your site is making 50 or more requests, (I have seen cases of 300+!) you need to reconsider what is essential and look at trimming back on plugins, fonts, images or adverts.