The 80/20
Most slow Indian websites are slow for three reasons: unoptimised images, too much JavaScript, and a server far from the user. Fixing those three typically recovers 70–80% of the available speed.
Speed is not a vanity metric in India. A large share of your traffic arrives on mid-range Android phones over variable mobile data. A site that feels instant on your office fibre connection can be genuinely unusable for the customer you are trying to win.
Measure before you optimise
Guessing wastes money. Use these three, in this order:
- PageSpeed Insights Test your key pages and read the mobile score, not desktop. Desktop scores flatter you and are not where your traffic is.
- Chrome DevTools, throttled Open your site with the network throttled to "Fast 3G" and CPU throttled 4×. This approximates a real mid-range phone far better than your laptop does.
- Search Console Core Web Vitals This shows data from your actual visitors rather than a lab simulation, which is what Google ultimately uses.
The three metrics that matter
| Metric | What it measures | Target | Usual cause when poor |
|---|---|---|---|
| LCP | When the main content appears | < 2.5s | Large images, slow server |
| INP | Responsiveness to taps | < 200ms | Heavy JavaScript on the main thread |
| CLS | Visual shifting while loading | < 0.1 | Images/ads without reserved space |
Fixes ordered by impact per hour of work
1. Images — usually the single biggest win
On most business sites, images are 60–80% of page weight, and most are dramatically oversized. A 4,000px photo displayed at 800px wastes the majority of its bytes.
- Serve WebP or AVIF instead of JPEG/PNG — typically 30–50% smaller.
- Resize to the largest size actually displayed, then serve responsive variants.
- Add
loading="lazy"to everything below the fold. - Always set width and height attributes — this alone fixes most layout shift.
- Never let a hero image exceed roughly 200KB.
2. JavaScript — the usual cause of poor interactivity
Every script must be downloaded, parsed, and executed, and on a budget phone the parsing is what hurts. Audit what you actually need:
- Remove analytics and marketing tags nobody reads any more.
- Defer non-critical scripts with
deferorasync. - Drop jQuery if it exists only for two small effects.
- Question chat widgets and heatmap tools — they are frequently the heaviest thing on the page.
- Self-host fonts rather than loading them from a third party.
3. Hosting and server location
If your customers are in Bengaluru and your server is in the United States, every request pays a fixed physical penalty of 200–300ms that no amount of code optimisation can recover.
Cheapest high-impact fix available: move to a host with an Indian region (Mumbai is standard) or put Cloudflare in front of your existing host. For an India-focused business this frequently beats weeks of code optimisation.
4. Fonts
Custom fonts routinely block text from rendering. Limit yourself to two families and a small number of weights, use font-display: swap so text appears immediately, and preconnect to the font host.
5. Caching
Set long cache lifetimes on static assets so returning visitors download almost nothing. On WordPress a caching plugin does most of this; on custom sites it is a few lines of server configuration.
WordPress-specific quick wins
- Audit plugins — deactivate anything unused, and check what each adds to page weight.
- Replace bloated multipurpose themes with something lean.
- Install one caching plugin, not three fighting each other.
- Clean the database of post revisions and expired transients.
- Disable embeds and emoji scripts you do not use.
What "fast" is worth
Speed is not an engineering nicety. It is the difference between a visitor reading your offer and a visitor who never saw it.
Every additional second of load time measurably reduces conversion, and the effect is amplified on mobile data. For a business generating leads through its website, performance work usually pays back faster than a redesign does.
If your site is slow and you would like a specific, prioritised diagnosis rather than generic advice, send us the URL. See also our guides on local SEO for Bengaluru and schema markup.