The statement ‘mobile converts worse than desktop’ is both true and useless. It does not tell you whether the difference comes from a different stage in the decision process, a different type of traffic or a button that cannot be tapped with a thumb. As long as you treat mobile as a single underperforming segment, there is nothing specific to fix.
We deliberately give no ‘industry averages’ for mobile conversion in this article. Figures circulating online come from different markets, industries and definitions, and comparing yourself with them leads to bad decisions more often than good ones. Your benchmark is your own result from the previous quarter.
Some of the difference is natural—establish how much
Phones and computers are used at different points in the decision process. Someone browses an offer while queuing at the till, then returns to it on a laptop that evening. This is not a problem to fix—it is how people buy. The key is to separate this part from barriers you can actually remove.
Scroll the table sideways to see all columns.
| Observation | Natural difference | Genuine barrier |
|---|---|---|
| Shorter visits | Browsing on the move and returning later | Slow loading or an illegible layout |
| Fewer completed forms | Entering details on a phone is slower | The wrong keyboard for the field or rigid validation |
| More visits from social media | A different, less committed audience | A landing page that does not match that traffic |
| Fewer high-value purchases | Larger decisions are made on a larger screen | No option to save the offer for later |
| More return visits | A natural consideration stage | No quick way to find something viewed earlier |
A practical tip: instead of comparing mobile with desktop, compare mobile with its own performance from the previous quarter and across pages. A drop on one page while results remain stable elsewhere is a much stronger signal than the difference between devices.
Filter the data down to mobile traffic alone, then look for the stage with the biggest drop. See how Meetlead segments behaviour by device.
Where the real problem is most often found
Once the data is filtered to phone traffic alone, the problems start falling into recurring categories. The four below account for most of the differences you can eliminate.
- Touch targetsButtons that are too small or too close together. Repeated taps beside the element reveal the problem.
- Content orderElements that sit side by side on desktop are stacked on a phone—often in the wrong order.
- Floating elementsTogether, a consent banner, promotion bar and live-chat launcher can cover half the screen.
- FormsThe wrong keyboard for a numeric field, autofill that does not work, and validation on every keystroke.
The third problem is especially common and especially easy to miss because the team usually tests the website after dismissing the consent banner. Once a quarter, open the site on a phone in private browsing mode and check how much room is left for the content.
- 0:00
A visitor arrives from a search engine on a service page
- 0:04
The consent banner covers the heading and contact button
- 0:11
Two taps beside the button; the page does not respond
- 0:19
The visitor leaves without interacting with the offer
Some defects affect only a narrow group of phone configurations and therefore disappear into the average. We explain how to spot them in our article on errors visible to only some users.
How to check in practice
Mobile diagnosis differs from desktop diagnosis in one respect: you must consistently stick to one device category throughout the analysis. Mixing data at any stage invalidates the conclusions.
- Choose one important page.Ideally, choose the one with the most mobile traffic and a clear objective.
- Filter for mobile traffic only.Do this separately in quantitative data, heatmaps and the recording selection.
- Check scroll reach.If key information sits below the point reached during most visits, you have a candidate cause.
- Look for taps with no effect.Repeated taps in the same place usually indicate an element that looks interactive but is not.
- Watch ten phone recordings.Look for the moment when the pace slows or the user goes back.
- Follow the journey yourself on your phone.Do not use the browser’s device preview. Use a real device, a real connection and private browsing mode.
We explain how to read heatmaps and select recordings in more detail in our guides to reading heatmaps and analysing session recordings. One more rule applies on mobile: do not judge the layout from a screenshot of your own phone, because resolutions and screen sizes vary more than you might expect.
A heatmap shows the pattern, a recording shows the sequence, and a conversation tells you what was missing. Schedule an implementation—we will help you set up the first analysis exclusively for mobile traffic.
Contact on a phone follows its own rules
On a computer, a form is a natural way to make contact. On a phone, it can be the worst possible option: it requires typing details, switching keyboards and a degree of patience nobody has while standing at a bus stop. That is why the arrangement of contact channels should be different on a small screen.
- A phone number presented as a clickable link, not text that must be copied.
- A shorter mobile version of the form if the full version is not essential.
- The correct keyboard type for numeric and email fields.
- A live-chat launcher that does not cover the purchase button or menu.
- A callback request as an alternative to a long form.
- Clear availability information when nobody is there.
We explain how to choose fields and microcopy in our guide to website contact forms, and when a callback works better in our article on website callbacks.
Tapping a phone number and asking one question in live chat takes a customer a few seconds. A form takes a minute. Explore the contact channels and see what suits your traffic.
While you are there, check whether those channels work without a mouse and with a screen reader—it is easy to create an element on mobile that cannot be closed. We explain the method in our guide to accessible contact journeys.
If a sticky bar covers a form control, use the guide: Sticky elements covering buttons: find collisions on your website.
A quarterly mobile review
- Open the website on a phone in private browsing mode and follow the entire path to contact.
- Check how much of the screen is covered by the consent banner, promotion bar and launcher combined.
- Compare mobile performance with your own result from the previous quarter, not an online average.
- Review scroll maps for your most important pages, separately for phones.
- Watch several recordings of sessions that ended without an interaction.
- Read the questions asked in live chat from mobile devices—they may differ from those asked on desktop.
The last point reveals a surprising amount. Questions asked on phones are shorter and more often concern things the visitor simply could not find. That gives you a ready-made list of gaps in the mobile navigation with no additional analysis.
