What are Core Web Vitals and why your Indian website probably fails them
Only 44% of WordPress sites on mobile pass all three Core Web Vitals. In India, where most traffic is mobile and connections are slower, that number is worse. Here's what the metrics actually mean and what to do about them.
Google has been telling us since 2021 that page experience matters for rankings. Most site owners nodded, said "we'll look into it," and moved on. Then they wondered why their organic traffic plateaued.
Core Web Vitals are the specific measurements Google uses. They're not mysterious or technical once you understand what they're actually measuring. And for Indian websites, particularly WordPress sites serving primarily mobile users on variable connections, most of them are failing.
Here's what they are, why they matter, and what you can realistically do about them.
The three metrics
LCP — Largest Contentful Paint
This measures how long it takes for the biggest visible element on the page to load. On most websites, that's the hero image. Google wants this under 2.5 seconds. Above 4 seconds is considered poor.
The most common culprit: an uncompressed hero image. A 4MB JPEG hero loads in under a second on a 100Mbps connection. On a 4G mobile connection in tier-2 India, the same image takes 8-12 seconds. The same image compressed and converted to WebP might be 180KB and loads in under a second on that same connection.
CLS — Cumulative Layout Shift
This is the "page jumps around while loading" problem. You're reading something, an ad loads, everything shifts down, you lose your place. CLS scores that one.
Common causes: images without defined width and height attributes, embeds (YouTube, Google Maps), web fonts that load late and swap in, and banners that load after content. Good CLS is below 0.1.
INP — Interaction to Next Paint
As of March 2024, this replaced FID (First Input Delay). INP measures how quickly the page responds to any interaction — a click, a tap, a key press. Under 200ms is good. Above 500ms is poor.
Heavy JavaScript is usually the cause. Every plugin you add to WordPress loads JS. Every page builder loads more. The compounding effect often means clicking a button on your site takes 600-800ms to visibly respond.
Why Indian websites often score worse
A few India-specific factors that make this harder:
Mobile-first traffic, often mid-range devices. Your analytics probably shows 70-80% mobile traffic. A lot of that is on devices with 2-4GB RAM and mid-range processors. What loads fast on your MacBook will run slow on a Redmi Note.
Images uploaded without optimization. WhatsApp sends compressed images. Marketing teams save from Canva at full resolution. Developers push whatever the client hands over. A typical WordPress media library in India has images averaging 2-3MB that should be 80-150KB.
Too many plugins. The average WordPress site has 20-25 plugins installed. Each one adds weight. The ones that add a slide-in popup, a floating chat widget, and an exit-intent overlay each fire their own JavaScript on every page load.
No CDN. If your hosting is in Singapore or India but your site is slow to load, serving images from a CDN can cut LCP by 40-60% for users outside the server's geography.
How to check where you stand
Go to PageSpeed Insights and enter your homepage URL. It runs Google's Lighthouse and shows you your actual CWV scores with the specific elements that are failing.
Look at the mobile score specifically. That's what Google uses for ranking. The desktop score is almost always better and not where you'll find real problems.
The "Opportunities" and "Diagnostics" sections tell you exactly what to fix and roughly how much impact each fix would have. Pay attention to "Reduce unused JavaScript" and "Serve images in next-gen formats" — these appear on almost every WordPress site.
What actually moves the numbers
Compress and convert your images. This is usually the highest-impact change. Every image on your site should be compressed, and ideally served as WebP (which is 25-35% smaller than JPEG at comparable quality). If you're on WordPress, the OmegaPix Image Optimizer plugin handles this at the plugin level — convert on upload, serve WebP automatically. You can also process images manually in a browser at omegapix.app without installing anything.
Add image dimensions. Every <img> tag should have width and height attributes matching the rendered dimensions. This prevents layout shift as images load. In WordPress, this is usually automatic if you're using the built-in image block, but breaks when you use custom HTML or some page builders.
Audit and cut plugins. Go through every active plugin and ask whether you actually need it. Contact form, SEO, security, caching, and image optimization are legitimate. "Cool exit-intent popup we set up in 2021" is not. Each plugin you remove is JavaScript you no longer pay for on every page load.
Use a caching plugin. WP Rocket, W3 Total Cache, or LiteSpeed Cache (if you're on LiteSpeed hosting). These serve pre-built HTML files to visitors instead of building the page fresh on every request.
Defer non-critical JavaScript. Resources that don't affect the above-the-fold experience don't need to block page rendering. Your caching plugin handles some of this. A developer can do more.
Enable a CDN. Cloudflare's free tier is a reasonable starting point for most small sites. It caches your static assets at edge servers closer to your visitors.
What not to do
Don't obsess over getting 100 on PageSpeed. It's a good target but chasing it can lead to breaking changes. A score of 85-90 with green CWV metrics is genuinely fine and will not hurt your rankings.
Don't buy hosting just because someone said "fast hosting fixes Core Web Vitals." Hosting quality matters but rarely fixes a site with 3MB images and 40 active plugins. Fix the content first.
Don't ignore the mobile score and focus on desktop. Google's ranking signals use the mobile experience. A site that scores 90 on desktop and 45 on mobile is a 45 site.
Frequently asked questions
Do Core Web Vitals directly affect Google rankings?
Yes, they're a confirmed ranking signal in Google Search since 2021. They don't override content relevance — a weak site with great CWV won't outrank a strong site with poor CWV — but when two pages are comparably relevant, page experience is a tiebreaker. For competitive local searches in India, that tiebreaker matters.
My PageSpeed score shows 92 on desktop but 48 on mobile. Which matters for SEO?
The mobile score is what Google uses. Google moved to mobile-first indexing several years ago, meaning the mobile version of your site is what gets crawled and ranked. Focus on mobile.
Does image optimization actually make a big difference?
Usually, yes. Images are the single largest contributor to page weight on most sites. Moving from uncompressed JPEGs to compressed WebP typically cuts page weight by 60-80% for image-heavy pages. That directly improves LCP.
How often should I check my Core Web Vitals?
Check after any significant change to your site (new theme, major plugin update, new page template). For active sites, a monthly check catches regressions before they compound. PageSpeed Insights is free.
Can a cheap WordPress host cause bad Core Web Vitals?
Shared hosting with throttled CPU can slow time to first byte (TTFB) which indirectly affects LCP. But most CWV problems on Indian WordPress sites are content and plugin issues, not hosting. Fix images and JavaScript first, then evaluate hosting.
If you want your Core Web Vitals diagnosed without having to understand all of this yourself, we do technical website audits. We'll tell you what's failing and how to fix it.