Mobile-First Design: Why It Matters for Buyers

Google indexes the mobile version of a site. Not the desktop version with mobile as a consideration — the mobile version, as the primary source of what gets ranked. If the site you are buying hides content on small screens, that hidden content is largely what Google does not see.

That single fact turns mobile quality from a user-experience preference into a valuation question.

Why This Changes What a Site Is Worth

Mobile-first indexing. What is not in the mobile HTML is not being indexed. Sites that collapse sections, defer content behind tabs rendered only on desktop, or serve a stripped-down mobile template are being ranked on less content than they appear to have.

Most traffic is mobile. Roughly two thirds of web traffic across most consumer niches. A site with poor mobile conversion is leaving the majority of its audience underserved, which is either a problem you inherit or an opportunity you buy cheaply — depending on how fixable it is.

Core Web Vitals are measured on mobile. Google's field data weights mobile experience. A site passing on desktop and failing on mobile is failing.

What to Check Before You Buy

Open it on a real phone. Not a resized browser window — an actual device on a real connection. Emulators do not reproduce touch behaviour, mobile network latency, or how heavy the page feels.

Compare mobile and desktop HTML. Fetch the page with a mobile user agent and again with a desktop one, then compare the text content. Substantially less text on mobile means substantially less indexed content. This is the single most valuable check on this list and almost nobody does it.

Touch targets. Interactive elements should be around 44×44 CSS pixels with spacing between them. Links packed into a dense paragraph are unusable with a thumb.

Body text at 16px or larger. Below that, mobile browsers may zoom, and reading suffers.

Forms. Input types should trigger the right keyboard — type="email" for email, type="tel" for phone. Getting this wrong on a checkout form measurably costs conversions.

No horizontal scroll. One element wider than the viewport ruins the whole page. Scroll every page sideways to confirm nothing moves.

Test the money path. Whatever the site exists to do — a purchase, an enquiry, a signup — complete it end to end on a phone. This is where sites fail, because it is the flow nobody tests after a redesign.

Responsive Versus Adaptive, Practically

Responsive uses one HTML document and CSS that adapts. One codebase, one URL, one thing to maintain.

Adaptive serves different layouts per device class, sometimes from different templates. It performs well when done properly and creates real risk when not: two codebases drift, and the mobile one is usually the neglected half.

Separate mobile URLs (an m. subdomain) are legacy. If the site you are buying uses them, budget for a migration — and check the canonical tags carefully, because misconfiguration here causes serious indexing problems.

Common Failures in Sites for Sale

Content hidden behind desktop-only tabs. Fine for users; a real indexing problem if the mobile version never renders it.

Images without responsive sizing. A 3000px hero downloaded on a phone destroys load time and Core Web Vitals.

Interstitials on mobile. Pop-ups covering content on entry are a documented ranking negative on mobile specifically.

Hover-dependent navigation. Menus that open on hover have no equivalent on touch. Sometimes an entire section becomes unreachable.

Fixed elements eating the viewport. A sticky header plus a cookie banner plus a chat widget can leave a phone user with a third of the screen.

Verifying Within the Escrow Window

On Escrozon the seller is paid when you confirm receipt, so the mobile audit happens while funds are still held. Do the mobile-versus-desktop HTML comparison first — it is quick and it is the check that most often finds something material. Then complete the site's primary conversion flow on a phone.

If mobile behaviour materially contradicts the listing, that is grounds for a dispute, and the deal chat record of what was claimed is what supports it.

Frequently Asked Questions

How do I compare mobile and desktop HTML without tools? Most browsers' developer tools let you set a mobile user agent, reload, and view source. Copy the visible text from each into a document and compare length. A large gap is your answer.

Is a slow mobile site fixable? Usually, and often cheaply — image optimisation and deferring third-party scripts account for most of it. What is not cheap is a heavy page-builder theme, where the weight is structural.

Does responsive design hurt desktop? No. A well-built responsive site serves desktop fully. Problems come from designing for mobile only and letting desktop become an afterthought.

How much should poor mobile reduce the price? Price the fix, not the flaw. Get a quote for the work and negotiate against it. If the cause is a heavy theme, that is a rebuild rather than a fix, and the discount should reflect it.

Do I need to test on both iOS and Android? Test on whichever you have, then check the site's own analytics for its actual device split. If a meaningful share is on the platform you did not test, borrow a device before confirming.