The mobile version: what breaks most often
More than half of your visitors come from a phone, and search engines evaluate a site by exactly that version. Meanwhile sites are usually built and checked on a large monitor — hence the gap between what the owner sees and what the client sees.
Search engines judge a site by its mobile version, so your positions are decided by what the crawler sees on a phone. Four things break most often: horizontal scrolling, small buttons, full-screen popups and awkward forms. All of it can be checked in ten minutes on your own phone.
In this article7 sections
Why the mobile version matters more than the desktop one
Search engines have switched to evaluating the mobile version. That means a site's positions — including on desktop — are determined by what the crawler sees on a phone.
The second argument is more prosaic: if a person cannot leave a request from their phone, they will not open a laptop. They will open a competitor.
If part of the content visible on desktop is hidden on mobile, a search engine may not count it at all — it looks at the mobile version.
What breaks most often
Horizontal scrolling
Something does not fit the screen and the page shifts sideways. The usual culprits are wide tables, long words, fixed-width images or blocks with negative margins.
Small buttons and links too close together
A finger is thicker than a cursor. A button under 24 pixels, or two links side by side, means people tap the wrong thing and get annoyed. Usability tools flag this too.
Text you have to zoom in on
A font under 14–15 pixels reads poorly on a phone. This applies especially to legal blocks and captions.
Full-screen popups
A window covering the content immediately after entry is a direct violation of search engine guidance and a guaranteed way to lose people.
Forms that are awkward to fill in
The phone field opens a letter keyboard, the email field opens the plain one, the date picker does not work. All of it is solved by setting the correct field types.
A menu that will not close
Or closes only via a cross in an awkward place. The person gets stuck and leaves.
Heavy images
On mobile internet a 3-megabyte image means several seconds of waiting. And it is often displayed in a 300-pixel-wide block anyway.
How to check it yourself in ten minutes
- Open the site on your own phoneOn a real device, not in a browser emulator, and preferably not the newest one.
- Turn off Wi-FiCheck on mobile data — the way a client does on the move.
- Walk the client's pathFind the service, find the price, leave a request, try calling via the button.
- Swipe sidewaysOn every page. If anything shifts, you have a width problem.
- Tap everythingButtons, menu links, the phone, messengers. It all has to work on the first attempt.
- Check on a small screenNot every phone is large. A 360-pixel width is common.
What must definitely be in order
- The phone number is tappable and dials immediately.
- The request button is visible on the first screen without scrolling.
- The form can be filled in with one hand.
- Prices are readable without zooming.
- Tapping the address opens a navigation app.
- The menu opens and closes predictably.
- Nothing extends past the edge of the screen.
Forms on a phone
A topic of its own, because this is exactly where requests are lost. A correctly configured field opens the right keyboard and offers saved data.
- The phone field should open a numeric keyboard, not a letter one.
- The email field — a keyboard with an @ sign.
- Autofill must work: the browser inserts name and phone from memory.
- Fields should be at least 44 pixels tall — otherwise they are hard to hit.
- The submit button must not be covered by the keyboard.
What often breaks after updates
The mobile version breaks quietly: on a desktop everything looks fine, and nobody notices for weeks.
- A table was added to a text — horizontal scrolling appeared.
- A widget was installed — it covered the request button.
- A large image was uploaded — the page now loads twice as slowly.
- The font was changed — text became smaller on small screens.
- A popup was added — it covers the whole screen.
Make it a habit to open the site on a phone after every update. It takes thirty seconds and saves weeks of lost requests.
Separate version or responsive
It used to be common to build a separate mobile site on a subdomain. Today that is almost always a bad idea: you maintain two sites, their content drifts apart, and you get duplicates and address confusion.
The standard is one responsive version that rebuilds itself according to screen width. One address, one set of content, one maintenance workload.
Frequent questions
How do we tell whether the mobile version is holding us back?
Compare metrics by device in analytics: if exits from phones are noticeably higher and conversion on the same traffic is lower, the problem is the mobile version.
Should we write separate texts for mobile?
No, the content should match. Hiding part of the text on mobile is risky: a search engine may not count it.
What to do about long tables on a phone?
Give them horizontal scrolling inside their own block so the table shifts rather than the whole page. Or rebuild the rows as cards, which reads better.
Are promo popups acceptable?
They are, if they do not appear immediately, do not take the whole screen and close easily. A full-screen window on entry is a direct route to losing people and to search engine complaints.
Do we need a separate mobile menu?
Not a separate menu but an adapted one: the same items, collapsed into a button. Different sets of items on phone and desktop confuse people and complicate maintenance.
How small can tap targets be?
Twenty-four pixels is the accepted minimum, and forty-four is comfortable. Anything smaller means mistaps, and usability checks flag it.
The materials answer general questions. We will look at your specific case — free and without obligation.