Key Takeaways
- Indian speed guides put ~60% of Indian sites outside Core Web Vitals thresholds against ~40% globally, with ~80% of Indian traffic on mobile. Google ranks the mobile experience.
- Five causes, five fixes: image weight → compression and sizing; builder themes → a light theme; hosting abroad → Indian data centre or CDN edge; blocking JavaScript → defer and diet; no caching → server and browser caching.
- Measure on a mid-range Android on throttled 4G, not on a laptop. The guides estimate image work alone moves scores 30–40%.
- A one-second mobile delay is put at up to 20% fewer conversions by the guides; on a store that is revenue, not a score.
Your website is slow on Indian mobile data for reasons that are specific to how Indian sites are built and where Indian users are. The speed guides written for this market in 2026 put around 60% of Indian websites outside Google’s Core Web Vitals thresholds, against roughly 40% globally, with about 80% of traffic on mobile — and Google indexes and ranks the mobile experience. The gap between the office laptop and the customer’s ₹12,000 Android on a variable 4G connection is usually four to six seconds, and it is made of five things. Each has a fix a developer can ship in days.
First, Measure Where the Customer Is
Every slow Indian site we see passed its own developer’s test, because the test was a laptop on office Wi-Fi. Before fixing anything, measure honestly:
- Open PageSpeed Insights and read the mobile score and the field data (Chrome UX Report), which reflects real Indian visitors on real connections.
- In Chrome DevTools, throttle to “Slow 4G” and a 4× CPU slowdown — a fair proxy for a mid-range Android on Jio or Airtel outside a metro core.
- Note three numbers: Largest Contentful Paint (should be under 2.5s), Interaction to Next Paint (under 200ms), Cumulative Layout Shift (under 0.1).
Those three are the ranking inputs, and they are also what your customer feels.
The Five Causes and the Five Fixes
| Cause | What it does on 4G | The fix |
|---|---|---|
| 1. Image weight | A 3MB hero and 800KB product shots take the whole budget | WebP/AVIF, sized to the slot, compressed, lazy-loaded below the fold; guides put this at a 30–40% score gain alone |
| 2. Builder themes | A megabyte of CSS and JS on every page before content renders | A light or hand-built theme; remove the builder or restrict it to the pages that need it |
| 3. Hosting abroad, no Indian edge | Every request crosses an ocean; latency stacks | Indian data centre (Mumbai, Chennai, Hyderabad) or a CDN with Indian edges |
| 4. Blocking JavaScript | Chat widgets, analytics, sliders and app scripts block the first paint | Defer and async everything non-critical; delete the widgets nobody uses; one analytics tag |
| 5. No caching | Every visit rebuilds every page | Server-side caching, browser cache headers, a CDN cache for static assets |
Do them in that order. The first two are usually 70% of the problem; the last three finish it.
Why It Is Revenue, Not a Score
Speed guides cite Google’s own figure that a one-second mobile delay cuts conversions by up to 20%. On a store selling ₹20 lakh a month, a site that loads in six seconds instead of two is not scoring badly; it is leaving lakhs on the floor every month, and paying for ads that land on a page people abandon.
It is also a ranking input. Core Web Vitals are part of how Google orders results, and with mobile-first indexing the mobile numbers are the ones that count. A slow site pays twice: it ranks lower, and it converts less of what it does get. That is why speed is the first thing we fix on any Indian site before content or links, and why the Kolkata page lists Core Web Vitals “measured on a mid-range Android on Jio” among its twelve technical checks.
What Not to Do
- Do not install a “speed plugin” and stop. Caching plugins help; they do not shrink a 3MB image or remove a builder.
- Do not trust a desktop score. Ninety on desktop and thirty-five on mobile is thirty-five.
- Do not add a second CDN or a second analytics tag to fix the slowness the first ones caused.
- Do not rebuild the whole site before trying the five fixes. Most Indian sites go from failing to passing without a redesign; the ones that do not are the builder-theme sites, and for those the theme is the redesign.
Frequently Asked Questions
Why is my website slow on mobile in India?
Five common causes: heavy images (often 3MB heroes), page-builder themes shipping a megabyte of CSS and JavaScript, hosting abroad with no Indian CDN edge, blocking scripts (chat widgets, sliders, multiple analytics tags), and no caching. Indian speed guides put around 60% of Indian sites outside Core Web Vitals thresholds for these reasons.
What are Core Web Vitals and why do they matter in India?
Three measurements of real user experience: Largest Contentful Paint (under 2.5s), Interaction to Next Paint (under 200ms) and Cumulative Layout Shift (under 0.1). They are ranking inputs, and with about 80% of Indian traffic on mobile and mobile-first indexing, the mobile numbers are the ones Google uses.
How do I test my site speed properly?
PageSpeed Insights on mobile, reading the field data from real visitors; and Chrome DevTools throttled to Slow 4G with a 4× CPU slowdown, which approximates a mid-range Android on Jio or Airtel outside a metro core. Ignore desktop scores.
What is the quickest speed fix?
Images. Converting to WebP or AVIF, sizing to the slot, compressing and lazy-loading below the fold moves scores 30–40% on most Indian sites according to the guides. Removing a page builder is the second largest fix and the harder one.
Does hosting location matter for Indian visitors?
Yes. Every request to a server in the US or Europe adds latency that stacks across dozens of files. An Indian data centre or a CDN with Mumbai and Chennai edges removes most of it for the cost of a plan change.
Planning a site or a store?
Book a free strategy call. We look at what you have, tell you what it should cost to fix or replace — honestly, including “keep it” — and you get a staging URL from week one if we build it.
Book a Free Strategy Call