Mobile CRO: how to turn phone visitors into leads

What is CRO for mobile?

It is conversion rate optimization done for phone visitors: making the path from landing to enquiry work on a small screen, a slower connection and a thumb. The checks are the same as on desktop, but the bar is higher, because a phone visitor has less room, less patience for typing and often a slower connection.

Google treats phones separately too. Its mobile-first indexing documentation says “Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking”, and web.dev measures Core Web Vitals at “the 75th percentile of page loads, segmented across mobile and desktop devices”.

Why do phones convert differently?

Because almost everything is harder. Lighthouse, the test behind PageSpeed Insights, models a phone visit on a slow 4G connection, 150 milliseconds of latency and 1.6 megabits per second, with the processor slowed four times, while desktop is tested on a wired connection. Our own home page shows the gap: on 20 October 2026 it scored 97 to 100 on desktop and 70 to 90 on mobile in the same test, minutes apart, as our page speed guide explains.

The screen changes what fits: one column, so the first screen has to carry the offer and the next step. And typing on a phone is slow. Meta warns, for its own lead forms, that requiring people to type in multiple pieces of information “may prevent them from submitting the form”. Its default form type is built so people can quickly submit it “on a mobile device”, and its Higher intent form runs only in the mobile feeds.

What should you check on a phone? Nine mobile CRO checks

Start with check 1: open your page on a real phone, not a resized desktop window, and see what fits before the first scroll. Our guides to what makes a good landing page and how to write a call to action cover the rest of the page in detail.

How do you make a website mobile-friendly?

Good mobile web page design starts with the basics that let a page fit a phone at all, then the ones that make it easy to use:

1. Add the viewport tag. MDN recommends a viewport meta tag set to width=device-width, which “sets the viewport to match the device's width”.
2. Use a layout that reflows into one column. WCAG 2.2's reflow rule asks that content works without scrolling in two directions at a width equivalent to 320 CSS pixels.
3. Size tap targets for a thumb: at least 24 by 24 CSS pixels under WCAG 2.2, and ideally around Apple's default of 44 by 44 points.
4. Keep the first screen useful: the headline, the offer and the next step, readable without zooming or scrolling.
5. Load fast on mobile data, and don't cover the page with pop-ups.

Google retired its Mobile-Friendly Test and Search Console's Mobile Usability report on 1 December 2023, so check pages in Chrome's device mode and with a Lighthouse mobile run instead, and read real visitors' data in the Core Web Vitals report.

How did we build our own site for phones?

We rebuilt ranknexus.com phones first in October 2026, and every change is checked at 360 and 390 pixels wide before desktop. Three patterns from it:

• A dock instead of a hamburger menu. A floating bar at the bottom holds Home, Services, Contact, Work and More, with Contact in the middle where a thumb lands. It shrinks as you scroll.
• A form in three steps. On phones our contact form starts with a tap on what you need, then asks for your details, then your message. On desktop it stays a single form.
• Prices in one tap. Our pricing page shows plan tabs with the price on each, and each tab opens a full-width plan rather than a half-hidden card.

Two smaller rules: there is no loading screen, and long text is folded behind a Read more link on phones while the full text stays in the page's HTML. For quick contact we offer WhatsApp rather than tap-to-call. We claim no conversion lift from these choices; they are the standard we hold our own pages to.

How do you make a form easy on a phone?

Cut the typing, and make the typing that's left easy:

• Start with choices. Ask what someone needs with buttons before you ask for their details, as our three-step form does.
• Use the right keyboard. MDN's reference says the tel input type “causes mobile browsers to display a special keyboard for entering phone numbers”, and an email keyboard “Typically includes the @ character”.
• Let the browser fill fields in. The autocomplete attribute tells the browser what each field is, so saved names, emails and numbers can be filled in for the visitor.
• Ask fewer questions, and make most of them multiple choice. Meta's advice for its own forms applies to yours.
• Make every field and button easy to hit: WCAG 2.2's minimum target is “at least 24 by 24 CSS pixels”, and Apple's default control on iPhone is 44 by 44 points.

Do pop-ups hurt mobile conversions?

Intrusive ones work against you. Google describes intrusive interstitials and dialogs as page elements that “obstruct users' view of the content, usually for promotional purposes”, and warns that interrupting people with them “may frustrate them and erode their trust in your website”. Its advice is to “use banners that take up only a small fraction of the screen” instead, and: “Don't obscure the entire page with interstitials.”

Google's page experience guide asks the same question of every page: “Do your pages avoid using intrusive interstitials?” Some of the pages that rank for mobile conversion tips are written by companies that sell pop-up tools, so weigh their advice against Google's.

How do you test your site on mobile?

• On real phones first, an iPhone and an Android if you can, on mobile data rather than office Wi-Fi.
• In Chrome's device mode for quick checks at 360 and 390 pixels wide.
• With PageSpeed Insights' mobile tab for speed, reading the field data before the score.
• With Search Console's Core Web Vitals report, mobile tab, for real visitors across your site.
• By sending yourself a test enquiry from a phone and checking that it arrives.

The test enquiry is one of the five checks in our guide to website traffic but no leads, and our page speed guide explains field data and lab scores.

How do you measure mobile conversion?

Compare devices side by side. GA4's Device category dimension splits activity into “'desktop', 'mobile', and 'tablet'” and is “populated automatically”, so add it to the report that shows your enquiries and compare the enquiry rate for each. Both Google Ads and Meta Ads Manager can break results down by device too.

A gap between devices is a clue, not a verdict: phone visitors may be earlier in their decision. Compare the same page and the same traffic source before you change anything, and count enquiries as key events so the comparison means something. The free Cost Per Lead Calculator then shows what each device's leads cost you.

Mobile conversion myths, and the facts

Questions people ask about mobile conversion

What is CRO for mobile?

It is conversion rate optimization for phone visitors: a fast first screen, the next step in thumb reach, big tap targets and a form that asks for taps before typing, all judged on mobile data rather than desktop.

How do I improve my mobile conversion rate?

Speed up the first screen, put the offer and the next step where they show without scrolling, make buttons at least 24 by 24 CSS pixels, start forms with choices, use the right keyboard for each field and remove intrusive pop-ups. Then compare mobile and desktop in Google Analytics 4.

Why is my mobile conversion rate lower than desktop?

Phones load pages on slower connections and processors, show one narrow column and make typing harder, so every weak spot costs more. Compare the same page and traffic source by device to find where phone visitors drop off.

What makes a good mobile landing page?

One offer and the next step on the first screen, fast loading on mobile data, proof close to the button, a short form that starts with choices and a second way to ask, such as WhatsApp.

What are mobile UX best practices?

Design for one column and a thumb: big, well-spaced tap targets, the main action within reach, simple navigation, readable text, no intrusive pop-ups and forms with as little typing as possible.

How do I test my website on mobile?

Use a real phone on mobile data first, then Chrome's device mode for quick checks, PageSpeed Insights' mobile tab for speed, Search Console's Core Web Vitals report for real visitors and a test enquiry sent from a phone.

Open your best-selling page on your own phone today and run the nine checks. If you'd rather we fix it, see conversion optimization, and our Meta Ads work for funnels built on phone-first lead forms.

About this article

Google's guidance is quoted from Search Central, Google Ads Help and Google Analytics Help; form behavior from MDN Web Docs; target sizes from W3C's WCAG 2.2 and Apple's Human Interface Guidelines; and Meta's from its Business Help Center, all read on 20 October 2026. The screenshots show our own live site on 20 October 2026, and the speed figures are our own Lighthouse runs that day. We claim no conversion results from our design choices.