Mobile-friendly is the floor, not a goal

Google's index is mobile-first. The mobile version of your page is what gets crawled, evaluated, and ranked. Pages that fail mobile usability checks are demoted across the board, not just on mobile searches. Passing mobile-friendly tests is no longer optional; it is the cost of being indexed.

This tester checks the three things Google's algorithm grades: viewport configuration, touch target sizing, and font readability. Each is a yes-or-no signal that Google watches across every URL.

The viewport meta tag

Without <meta name="viewport" content="width=device-width, initial-scale=1">, mobile browsers render your page as if it were 980 pixels wide and zoom out to fit the screen. Text becomes unreadably small. Layouts break. Google flags the page as not mobile-friendly within hours.

The viewport tag must be in the head and appear before any other content-affecting tags. Setting initial-scale to anything other than 1 (especially scale=0.5 or fixed scales) is also flagged. Using user-scalable=no breaks accessibility (users cannot zoom in for readability) and is no longer supported in iOS Safari.

Touch targets and their 48px rule

Touch targets (buttons, links, form controls) need to be at least 48 by 48 CSS pixels. Smaller targets are hard to tap accurately on phones, especially for users with mobility challenges. Targets too close together (under 8 pixels apart) cause mistaps.

Common offenders: navigation menus with tiny tap zones, dense link clusters in footers, social media icons crammed side-by-side. Even if the visible icon is small, you can pad the click area with CSS so the touch target meets the minimum even if the visual stays compact.

Font sizes for mobile readability

Body text under 16 pixels triggers Google's small-text warning and forces mobile users to pinch-zoom. The minimum body size in 2026 should be 16 pixels (approximately 1rem with default browser settings). Larger sites use 18 pixels for better readability.

Be careful with em or rem units when the user has changed browser default font size. Pages that look fine at default settings can fail mobile-friendly tests when a user has bumped their default to 20 pixels for accessibility.

Common mobile-friendly failures

Horizontal scrolling caused by fixed-width elements. Tables with fixed pixel widths, images with hardcoded width attributes, and pre-formatted code blocks without overflow handling are the usual suspects. Wrap them in containers with overflow-x: auto or use responsive table patterns.

Tap-blocking interstitials. Cookie banners, newsletter popups, and app-install prompts that cover the top portion of the page are penalized as intrusive interstitials. They affect rankings directly. Use bottom-anchored banners or smaller, dismissable bars.

Flash content. Google deprecated Flash years ago and modern browsers no longer support it. If anything in your stack still outputs Flash (extremely rare in 2026 but it happens with legacy CMSs), it fails mobile-friendly entirely.

Beyond mobile-friendly

Passing the mobile-friendly test is the bare minimum. Google's page experience signals layer in Core Web Vitals (LCP, INP, CLS), HTTPS, no intrusive interstitials, and several others. A site can pass mobile-friendly while still losing to faster, smoother competitors.

Run this test alongside Core Web Vitals checks for a fuller picture. The mobile-friendly test confirms the basics; CWV confirms the experience is competitive. Both must pass for sustainable mobile ranking.