MOBILE FRIENDLY TEST

How to Use This Tool

The Mobile-Friendly Test is not at all difficult to use; basically type in the full URL of the site page you need to test. Each sidetrack the page runs will be followed by testing. The test usually takes a short time to run.

The test results included screenshots of how the page was displayed on Google on the phone, along with other issues it found. Mobile preview issues can affect clients visiting pages on portable gadgets (small screens), including small text dimensions (which are difficult to read on small screens) and Flash usage (which most phones don't support).

When the web page cannot be reached

If the Mobile Friendly Test tool can't open the page, it will show an error describing the problem. Access issues include system availability issues or site downtime.

This Mobile Friendly test tool opens the page as Googlebot (that is, not using your qualifications, but as Google). This implies that it is likely to be blocked by the robots.txt document.

When the page contains unmountable elements

If the test can't stack all the elements used by the page, you'll get a notification. Resources are external components included by a page, for example, images, CSS, or script files. This can happen for several reasons:

• The element cannot be loaded in a reasonable size of time. For this situation, try running the test again. If that continues, consider facilitating the element elsewhere, or, in all likelihood, try to find and correct the explanation behind the no-response from the host.
• The element does not exist in the recorded area (404 error). Fix the URL.
• This element is not available to clients who are not logged in. Test logged on to the page as anonymous client; make sure that all resources are open to external clients.
• The element is set to block Googlebot with a robots.txt file. If the resource is important and it is on your own web page, you should free Googlebot; if it's on another website, you have to contact the admin of the web page and ask to unblock it.

Unblocks significant resources

If the assets being blocked are very significant, they can greatly affect how Google understands the page. For example, a large blocked image can cause a page to appear mobile-friendly when it is not. Or a blocked CSS document can cause misunderstanding of the text styles to be applied (for example, the size is too small for the gadget). This affects Google's mobile-friendly score and capacity to crawl your pages. You must ensure that critical elements are not blocked by Googlebot by robots.txt and are available.

Unstable test results / Page loading issues

If you have an unloaded element or other pileup issue, you may see slightly different results each time you run the test. That's because the stacked resource settings can be different during each test. If you see your page making changes every time you run the test, and you haven't changed anything, check the "page loading issues" note; if applicable, click for more information to find out what might happen to prevent the page from being delivered reliably and effectively.

Mobile Usability Error

The Mobile Friendly Testing Tool can distinguish the following errors:

1. Using incompatible plugins

If your page uses a plugin, for example, Flash, which is not supported by portable devices, we recommend overhauling your page to start using modern, widely supported web technologies, for example, HTML5.

2. Viewport not adjusted

The page doesn't characterize the viewport property, which tells the browser how to change the sizing and scaling of the page to fit the screen size. Since visitors to your site use a variety of gadgets with different screen sizes - from large workspace screens, to small tablets and phones - your page must define the viewport with the meta viewport tag.

3. Content wider than screen

Horizontal scrolling is important for seeing words and images on the page. This occurs when the page uses absolute values ​​in CSS, or uses an image that is meant to view a specific browser width, (for example, 980px). To fix this error, make sure the page uses relative width and position values ​​for the CSS component, and make sure that the image is scalable as well.

4. Text too small to read

This is an error that occurs when the text font size for the page is too small and will require the user to "squeeze to zoom" to read. After setting the viewport for your page, set the font size for your text to an appropriate scale within the viewport.

5. Clickable elements are too close together

Linkable components, for example, buttons and link text with links, are so close that it takes a significant amount of effort for mobile clients to tap the ideal component with their finger without tapping adjacent components. To fix this error, make sure to estimate accurately and the spacing and link buttons to be suitable for your mobile users.