Open Search Console on almost any Indian site and the device split is lopsided: mobile dominates, often by four to one. Then open the site on a three-year-old Android handset on a patchy 4G connection and you discover it was designed on a MacBook on office fibre.
That gap is not an aesthetic problem. It shows up directly in rankings and more directly in revenue, and it is the single most under-diagnosed issue on Indian websites.
Test on the device your traffic actually uses
Most performance testing in India is done wrong in one specific way: it is done on good hardware and good connections, including by tools run at default settings. Lab scores come back acceptable and field data in Search Console tells a different story.
The useful habit is simple. Throttle to mid-tier mobile CPU and a slow-4G connection, and test the three pages that actually matter — your highest-traffic landing page, your main service or category page, and your enquiry or checkout page. Then compare against Search Console's Core Web Vitals field data, which is real users on real devices. When lab and field disagree, field wins.
The usual culprits, in the order they usually appear
Hero images that were never resized. A 2.4MB JPEG at 3000px wide, served to a 360px screen. This is still, in 2026, the most common single cause of a bad LCP on Indian sites. Resize, serve WebP or AVIF, and set explicit width and height so the layout does not jump.
Fonts loading before anything renders. Three weights of two families, blocking, no font-display: swap. On fibre this is invisible. On slow 4G it is two seconds of blank screen.
Chat widgets, popups and tag managers. Most Indian sites carry a chat widget, an exit-intent popup, two analytics scripts, a heatmap tool, a pixel, and a review widget. Each was added by someone reasonable for a reasonable purpose. Together they are often more JavaScript than the site itself. Audit what is loading; a meaningful fraction is usually for a tool nobody logs into any more.
Sliders. A homepage carousel loads every slide's image to show one. It is almost always the heaviest element on the page and almost always the least used.
Interaction delay is the one people miss
Loading gets the attention; responsiveness gets ignored. On a mid-range phone, a page that paints in two seconds but freezes for half a second when someone taps the menu feels broken, and INP measures exactly that. The causes are usually long JavaScript tasks on the main thread — a large bundle executing, a third-party script initialising, an event handler doing too much work.
The practical test is not a score. It is tapping your own navigation, your own filters and your own form fields on a throttled phone and noticing whether anything lags. If it does, your users noticed first.
Forms are where mobile traffic is actually lost
Rankings get the attention and forms lose the money. On Indian mobile sites the recurring faults are consistent: a phone field without type="tel" so the keypad does not switch, an email field without type="email", a CAPTCHA that is unreadable at 360px, nine fields where four would do, and a submit button that sits below a sticky footer bar and cannot be reached.
None of this is an SEO issue in the narrow sense. All of it decides whether the traffic you worked months to earn turns into an enquiry. Fixing a form is usually a one-hour job with a larger effect on revenue than a month of link building.
Data cost still shapes behaviour
Indian mobile data is cheap by global standards but users are not indifferent to it, particularly outside the metros. Heavy autoplay video, uncompressed images and large background assets get abandoned rather than endured. Lazy-load below-the-fold media, never autoplay video with sound, and do not ship a 5MB homepage to somebody who is checking your opening hours.
A half-day audit that usually finds everything
Throttle to mid-tier mobile and slow 4G. Load your top three pages. Record LCP, CLS and the feel of tapping things. Open the network panel and sort by size — the top five requests are usually your whole problem. Open the coverage panel and see how much JavaScript is unused. Submit your own enquiry form, on a phone, one-handed.
Write down what you find and fix the three biggest items. That is normally most of the available gain, and it costs a day rather than a redesign.
Deep Bhardwaj runs this audit as the opening step on most Indian sites, because it is cheap, it is quick, and it almost always finds something that is quietly costing more than the rankings everyone is worried about.
Related: once the pages are fast, the next question is which pages should exist at all — see an SEO audit is not an SEO strategy.