Mobile friendliness is how well your website works on a phone or tablet. Not just whether it loads, but whether a visitor can read the text, tap buttons without zooming, and navigate without frustration. Google ranks the mobile version of your site first. That has been the default since 2020. A poor mobile experience hurts your rankings for everyone, including desktop searchers.

Does mobile friendliness affect your search rankings?

Yes. Google and Bing both use mobile friendliness as a ranking signal when a user searches on a mobile device. But the bigger shift is mobile-first indexing. Google crawls and indexes your mobile site first, then uses that version to determine your rankings everywhere. If your mobile site is missing content, loads slowly, or breaks on small screens, your entire search presence suffers.

Google does not index your desktop site first anymore. It indexes your mobile site first.

Three ways to build a mobile-friendly site

There are three standard approaches to making a website work on mobile. Each has different tradeoffs:

  • Responsive design: one codebase, one URL, one site that adjusts to any screen size using CSS. This is Google's recommended approach and requires the least ongoing maintenance.
  • Dynamic serving: the server detects the visitor's device and sends different HTML depending on whether they are on mobile or desktop. Requires the Vary HTTP header to prevent caching errors.
  • Mobile subdomain: a completely separate site hosted at a URL like m.yourdomain.com. Requires the most developer time and introduces complexity around keeping both versions in sync.

Responsive design is Google's recommended approach. One site, one URL, no redirect logic.

What your site needs to pass a mobile check

These are the core signals that determine whether your site is genuinely mobile friendly:

  • Viewport meta tag: the single line of HTML that tells browsers how to scale your page. Without it, mobile browsers render your site at desktop width and shrink it down. Missing this tag is a critical failure.
  • Touch-friendly targets: buttons and links need to be large enough to tap accurately. Targets that are too small or too close together frustrate users and increase bounce rates.
  • Readable font sizes: base text should be at least 16 pixels on mobile. Anything smaller forces users to pinch and zoom.
  • Responsive images: images should scale to fit the screen. Use srcset or picture elements so browsers load the right image size for the device.
  • No obsolete plugins: Flash, Java, and Silverlight do not run on mobile browsers. Any content that depends on them is invisible to mobile users.
  • Simple navigation: drop-down menus rarely work well on touchscreens. Vertical layouts with a clearly marked menu button work better.
  • Mobile-optimised form inputs: use the correct input type for each field, email, tel, number, date. This triggers the right keyboard on mobile and speeds up form completion.

Page speed is not optional on mobile

Most mobile users will leave a page that takes more than three seconds to load. Google's standard is stricter: content above the fold should render in under one second. The metrics that matter are called Core Web Vitals. Google uses them directly as ranking signals.

  • LCP (Largest Contentful Paint): how long the main content takes to appear. Target: under 2.5 seconds.
  • INP (Interaction to Next Paint): how quickly the page responds after a tap or click. Target: under 200 milliseconds. This replaced First Input Delay as the standard in 2024.
  • CLS (Cumulative Layout Shift): how much the page jumps around while loading. Target: under 0.1. Layouts that shift as images load are a common mobile frustration.

INP replaced FID in March 2024. Tools still reporting FID are using an outdated standard.

What Stackra checks that most tools miss

Standard mobile checkers confirm the viewport tag exists and run a speed test. Stackra goes further across six areas:

  • Parallel mobile and desktop analysis: Stackra runs two separate PageSpeed Insights calls on every scan, one for mobile and one for desktop, so scores are never blended or estimated.
  • Current Core Web Vitals: Stackra reports LCP, INP, CLS, FCP, and TBT using the 2024 standards. INP is the correct interaction metric, not FID.
  • Visual AI assessment: Stackra uses GPT-5.4 to look at a rendered screenshot of your homepage and assess mobile presentation directly, catching layout issues that HTML parsing cannot detect.
  • Touch target analysis: Stackra evaluates every button and navigational link individually and checks that at least 60 percent of interactive elements meet size guidelines. It excludes inline body text links to avoid false positives.
  • Mobile form optimisation: Stackra checks input type attributes across every form, flagging fields that would show the wrong keyboard on mobile.
  • Business-type adaptive scoring: for businesses where mobile performance directly affects revenue, like e-commerce or SaaS, Stackra increases the mobile weighting in the Technical Pillar from 15 percent to 20 percent.

A missing viewport tag is not a warning in Stackra. It is a 15-point penalty to the UX score, treated as a critical failure.