The Mobile Version: Why There Is No Traffic Without It

In Russian commercial niches the share of mobile traffic holds at 70–80%, and in services it reaches 85%. Yet decisions about the site are almost always made in front of a desktop monitor — hence the gap between how the site looks in a demo and what the real client sees.

Mobile-first indexing is not the future, it is a fact

Search engines build the index from the mobile version. If part of the content on a phone is hidden, loads after a "show more" click or is missing entirely, that content does not exist for search. We looked at a site where product reviews and specifications rendered on mobile only after a tap — 40% of the useful text simply was not indexed. The principles of responsive design are set out well on web.dev.

A separate mobile subdomain: why not

The m.site.ru scheme made sense ten years ago. Today it means double the maintenance, the risk of content drifting out of sync, mandatory rel=alternate/canonical and constant redirect errors where a phone opens the desktop page and the other way round. Responsive layout on a single URL is cheaper to maintain and more reliable in indexing.

What is most often broken on mobile

• Horizontal scrolling caused by a table or a wide image — an instant bounce
• A "Submit" button under a sticky footer that you cannot reach
• Forms with 30 px fields and no correct input types: the phone opens a letter keyboard
• A full-screen popup 2 seconds after arrival
• The phone number in the header is not a tel: link — the user has to copy the number by hand
• A half-page map that hijacks scrolling

Mobile speed is a discipline of its own

The average Russian user arrives on a device weaker than your work phone and over a connection worse than office Wi-Fi. On a typical site the LCP difference between desktop and mobile is two to three times. Measurement and the order of fixes are described in detail in the article on load speed and in the breakdown of Core Web Vitals.

When you need an app and when a site is enough

An app is justified if you have repeat visits, push scenarios, a loyalty program or an offline mode. For a services site with one purchase a year an app is 1.5–3 million roubles thrown away plus permanent support for two platforms. The sensible order: a responsive site first, then an app once you have a base of returning clients. Our approach to such projects is in the mobile development section.

A 20-minute check

• Open the site on your own phone and try to submit a request — all the way to the end
• Check 360 px width in developer tools: is there any sideways scrolling
• Make sure all the text is in indexable markup rather than loaded by a script on click
• Check that the phone number and address are tappable, and check button sizes
• Compare mobile and desktop LCP on field data

What it gives you in numbers

On a beauty salon project, putting the mobile version in order — reworking the booking form, speeding up the first screen, removing an aggressive popup — raised conversion from 1.8% to 3.4% in a month with no change in traffic. We have seen similar results on other projects: the mobile version almost always delivers a bigger gain than the next rouble spent on ads.

If you are not sure your site works properly on a phone, start with the simplest test — try placing an order on your own site from a mobile, standing out on the street. After that you can discuss the scope of the work through the contact form.