Mobile-Friendly Checker

Mobile friendliness means text, tap targets, and layout work in a narrow viewport. A real test loads the page at a phone width. This screen shows a pass or fail layout without doing that load.

Mobile friendliness means text, tap targets, and layout work in a narrow viewport. A real test loads the page at a phone width. This screen shows a pass or fail layout and a short list of checks without doing that load.

Pass or fail is one of the values Mobile-Friendly Checker puts on screen. A summary of whether the page works on a phone. The sample chooses a label on the page. Do not ship a CSS change from that label.

Read Subchecks on its own before you mix it with the other rows. Real tests name text size, tap targets, and viewport. The list under the label is a sample. A passed row here was not measured.

Viewport answers a narrower question than the headline number. The viewport meta tag sets the layout width. This screen does not read that tag. View source for the viewport element.

Treat Tap targets as a label with a specific job. Buttons need space a thumb can hit. The sample cannot see your buttons. Try the page on a phone.

The Narrow layout line is worth a full stop. A phone is a narrow window. The tool does not resize a live document. Use the browser’s device mode for a real look.

Open the URL on a phone or in a narrow browser window when you need a real answer. A pass on this page does not mean buttons are tappable.

If you remember one sequence from Mobile-Friendly Checker, remember the fields in the order they change a decision. Pass or fail matters because A summary of whether the page works on a phone. In practice, The sample chooses a label on the page. The mistake to avoid is this: Do not ship a CSS change from that label. Subchecks matters because Real tests name text size, tap targets, and viewport. In practice, The list under the label is a sample. The mistake to avoid is this: A passed row here was not measured. Viewport matters because The viewport meta tag sets the layout width. In practice, This screen does not read that tag. The mistake to avoid is this: View source for the viewport element. Tap targets matters because Buttons need space a thumb can hit. In practice, The sample cannot see your buttons. The mistake to avoid is this: Try the page on a phone. Narrow layout matters because A phone is a narrow window. In practice, The tool does not resize a live document. The mistake to avoid is this: Use the browser’s device mode for a real look. After that, the checks are simple. You did not announce a pass from this page. You planned a narrow-window look. Tap targets will be tried with a finger. The viewport tag will be read in source. Sample subchecks stayed out of the ticket.

The worked example for Mobile-Friendly Checker, read as one scene, is this. Type https://example.com. You may see a pass and a few checks. example.com was not rendered at 360 pixels. Open the same URL in a narrow window. Scroll, tap, and read. That session replaces this label.

Final notes for Mobile-Friendly Checker, written as decisions rather than as a table. When Pass or fail is in front of you, decide using this: A summary of whether the page works on a phone. Do not ship a CSS change from that label. When Subchecks is in front of you, decide using this: Real tests name text size, tap targets, and viewport. A passed row here was not measured. When Viewport is in front of you, decide using this: The viewport meta tag sets the layout width. View source for the viewport element. When Tap targets is in front of you, decide using this: Buttons need space a thumb can hit. Try the page on a phone. When Narrow layout is in front of you, decide using this: A phone is a narrow window. Use the browser’s device mode for a real look. Then apply the checks without skipping one. You did not announce a pass from this page. You planned a narrow-window look. Tap targets will be tried with a finger. The viewport tag will be read in source. Sample subchecks stayed out of the ticket.

Keep Mobile-Friendly Checker as this step only. When the job moves on, the Page Speed Test UI is the next page: Page Speed Test UI shows a performance score and lab-style metrics for a URL you type. The Page Size Checker covers a different piece of the same work: Page Size Checker asks for a URL and then shows a total kilobyte figure plus a split across HTML, images, scripts, and CSS.