Test Result

Tested on 04/08/2020 22.50

Page is mobile friendly

This page is easy to use on a mobile device

Page Screenshot

mobile preview small

Mobile Friendly Test Tool

Having a mobile friendly site is a basic piece of your online brand awareness. In numerous nations, cell phone traffic currently surpasses desktop traffic. On the off chance that you haven't made your site portable well disposed, you should. Mobile-Friendly Test Tool by CMLABS is a brisk, simple approach to test whether a page on your site is mobile-friendly.

How to Use the Tool

The Mobile-Friendly test is anything but difficult to utilize; essentially type in the full URL of the site page that you need to test. Any sidetracks executed by the page will be trailed by the test. The test ordinarily takes a short moment to run.

Test outcomes incorporate a screen capture of how the page shows on Google on a cell phone, along with other issues that it finds. Mobile preview issues can influence a client that visits the page on a portable (small screen) gadget, including little text dimensions (which are difficult to read on a little screen) and utilization of Flash (which isn't upheld by most cell phones).

When the web page can't be reached

On the occasion where the Mobile Friendly Test tool can't get to the page, it will show a mistake portraying the issue. Access issues include system availability issues or the site being down.

This Mobile Friendly test tool gets to the page as Googlebot (that is, not utilizing your qualifications, however as Google). This implies it tends to be blocked by a robots.txt document.

When the page contains unloadable elements

In the occasion where a test can't stack all elements utilized by a page, you will get an notification. Resources are outer components included by the page, for example, pictures, CSS, or script files. This can occur due to a few reasons:

  • The element wasn't loadable in a sensible measure of time. For this situation, retry running the test once more. In the event that it keeps on occurring, consider facilitating the elements elsewhere, or, in all likelihood attempt to find and fix the explanation behind absence of response from the host.
  • The element doesn't exist in the area recorded (404 error). Fix the URL.
  • The element is unavailable to non-signed in clients. The test gets to the page as an anonymous client; make sure that all resources are open to external clients.
  • The element is set to block Googlebot by a robots.txt file. On the occasion where the resource is significant, and it is on your own webpage, you should unblock Googlebot; in the event that it is on another website, you should contact the webpage's admin and request to have it unblocked.

Unblocking significant resources

On the occasion where the blocked asset is very significant, it could highly affect how Google comprehends the page. For instance, a blocked enormous picture could cause a page to seem mobile friendly, when in fact, it isn't. Or a blocked CSS document could bring the misunderstanding about the text style being applied (for instance, the size is too small for a gadget). This influences both the mobile friendly score and Google's capacity to crawl your page. You should ensure that significant elements are not hindered to Googlebot by robots.txt and are available.

Flaky test results/Page loading issues

If you have unloadable elements or other page stacking issues, you may see marginally various outcomes each time you run the test. It happens because the arrangement of resources that were stacked can differ during each test. If you see your page delivering changes each time you run the test, and you have not transformed anything, check for a "page loading issues" note; if present, click for more information to perceive what may have happened to keep the page from being delivered reliably and effectively.

Mobile-usability errors

The Mobile-Friendly Test tool can distinguish the following errors:

Uses incompatible plugins

If your page utilizes plugins, for example, Flash, that are not upheld by most portable deviced, we suggest overhauling your page to start using modern, broadly-supported web technologies, for example, HTML5.

Viewport not set

The page doesn't characterize a viewport property, which advises browsers how to alter the page's measurement and scaling to suit the screen size. Since guests to your site utilize an various gadgets with differing screen sizes—from huge work area screens, to tablets and small cell phones—your pages ought to determine a viewport with the meta viewport tag.

Viewport not set to "device-width"

If the page sets a fixed-width viewport property, which implies that it can't modify for various screen sizes. To fix this mistake, receive a responsive plan for your site's pages, and set the viewport to suit the gadget's width and scale.

Content wider than screen

Horizontal scrolling is important to see words and pictures on the page. This happens when pages utilize absolute values in CSS, or use pictures intended to take a gander at a particular browser width, (for example, 980px). To fix this mistake, ensure the pages utilize relative width and position values for CSS components, and ensure pictures can scale too.

Text too small to read

It is the error that happens when the text font size for the page is too small and would require users to "squeeze to zoom" in order to read. After setting a viewport for your pages, set your text font size to scale appropriately inside the viewport.

Clickable elements too close together

Linkable components, for example, buttons and anchor text with links, are so near that a mobile client need significant effort to tap an ideal component with their finger without tapping a neighboring component. To fix these mistakes, make a point to accurately estimate and space buttons and links to make it appropriate for your mobile users.