WordPress speed optimisation: the complete 2026 guide for Indian sites
14 min read · 20-Apr-2026
villagehosting.in team
20 April 2026
Indian mobile users leave a page that takes more than 3 seconds to load. Here is the exact playbook we use on every WordPress site we host.
Why Indian sites are slower than they should be
Most Indian WordPress sites are slow for one of three reasons: 1. Wrong hosting — shared plans that are oversold, Apache instead of LiteSpeed, no object cache. 2. Unoptimised images — a homepage with 4MB of JPEG images loaded on a Jio 4G connection is going to be slow. 3. Too many plugins — especially page builders with 300KB of JavaScript that blocks rendering. Fix the hosting first. You cannot cache your way out of a bad server. Once you are on a good host with LiteSpeed Enterprise, a Redis object cache, and SSD storage, the remaining optimisations compound.
Step 1: LiteSpeed Cache plugin setup
LiteSpeed Cache is free and purpose-built for LiteSpeed servers. It is dramatically better than WP Rocket or W3 Total Cache when you are on a LiteSpeed host because it communicates directly with the server's cache layer. Key settings to enable: • Full-page cache: ON • Browser cache: ON • Object cache (Redis): ON — requires your host to have Redis available • Lazy load images: ON • CSS/JS minification: ON — test thoroughly, some plugins break with this on • Critical CSS: ON — reduces render-blocking CSS • Image optimisation: use the built-in LQIP and WebP conversion Do not install WP Rocket alongside LiteSpeed Cache. They conflict.
Step 2: Image optimisation
Images are typically 60–80% of a page's byte weight. For Indian mobile users on 4G with 15–30ms latency to your server, this matters enormously. What to do: • Convert all images to WebP format — 25–35% smaller than JPEG at the same quality • Set width and height attributes on every <img> tag to prevent layout shift • Lazy load images below the fold (LiteSpeed Cache does this automatically) • Use srcset for responsive images — serve a 400px image to mobile, not a 1400px one • Compress uploads before they go in — Squoosh or Optimole handles this automatically Target: no single image above 150KB on mobile. Hero images: under 80KB as WebP.
Step 3: Database optimisation
WordPress databases grow slowly and then all at once. Post revisions, transients, WooCommerce sessions, and expired entries accumulate silently. Run this monthly: • Delete post revisions older than 30 days (WP-Optimize can automate this) • Clear expired transients • Optimise all InnoDB tables • For WooCommerce: clear completed sessions older than 24 hours Also check the slow query log. A single unindexed query on wp_postmeta can add 800ms to every page load. WP Query Monitor plugin will show you which queries are slow and which plugins are causing them.
Step 4: Remove what you do not use
Every plugin adds HTTP requests, JavaScript, and CSS — even if you are not using its front-end features. Audit your plugins. Common offenders: • Contact Form 7 + Flamingo (swap for WPForms Lite or Gravity Forms which load conditionally) • WooCommerce loading cart fragments on non-shop pages • Elementor loading its full CSS/JS library even on pages built with the block editor • Social share plugins that load 8 third-party scripts per page Target: under 20 plugins on a production site. Under 15 HTTP requests on the homepage. Under 500KB total page weight on mobile.
Step 5: CDN setup for Indian users
A CDN caches your static assets (images, CSS, JS) on servers geographically closer to your visitors. For Indian users, this matters most for sites targeting multiple regions — if your server is in Central India, users in Chennai, Mumbai, and Delhi all get similar latency. But for international visitors or to offload bandwidth, Cloudflare Free is sufficient. For most Indian WordPress sites, a good Central India server with LiteSpeed Cache is enough. You do not need a CDN for an Indian business targeting Indian customers if your server is already in India.
Measuring your improvements: the right tools
Use these in order: 1. PageSpeed Insights (Google) — run on mobile, not desktop. The mobile score is what Google uses for ranking. 2. GTmetrix — run from Mumbai node. Free account available. 3. WebPageTest — run from a Jio 4G connection profile from India. Target scores: • Core Web Vitals: LCP under 2.5s, CLS under 0.1, INP under 200ms • PageSpeed mobile score: above 75 • Time to first byte: under 200ms Do not chase 100/100 PageSpeed scores. A 82/100 site that converts well is better than a 100/100 site that is hard to maintain.
related services
Tags: