Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Optimize your website for mobile: test, fix and retest

Updated · 7 min read

Short answer Test on two real phones first, one iPhone and one Android, on mobile data: read, scroll, tap the phone number, the menu and the form. Then run the free tools: PageSpeed Insights on Mobile, Chrome's device mode and Search Console's URL Inspection. Fix what failed, retest the lab score the same day, and recheck real-visitor data after 28 days.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

How to test your website on mobile: the 20-minute routine

Run it on your home page and every page that brings calls or bookings. Do it monthly, and after any theme change, new plugin or redesign.

StepToolCostIt fails when
1. Thumb testYour own iPhone and an Android, on mobile dataFreeYou zoom, swipe sideways, or tap twice to hit something
2. Speed and layout scanPageSpeed Insights, Mobile tabFreeCore Web Vitals fail, or the report flags the viewport or touch targets
3. Narrow-screen checkChrome's device mode on a computerFreeText or buttons spill off a 320-pixel-wide screen
4. Google's viewSearch Console, URL Inspection, live testFreeText you see on the phone is missing from the rendered page

Real phones come first. Chrome's own documentation says device mode is only "a first-order approximation", and:

"When in doubt, your best bet is to actually run your page on a mobile device." (Chrome for Developers: Simulate mobile devices with device mode)

The phone version also decides your search ranking. Google says it "uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking" (Google Search Central: Mobile-first indexing best practices). Since July 5, 2024, it crawls every site for Search with its smartphone crawler (Google Search Central Blog, June 2024).

Test on real phones: what to tap

Borrow a second phone if you need to, so you have one iPhone and one Android. Turn off Wi-Fi: customers in a driveway or a parking lot are on mobile data.

  1. Read without zooming. If you pinch to read prices or hours, the text is too small or the page is zoomed out.
  2. Scroll to the bottom. The page should only move up and down. A sideways wobble means something is wider than the screen.
  3. Tap the phone number. It should open the dialer. web.dev advises wrapping every number in a `tel:` link rather than trusting the phone to spot it (web.dev: Click to call). A number inside a photo can't be tapped at all.
  4. Open the menu and every link in it. Each tap should land the first time, without hitting the next link.
  5. Fill in the form. The phone field should open a number pad. web.dev says the right field type gives "the right keyboard on mobile" (web.dev: Sign-up form best practices). Submit it and check the message arrives.
  6. Turn the phone sideways. Nothing should be cut off or hidden behind a fixed header.
  7. Make the text bigger. On iPhone, go to Settings, Accessibility, Display & Text Size, Larger Text (Apple Support). Reload. The accessibility standard WCAG asks that text can grow to 200% "without loss of content or functionality" (W3C: Resize Text).
  8. Watch the first five seconds. Note any pop-up that covers the page. Google warns these "may lead to poor search performance" and suggests "banners that take up only a small fraction of the screen" instead (Google Search Central: Avoid intrusive interstitials).

Write down each failure with the page and the phone. That list is your fix list.

Free tools that catch what your thumb misses

ToolWhat it showsLimit
PageSpeed InsightsLab test of one load on a simulated "mid-tier device (Moto G4)" on a mobile network, plus real Chrome users over the past 28 daysSmall sites often have too little real-user data, so only the lab part shows (PageSpeed Insights)
Lighthouse in ChromeThe same lab audits, run from Chrome's DevTools in 30 to 60 seconds; works on pages behind a login (Lighthouse overview)One load on your computer, not your customers' phones
Chrome device modeYour page at phone widths; the "Mid-tier mobile" setting simulates fast 3G and a CPU 4 times slower (Device mode)Simulation only
Search Console URL InspectionA live test of how Google loads the page (Get started with Search Console)Needs a verified Search Console account
Safari Web Inspector, Chrome remote debuggingThe code running on a real iPhone or Android, viewed from a computer over a cable (Apple Developer; Chrome for Developers)For whoever fixes the site, not for a quick check

In PageSpeed Insights, two lines map straight to mobile problems. "Optimize viewport for mobile" means the page lacks the tag that fits it to the screen (Chrome for Developers: Lighthouse viewport audit). "Touch targets do not have sufficient size or spacing" means buttons are too small or too close (Lighthouse source). WCAG's minimum for a tap target is "at least 24 by 24 CSS pixels" (W3C: Target Size Minimum).

In device mode, pick the 320-pixel "Mobile S" width. WCAG's reflow rule asks that pages work at 320 CSS pixels wide without scrolling both ways (W3C: Reflow).

In URL Inspection, Google says to check that your content "is visible on the rendered page", which is "how Google sees your page" (Google Search Central: Mobile-first indexing best practices). The tool for this is covered in Google Search Console for a small business.

Fix what failed

Most failures trace back to a handful of causes. Hand this table to whoever edits your site.

What you sawLikely causeFix
Page loads zoomed out, tiny textNo viewport tagAdd `width=device-width, initial-scale=1` in the page head (Lighthouse viewport audit)
Sideways scrollingA wide image, table or embedded mapMake it shrink to the screen, or let only that element scroll
Wrong link tappedButtons too small or touchingAt least 24 by 24 pixels with space around (W3C); bigger for the call button
Phone number won't dialPlain text or an imageA `tel:` link (web.dev)
Text you see on desktop missing on the phone, or from Google's rendered pageMobile theme hides it, or it loads only after a tapRestore it; accordions and tabs are fine if the content is equivalent. Google won't load "content that requires user interactions" (Mobile-first indexing best practices)
Slow lab scoreHuge photos, too many plugins or chat widgetsSmaller images, fewer scripts; details in Core Web Vitals and website speed
Larger text breaks the layoutFixed-height boxesLet boxes grow with the text; see ADA website compliance
Full-screen pop-up on arrivalOffer or newsletter windowA small banner (Avoid intrusive interstitials)

Retest: when the fix shows up

Each check refreshes on its own clock.

  • Phone test and lab score: same day. Rerun steps 1 to 3 after each fix. Clear the phone's cache or use a private tab so you don't see the old version.
  • Google's view: after a recrawl. Run the URL Inspection live test again. The tool also lets you "ask Google to crawl a specific page" (Get started with Search Console).
  • Real-visitor speed: about 28 days. PageSpeed Insights' real-user data covers the previous 28 days (PageSpeed Insights), so a fix shows fully only after old visits roll off.

Don't chase 100. Google says good scores don't "guarantee that your pages will rank at the top", and that relevance comes first (Google Search Central: Understanding page experience). Stop when your thumb test passes and Core Web Vitals are green.

Example

Illustrative cases with invented round numbers.

A plumber whose number didn't dial (US dollars)

On the owner's iPhone, tapping the header number did nothing: it was part of the logo image. The web designer added a `tel:` link in 15 minutes. One $400 drain call a month covers it many times over.

A Vancouver hair salon that broke at large text (Canadian dollars)

With iPhone text set to large, the "Book" button slid under the price list and couldn't be tapped. The fix let the price boxes grow. The salon retested at large text on both phones. One C$90 booking a week was at stake.

A landscaper with a hidden service list

PageSpeed Insights was green, but URL Inspection's rendered page showed only a photo and "Contact": the mobile theme dropped the services. They went back in a collapsible section, and the next live test showed them.

FAQ

Is there still a Google mobile-friendly test?

No. Google retired the Mobile-Friendly Test and Search Console's Mobile Usability report on December 1, 2023 (Google Search Central Blog, April 2023). Lighthouse, inside PageSpeed Insights or Chrome, is the closest free check.

Can I test without owning both kinds of phone?

Partly. Chrome's device mode shows phone layouts, and a Mac can run iPhone simulators (Apple Developer). Neither shows real speed, so test on one real phone.

Do I need AMP pages to load fast on phones?

No. Google says it "indexes AMP pages just like other web pages" (Google Search Central: About AMP). A normal responsive page that passes Core Web Vitals does the job.

How often should I retest?

Monthly, and after every theme update, plugin install or redesign. Those are the changes that quietly break mobile layouts.

Different for you?

Keep learning

NextSearch Console for mobile SEO: what you can still checkSearch Console lost its mobile usability tools in 2023. The four places it still shows mobile data, how to read them, and what to test elsewhere.

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: Mobile site and mobile-first indexing best practices
  2. Google Search Central Blog: Mobile-indexing-vLast-final-final.doc (June 2024)
  3. Google Search Central Blog: The role of page experience in creating helpful content (April 2023)
  4. Google Search Central: Understanding page experience in Google Search results
  5. Google Search Central: Avoid intrusive interstitials and dialogs
  6. Google Search Central: Get started with Search Console
  7. Google Search Central: About AMP on Google Search
  8. PageSpeed Insights: About PageSpeed Insights
  9. Chrome for Developers: Simulate mobile devices with device mode
  10. Chrome for Developers: Lighthouse overview
  11. Chrome for Developers: Lighthouse viewport audit
  12. Lighthouse source: target-size audit
  13. Chrome for Developers: Remote debug Android devices
  14. Apple Developer: Inspecting iOS and iPadOS
  15. Apple Support: Change the font size on your iPhone, iPad and iPod touch
  16. W3C: Understanding WCAG 2.2 Success Criterion 1.4.4 Resize Text
  17. W3C: Understanding WCAG 2.2 Success Criterion 1.4.10 Reflow
  18. W3C: Understanding WCAG 2.2 Success Criterion 2.5.8 Target Size (Minimum)
  19. web.dev: Click to call
  20. web.dev: Sign-up form best practices