Mobile-first isn't optional here, it's the baseline.

"Mobile-friendly" was always the wrong bar. In a market like India, mobile isn't one audience among several; it's most of the audience, most of the time, which means designing for desktop first and adapting down is backwards.

What the numbers actually say about India

Mobile traffic accounts for over 70% of total web usage in India, and roughly 96.6% of Indian internet users access the internet via a mobile device at all, smartphones specifically making up the large majority of that. India now has over a billion internet users, the great majority of them mobile-first by default, not by preference alone. Designing primarily for desktop and treating mobile as an afterthought means building for a shrinking minority of the actual audience.

Google only really looks at the mobile version

Google's indexing runs mobile-first: the crawler evaluates the mobile version of a page to decide how it ranks, full stop. That has specific, measurable consequences. Core Web Vitals (Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift) are measured against mobile rendering, not desktop. Content, internal links, or schema markup present on desktop but missing from the mobile version simply doesn't count toward indexing. The mobile page is the canonical version as far as Google's concerned, not a secondary copy of the "real" site.

Designing mobile-first actually makes everything faster

Starting from a small screen and limited bandwidth forces real discipline: only the strictly necessary assets get prioritized, and everything else loads progressively for larger screens afterward. That constraint produces a leaner, faster codebase across every device, not just mobile. It's a genuine case where a limitation improves the end result rather than compromising it.

A quick, real way to check

Open the site on an actual phone, on a normal connection, and ask: does the main content load within about 2.5 seconds on 4G? Is the text readable without pinching to zoom? Are buttons and links spaced well enough to tap without missing? Can the main action, whether a form, a booking, or a contact request, be completed without unnecessary friction? If the answer to any of these is no, that's a fixable structural issue, not a minor cosmetic one.