Mobile Friendly Test

Mobile Friendly Test

Is your web page mobile-friendly?

Mobile Friendly Test tool is a quick and easy way to test whether a page on your site is mobile-friendly or not based on Googlebot User-agent

Insert Url to test

Include protocol type (http or https)

Mobile friendly Test Tool

Test how easily a visitor can use your page on a mobile device

The web is being accessed more and more on mobile devices. In many countries, smartphone traffic now exceeds desktop traffic and smatphones has surpassed personal computers.

Today, everyone has smartphones with them, constantly communicating and looking for information.

Designing your websites to be mobile friendly ensures that your pages perform well on all devices.

If not mobile-friendly, a site can be difficult to view and use on a mobile device. A non-mobile-friendly site requires users to pinch or zoom in order to read the content. Users find this a frustrating experience and are likely to abandon the site. Alternatively, the mobile-friendly version is readable and immediately usable.

The following table gives you a detailed explanation and example of each of the test-result parameters.

Test status unspecified

Internal error when running this test.

Internal error

Inspection terminated in an error state. This indicates a problem in Google's infrastructure, not a user error.

Page unreachable

Google cannot access the URL because of a user error such as a robots.txt blockage, a 403 or 500 code etc. Make sure that the URL provided is accessible by Googlebot and is not password protected.

Complete

Inspection has completed without errors. The tool provide the Mobile Friendly Test result based on Googlebot User-agent for smartphone:

  • Mobile friendly: tha page is mobile friendly and the tool display the screenshot image
  • Not Mobile friendly: the page is not mobile friendly
  • Mobile friendly test result unspecified: Internal error when running this test

There are three main techniques for implementing a website that can handle view screens of all types and sizes.

Here is a chart comparing the three methods:

Configuration Same URL Same HTML code
Responsive Web Design
Dynamic Serving
Separate URLs

Responsive Web Design:
Serves the same HTML code on the same URL regardless of the users' device (for example, desktop, tablet, mobile, non-visual browser), but can render the display differently based on the screen size. Responsive design is Google's recommended design pattern.

Dynamic Serving:
Uses the same URL regardless of device, but serve a different version of HTML for different device types based on what the server knows about the user's browser.

Separate URLs:
Serves different code to each device, and on separate URLs. This configuration tries to detect the users' device, then redirects to the appropriate page using HTTP redirects along with the Vary HTTP header.

Mobile-first indexing

What this means for your site?

Mobile-first indexing means Google predominantly uses the mobile version of the content for indexing and ranking site.

Starting July 1, 2019, mobile-first indexing is enabled by default for all new websites.

Historically, the index primarily used the desktop version of a page's content when evaluating the relevance of a page to a user's query.

Since the majority of users now access Google Search with a mobile device, Googlebot primarily crawls and indexes pages with the smartphone agent going forward.

Here is what this means for your site:

Site type Best practices
Desktop only: your site doesn't have a mobile-friendly version, it's desktop only No change. The mobile version is the same as the desktop version.
Responsive web design: your site adjusts for screen size No change. The mobile version is the same as the desktop version.
Canonical AMP: all your web pages are created in AMP HTML. No change. The mobile version is the same as the desktop version.
Separate URLs: each desktop URL has an equivalent different URL that serves mobile-optimized content. Google prefers the mobile URL for indexing.
Dynamic serving: your site serves different content based on the user's device. Users only see one URL. Google prefers the mobile optimized content for indexing.
AMP and non-AMP: your site has both AMP and non-AMP versions of a page. Google prefers the mobile version of the non-AMP URL for indexing.

Share this tool

Did u like it? Share it!

Related tools

Try these one!
Validate your AMP pages

AMP VALIDATOR

Validate your AMP pages with this tool.

Test your Accelerated Mobile Pages, get detailed report and optimize performance.

GO VALIDATE
Network requests and timeline waterfall

NETWORK WATERFALL

Capture web page requests and timeline waterfall.

Quickly capture and analyze web page network requests during page load.

GO ANALYZE
Test your page structured data

STRUCTURED DATA TEST

Test your web pages structured data.

Check conformity of your structured data json-ld and improve your SEO.

GO TESTING
Test your page speed insights

PAGESPEED INSIGHTS

Analyze your web page speed performance.

Retrieve information about speed index, latency, first contentful paint and more.

GO ANALYZE