A mobile website version is how you show the same content on a phone without horizontal scroll, tiny text, and broken forms. It used to mean a separate m.site.ru address. Today at NUGU and for most clients in Sochi the right answer is a responsive website: one URL, one CMS, layout that adapts to screen width.

Separate mobile version: where it still appears

**Subdomain m.example.com or a separate template.** Lightweight copy of the main site.

**Historical pros:** content could be heavily trimmed for 3G.

**Current cons:**

  • duplicate content and SEO confusion;
  • prices and promos out of sync;
  • ad links often land on desktop;
  • split analytics;
  • double maintenance cost.

Yandex and Google recommend responsive or dynamic serving, not a separate m-site on another URL.

Responsive as the mobile standard

One HTML, media queries, mobile-first design:

  • burger menu with clear items;
  • buttons from 44 px, clickable phone;
  • forms with type=tel, no zoom on focus;
  • images via srcset and WebP;
  • blocks reorder: on mobile CTA higher, heavy tables in accordions.

That is the modern "mobile version" without a second site.

Mobile traffic share in Sochi

For local business — hotels, restaurants, healthcare, real estate, services — mobile is often 60–80% of sessions. It grows in summer season: tourists search "near me", "today", "with reviews" from a phone on the promenade or in a taxi.

If the mobile experience is poor, you pay for Direct clicks and lose the customer on the landing page.

Mobile UX: what to check

**First screen.** Offer, price or "from", enquiry button, tap-to-call.

**Speed.** LCP under 2.5 s on 4G — see website load speed. Heavy sliders and autoplay video on mobile hurt.

**Forms.** Submit from iPhone and Android, success message, manager notification.

**Maps and widgets.** Yandex Maps should not cover half the screen without a close control.

**Content.** Do not hide important blocks with display:none on desktop only — SEO risk.

Mobile and SEO

Mobile-first indexing: Google and Yandex treat mobile as primary. At website launch check:

  • viewport meta;
  • one canonical URL;
  • structured data valid on mobile;
  • no full-screen "download our app" interstitial;
  • Core Web Vitals green or close.

AMP and PWA — do you need them

**AMP** is almost unnecessary for a typical business site in Russia.

**PWA** (home screen icon, offline) fits services with repeat visits; for ad landing it is overkill.

When to rebuild mobile

  • Fixed 1200 px width site, "microscope" on phone.
  • m.site.ru exists with outdated content.
  • Mobile conversion 2–3× lower than desktop with comparable traffic.
  • Ads run but no phone enquiries.

Fix: mobile-first redesign or new site. Rebuild of old site — from 50 000 ₽; new landing — from 30 000 ₽.

Mobile-ready site cost at NUGU

No separate "mobile version" line — responsive is standard:

  • landing — from 30 000 ₽;
  • service site — from 50 000 ₽;
  • corporate — from 80 000 ₽;
  • store — from 140 000 ₽;
  • Quick Start — 35 000 ₽, 7 days.

Mobile version checklist

  • No horizontal scroll at 320 px.
  • Body text from 16 px, sufficient contrast.
  • CTA on first or second screen.
  • Phone and WhatsApp/Telegram — one tap.
  • Form works; keyboard does not cover fields.
  • Speed: Lighthouse Performance 70+ on mobile.
  • Tested on real Android and iPhone, not only emulator.

Dynamic serving and mobile apps

**Dynamic serving** — one URL, different HTML for mobile and desktop by User-Agent. Rare legacy compromise; harder to maintain than responsive.

**Mobile app** — not a replacement for a mobile website. Booking or loyalty apps complement the site, but ads and search still land on web.

Mobile for local business in Sochi

Clinics, salons, auto service: Call and WhatsApp in sticky footer. Real estate: filters and full-screen map on mobile. HoReCa: replace PDF menu with HTML price block — PDF is awkward on phones.

A/B tests on mobile

Change block order, CTA copy, button colour — but test only after 200+ mobile sessions or conclusions are random. Metrica and Webvisor show scroll depth and clicks.

Migrating from m-version to responsive

If you have m.site.ru — set 301 to main domain, migrate content, check Webmaster. NUGU runs migration without drops with correct redirects. Timeline — 2–4 weeks depending on volume.

When to contact NUGU

You suspect lost phone enquiries — send the URL. In Sochi we run an express mobile UX audit and propose targeted fixes or a new responsive build.

Contacts — describe niche and traffic source (ads, SEO, social).

Mobile and ad budget

Every month of Direct spend on a landing that fails on phones is wasted budget. Before scaling campaigns ensure mobile conversion is not more than 1.5× lower than desktop. If the gap is larger — fix UX first, then raise bids. NUGU connects Metrica and sets mobile/desktop segments in reports.

Remember: mobile-first at NUGU is standard on all tiers, from 30 000 ₽ landing to 140 000 ₽ store. We do not charge a separate "mobile add-on" — that is baseline hygiene in 2026.

Test your site now: open on a phone, find the enquiry button in 5 seconds. If you cannot — that is a NUGU task, not "cosmetics".

Compare mobile and desktop in one Metrica report for the last 30 days: if conversion gap exceeds 50% — that is priority #1 before SEO, content, and new campaigns. Fixing mobile often adds 20–40% enquiries without increasing ad spend.