Mobile-Friendly test

Having a mobile-friendly website is a critical part of your online presence. In many countries, smartphone traffic now exceeds desktop traffic. If you haven't made your website mobile-friendly, you should. Search Console's Mobile-Friendly test is a quick, easy way to test whether a page on your site is mobile-friendly.

Open the Mobile-Friendly Test



The Mobile-Friendly test is easy to use: simply type in the full URL of the web page that you want to test. The test typically takes less than a minute to run.

Test results include a screenshot of how the page looks to Google on a mobile device, as well as a list of any mobile usability problems that it finds. Mobile usability problems are issues that can affect the page when visited on a mobile device, including small font sizes (which are hard to read on a small screen) and use of Flash (which isn't supported by most mobile devices).

You don't need to have a Search Console account to use this tool, or be logged in to your Search Console account, if you have one.

Run the test

Use this tool as part of a check-and-fix cycle for mobile usability issues. Do not use this tool to see whether your page is considered mobile-friendly in the Google index (see below).

To run the test:

  1. If you are trying to fix mobile usability issues for a page pointed to by Google Search (that is, the indexed page), confirm that you're testing the canonical URL. Fixing a non-canonical URL will help users who reach the page via direct links, but won't fix the page pointed to by Google.
  2. Type the URL to test in the text box and click Test URL.
  3. Google will fetch the requested URL as if it were a mobile device. The tool follows any redirects that the page implements without modifying the URL that you typed in. If your website sends mobile devices to a different URL, or if the page is a linked AMP page, the test will fetch that URL instead of the one you requested, but won't indicate that it is testing another URL, or show the actual URL fetched for the test.
  4. The test result shows the mobile-friendly status of the page. Be sure that you understand what your status means: status descriptions are listed below.
  5. If you have availability issues (that is, Google can't find or reach the URL, or the URL is blocked to Google), then fix those issues first.
  6. If the page has unloadable resources (such as images or stylesheets), then you will see a warning. Fix those next and retest, as they might be the cause of other issues on your page.
  7. If your page is reported as not mobile-friendly, fix all issues except Text too small to read first, and rerun the test.
  8. Once all other issues are resolved, then fix Text too small to read (if present) and confirm by rerunning the test. See the list of possible issues below.
  9. When fixing issues, it can be useful to see a screenshot of the page as Google sees it. To see a screenshot, click View tested page. The screenshot will show the size and resolution used by Google for testing mobile usability. If you need to see more than one screenful, you can use Chrome to simulate a mobile testing environment, or else open the page on a mobile device with a size similar to the screenshot.

This test doesn't necessarily show your mobile-friendly status in the Google index

The Mobile-Friendly test tool tests only the version of the URL that you provide.

If you test the non-canonical page using the Mobile-Friendly test tool, this doesn't reflect the mobile friendly status of the page in the Google index. During indexing, Google tests the mobile-friendliness only of the canonical URL from a set of duplicate pages. If the canonical version has mobile-friendly issues, then the page is considered to have mobile-friendly issues by Google, whether or not the duplicate versions are free of mobile-friendly issues.

If a URL has already been indexed, you can see its canonical URL using the URL Inspection tool (under Page availability > Google-selected canonical).

To determine whether you're testing the canonical URL:

  • Use the URL Inspection tool on the URL to inspect the indexed version (not the live test). Check the value shown in Coverage > Indexing > Google-selected canonical: the value "Inspected URL" means that the URL tested is canonical; if another URL is shown, the URL shown is the one that will appear search results.
  • To see site-wide mobile friendly statistics, use the Mobile Usability report.

Test results

About the results
The results shown here match the testing criteria used by Google Search. Other tests or tools might show additional meaningful mobile-usability issues, or might not report an issue reported by the Mobile-friendly test, but the issues reported by the Mobile-friendly test accurately reflect the test criteria used by Google Search. Just be sure that you are testing the right URL.
If the page can't be reached
This tool accesses the page as Googlebot (that is, not using your credentials, but as Google). This means that it can be blocked by a robots.txt file.

If for some reason the tool cannot access the page, it will display one of the following errors:

  • DNS server unresponsive: Often this is a transient problem that resolves itself in a few minutes.
  • DNS error: Host unknown: Your DNS server did not resolve your URL. This might be a transient problem that resolves itself in a few minutes.
  • DNS error: Private IP provided: Your DNS returned an IP that is in a special/private excluded range, such as RFC 1918 private IP (for example,
  • Server connection error: Server was unreachable, refused connection or failed to connect. Read more.
  • Server invalid response: Server does not support requested protocol the response or headers were truncated; or the response could not be parsed (for example, if the response data was incorrectly compressed). Read more.
  • Invalid server SSL certificate: Your site's SSL certificate is invalid. Google won't test an HTTPS URL on the site unless the certificate is valid.
  • Robots.txt unreachable: Google won't crawl a website if the robots.txt file is present but not reachable. You can check your robots.txt availability in the Crawl Stats report.
  • Hostload exceeded: Your site seems to be at maximum capacity for Google crawling or inspection requests. Google can't run tests until your traffic load (as estimated by Google) drops.
If the page has unloadable resources

If a test cannot load all the resources used by a page, you will see a warning. Resources are external elements included in the page, such as images, CSS, or script files. This test tries to load only certain types of resources; others that won't affect the test are ignored.

Loading issues can happen for several reasons:

  • The resource couldn't be loaded in a reasonable amount of time. In this case, try running the test again. If it continues to happen, consider hosting the resource somewhere else, or else try to discover and fix the reason for slowness or lack of response from the host.
  • The resource does not exist in the location listed (404 error). Verify and fix the resource's URL on your page.
  • The resource is inaccessible to non-logged-in users. The test accesses the page as an anonymous user; ensure that all resources are accessible to anonymous users.
  • The resource is blocked to Googlebot by a robots.txt file. If the resource is important (see below) and it is on your own site, you might want to unblock the resource to Googlebot. If the resource is on another site, you might want to contact the site's webmaster and ask to have it unblocked.

Unblocking important resources

If a blocked resource is important, it could have a big effect on how Google understands the page. For example, a blocked large image could make a page appear to be mobile-friendly when it is not, or a blocked CSS file could result in incorrect font styles being applied (for example, too small for a device). This affects Google's ability to crawl your page, which could affect your results on Google. You should make sure that important resources are not blocked to Googlebot by robots.txt and are generally accessible.

Inconsistent test results/Page loading issues

If you have unloadable resources or other page loading issues, you might see slightly different results every time you run the test. This is because the set of resources that were loaded can vary during each test run. If your page rendering changes each time you run the test, and you have not changed anything, check for a "page loading issues" warning; if present, click for more information to see what might have happened to prevent the page from being rendered consistently and correctly.

Mobile-friendly status

The following test results are possible:

  • Page isn't usable on mobile: The page won't work well on a mobile device because of one or more issues that exceed a quality bar. Google marks a page as mobile-friendly or not mobile-friendly according to the number of issues that affect a page and their relative severity. A page can have one or two (unreported) minor issues and still be considered mobile-friendly. See descriptions of the possible errors.
  • URL is not available to Google: The URL is blocked to Google crawling, which means that Google will not be able to crawl and index the page. The page cannot be tested for mobile friendliness until it is available to Google. Read the crawl details section to understand the issue. (Examine the Crawl allowed? value in the Details > Crawl section.)
  • No significant availability issues iconPage is usable on mobile: The page should work well on a mobile device. Note that a page marked as mobile friendly might still have minor issues, which will not be shown in the report. More details.
  • No data available: For some reason we couldn't retrieve the page or test its mobile-friendliness. Please wait a bit and try again.

If a URL has more than a threshold level of errors, it will have a status of Page isn't usable on mobile and all errors will be shown. If a URL has less than a threshold of errors, then the status will be Page is usable on mobile and no errors will be shown.

The weight and severity of the different error types is not explicitly defined. Therefore, a page that is marked as mobile-friendly might in fact have a few unreported errors, and could be relabeled as non-mobile-friendly with the addition of one more error. Don't worry about unreported mobile-usability errors on a page.

Mobile-friendly errors

The Mobile-Friendly Test tool can report the following usability errors:

List of errors

Uses incompatible plugins

The page includes plugins, such as Flash, that are not supported by most mobile browsers.

To fix: We recommend redesigning your page using modern, broadly-supported web technologies, such as HTML5. Read more about web animation guidelines.

Viewport not set

The page does not define a viewport property, which tells browsers how to adjust the page’s dimension and scaling to suit the screen size.

To fix: Because visitors to your site use a variety of devices with varying screen sizes—from large desktop monitors, to tablets and small smartphones—your pages should specify a viewport using the meta viewport tag. Learn more in Responsive Web Design Basics.

Viewport not set to "device-width"

The page defines a fixed-width viewport property, which means that it can't adjust for different screen sizes.

To fix: Adopt a responsive design for your site’s pages, and set the viewport to match the device’s width and scale accordingly. Read how to correctly Set the Viewport.

Content wider than screen

Horizontal scrolling is necessary to see words and images on the page. This happens when pages use absolute values in CSS declarations, or use images designed to look best at a specific browser width (such as 980px).

To fix: Make sure that the page uses relative width and position values for CSS elements, and make sure images can scale as well. Read more in Size Content to Viewport.

Text too small to read

A significant portion of the text on the page is too small relative to the width of the page. This makes the text hard to read on a mobile device. Look at the test screenshot for your device to try to identify the problematic text.

To fix: Specify a viewport for your web pages and set all your font sizes to scale properly within the viewport, so the text will be visible on a device screen. Read more about best practices for font size.

Clickable elements too close together

Touch elements, such as buttons and navigational links, are so close to each other that a mobile user cannot easily tap a desired element with their finger without also tapping a neighboring element.

To fix: Look at the test screenshot and identify all the buttons, links, and other touch targets. Make sure that your touch targets are not closer together than an average fingertip width, or that your fingertip can't span multiple link targets. Read more in Accessible Tap Targets.

Additional information

You can see a screenshot of the rendered page, as well as the rendered HTML for the test page, any JavaScript errors encountered, and more by clicking View tested page after running a test, provided the page can be retrieved.

Next steps

What is a rendered page?
When you visit a web page, your browser requests the page HTML, which typically includes linked resources such as embedded images and/or videos, style sheets, and scripts. The browser then requests these linked or embedded resources and runs any scripts on the page. These scripts and embedded images affect the layout and content of the page. For example, a script might reformat the page depending on whether the user is visiting from a laptop or a mobile device. Once the browser has finished loading all these resources and running any setup scripts, the page is "fully rendered" for the user. You might see this happening in real time on your own device, when images or other page elements appear and move around while the page is being loaded. Google tests the mobile usability of a page only after it's been rendered.
Was this helpful?
How can we improve it?
New to Search Console?

Never used Search Console before? Start here, whether you're a complete beginner, an SEO expert, or a website developer.

Clear search
Close search
Google apps
Main menu
Search Help Center