How to Fix, Your page is not mobile-friendly; other error

When you perform a mobile-friendly test on your webpage, and it shows “your page is not mobile-friendly”. There could be three reasons for this, these are:

  1. The page is mobile-friendly in an initial test but after validation of the page shows the same error.
  2. Due to other errors for js and CSS files.

Your page is not mobile-friendly in the mobile usability test.

This error occurs when you check your webpage for mobile-friendliness. This is all because your page may not use a mobile-friendly theme or you’re page content are wider than the screen.

If it is the first case, please use a mobile-friendly theme, and for the second case, please review your content by visiting the site from your mobile device. Check whether it is wider than the screen or not. If there is no such issue then follow the guide below.

Your page is not mobile-friendly Fix
Your page is not mobile-friendly Fix

If you’re using pop-up windows, then it may be possible that the pop-up window you’re using is of fixed size for both mobile and desktop versions. In this case, your page is not responsive due to that pop-up only.

If you are not using a responsive theme or missing tag, then this could be the reason.

Resources are blocked by the robots.txt file.

This error occurs when your page is mobile-friendly for all the devices but not for google bot. This may lead to downgrading your page for the mobile user. In other words, it affects the organic traffic of your website.

This is all due to the robots.txt root file of your website. The Function of the robots.txt file is to control the web crawler to allow or disallow the section. Default robots.txt file blocking the web crawler to access the page resources like JS or CSS files responsible for a responsive website.

How to fix this issue?

For this, you’ve to make changes in the robots.txt file of your website or blog. For WordPress users, permission may be disallowed for the javascript(js) or Cascade Style Sheet(CSS) files. So make the changes in the robots.txt file. Please copy the text file below, and replace it with your robots.txt file.

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Allow: /


After changing your robots.txt file, please validate your mobile-friendly page error. You’ll get a message of successful operation. SEO robots.txt for Blogger and WordPress SERP Improvement (

The page is Mobile-Friendly initially but after validation shows the same error.

If this is the case, when you check your page for Mobile-Friendly Test, the results show Your Page is mobile-friendly, and when you start validation of the page for errors in the Google Search Console. You’ll receive a mail after a few times, that problem not solved.

Now first, we’ve to understand the problem. Which section is wider than the screen after the validation result? Is your webpage support AMP? Then you’ve to check whether your AMP page has issues, its fits within the mobile screen.

Mobile Friendly Page Inspect URL
Mobile Friendly Page Inspect URL

Perform Mobile Friendly Test for Google

In the above case, you’ve to check mobile friendly you can’t perform Mobile-Friendly Test, as that fails later. Here you can perform a live site test that will display what would be the final result. You can try it by disabling the AMP page and also after enabling AMP pages.

Google Search Console Mobile Friendly Live Test
Google Search Console Mobile Friendly Live Test

When you perform the above test for mobile usability in Google Search Console, it will give you the final result that you may expect. If you got errors with the AMP-enabled page and no error after disabling AMP. In such a case, try changing CSS for the object causing the error in the AMP version of the page or disabling the AMP for the particular page.

The resource couldn’t be loaded, other error.

If the above two methods failed for you, then this could be the reason. The website breaks the connection for Google Bots.

In such a case, contact your hosting provider and ask to increase your connection time out, “request time out” at least about 60 seconds. That means the connection can stay for 60 seconds at least for a session to load all resources.

I hope we able to fix your mobile-friendly page error for Google Search Console. Thank you.

Ashok Kumar

Ashok Kumar working in the Search Engine Optimization field since 2015. And worked on many successful projects since then. He shares the real-life experience of best SEO practices with his followers on You also can learn Advance level SEO for WordPress, Blogger, or any other blogging platform. Stay tuned.

Related Articles

Leave a Reply

Back to top button