What Is Core Web Vitals? A Simple Guide for Mumbai Business Owners

If you've heard the phrase "Core Web Vitals" and had no idea what it means — you're not alone. Most Mumbai business owners I speak to have either never heard of it, or they've been told it matters but nobody explained why, or how to fix it. This post changes that.

Core Web Vitals are three specific measurements Google uses to score how good — or bad — the experience of using your website feels to a real visitor. They are baked into Google's ranking algorithm. A poor score quietly pushes your website down the search results. A good score is a ranking advantage your competitors may not have.

Let me break down exactly what each metric means, what score you need to aim for, how to check where you stand right now, and what to do if your numbers are bad.

What Are Core Web Vitals?

Core Web Vitals are three page experience signals that Google officially uses as ranking factors. They measure speed, interactivity, and visual stability — the three things that determine whether a visitor feels your website is fast and usable, or slow and frustrating.

The three metrics are:

• LCP — Largest Contentful Paint: How fast does the biggest visible element (usually your hero image or headline) load?
• INP — Interaction to Next Paint: How quickly does your page respond when a visitor taps a button or clicks a link?
• CLS — Cumulative Layout Shift: Does your page jump around as it loads, causing visitors to mis-tap or lose their place?

Google collects real-world data from Chrome users visiting your site (called field data) and evaluates your scores against defined thresholds. These aren't theoretical benchmarks — they're measured on actual visitors on actual devices and connections, including Indian 4G networks.

LCP — Largest Contentful Paint Explained

LCP measures the time from when a user first navigates to a page to when the largest visible content element is fully rendered. This is typically your main hero image, a large banner, or the primary heading block at the top of the page.

Think about this from a Mumbai buyer's perspective. They're on Jio 4G on a crowded local train. They tap your link from a Google search result. How long before they see anything useful? That's what LCP measures.

A slow LCP — anything over 4 seconds — means a visitor stares at a half-loaded page and bounces before they even know what you offer. For service businesses in Mumbai competing for local search traffic, this is a silent lead killer.

The biggest culprits behind slow LCP are:

• Unoptimised images (hero photos uploaded at 4MB, displayed at 400px)
• Slow web hosting (budget shared hosting from Indian providers)
• Render-blocking JavaScript and CSS loaded before the main content
• No CDN, so assets load from a server in Singapore or the US

Our website speed optimisation service addresses all of these systematically — from server configuration to image delivery pipelines — not just the obvious quick wins.

INP — Interaction to Next Paint Explained

INP replaced the older FID (First Input Delay) metric in March 2024. It measures the full responsiveness of a page throughout the entire visit — not just the first tap. Every time a visitor clicks a button, opens a dropdown, or submits a form, INP captures how long the page takes to visually respond.

A high INP score means your website feels sluggish and unresponsive. On a WordPress site loaded with plugins — a WooCommerce store, a booking plugin, a chat widget, a cookie banner, and a page builder — the browser's main thread is constantly busy. When a visitor taps "Add to Cart", the browser may take 500ms or more to respond. That's half a second of nothing. Users tap again. The page double-fires. Frustration sets in.

For Mumbai e-commerce sites and booking-based businesses (clinics, salons, consultants), INP directly affects how many visitors complete their intended action.

CLS — Cumulative Layout Shift Explained

CLS measures how much the page layout shifts unexpectedly during loading. You've experienced this: you're about to tap a button, and suddenly an image loads above it, shoving the button down — and you tap the wrong thing instead.

On mobile, layout shift is especially damaging. Indian users on 4G connections experience more layout shift because images and ads load asynchronously on slower connections. A CLS score above 0.25 is classified as poor by Google.

Common causes of CLS in Mumbai business websites:

• Images without defined width and height attributes
• Late-loading ads or pop-up banners that push content down
• Web fonts that swap in after the page renders (FOUT)
• Embeds (YouTube, Google Maps, social media) without reserved space

Core Web Vitals Thresholds: Good, Needs Improvement, Poor

Here's exactly what Google defines as good, acceptable, and poor for each metric:

To pass Core Web Vitals, your site needs to hit "Good" on all three metrics for at least 75% of real-world page loads. Google uses the 75th percentile — meaning 3 out of 4 visitors must have a good experience, not just the average visitor.

How to Check Your Core Web Vitals Score

The fastest way to check is Google PageSpeed Insights. Go to pagespeed.web.dev, enter your website URL, and run the analysis. You'll see two sets of data:

• Field Data (top section): Real measurements from actual Chrome users visiting your site. This is what Google uses for ranking. If you don't have enough traffic yet, this section will be empty.
• Lab Data (bottom section): Simulated measurements run on a controlled connection. Useful for diagnosing problems but not used directly for ranking.

Always check the Mobile tab first. Mobile scores are almost always lower than desktop, and Google uses mobile-first indexing — meaning your mobile experience is what counts for ranking.

If your mobile LCP is over 3 seconds, your site is failing in the eyes of both Google and your Mumbai customers browsing on 4G. A full website audit will identify exactly which elements are causing the delay and what fixing them will cost.

Why Core Web Vitals Matter for Google Ranking in India

Google confirmed Core Web Vitals as ranking factors in 2021. Since then, the Page Experience signal — which includes Core Web Vitals, HTTPS, mobile-friendliness, and no intrusive interstitials — has been part of how Google decides which sites rank above others for identical content.

In practice, this means: if two Mumbai law firm websites both have strong content and good backlinks, the one with better Core Web Vitals scores will rank higher. The one with a 6-second LCP and a CLS of 0.3 will be penalised.

For local businesses competing in Mumbai on keywords like "web designer in Mumbai", "clinic in Andheri", or "interior designer Bandra", the margin between ranking position 3 and position 7 can be a Core Web Vitals gap. Position 3 gets roughly 10% of clicks. Position 7 gets under 2%.

Beyond ranking, the user experience impact is real. A Jio 4G user on a crowded local train tapping your site on a mid-range Android phone — a Redmi Note or a Realme device — is the median Indian internet user. If your site takes 5 seconds to load and shifts layout while they're trying to read, they leave. They don't come back.

Next.js vs WordPress: Core Web Vitals in Practice

One of the most consistent patterns I've seen across the hundreds of websites we've audited is the performance gap between Next.js sites and standard WordPress sites. It's not subtle.

Here's what typical scores look like for a comparable content-driven business website:

Why is Next.js so much faster? Several architectural reasons:

• Static site generation (SSG): Pages are pre-built at deploy time, not generated on each request. No PHP execution delay.
• Image optimisation built in: Next.js automatically serves WebP/AVIF formats, correctly sized for the device, with lazy loading — zero developer effort required.
• Code splitting: Only the JavaScript needed for the current page loads. WordPress typically loads plugin scripts across every page.
• Edge delivery: Next.js apps deploy to global CDN edge networks (Vercel, Cloudflare Pages). Visitors in Mumbai get assets served from nearby edge nodes, not a distant server.

WordPress can be optimised to pass Core Web Vitals — but it requires significant plugin management, caching configuration, and ongoing maintenance. A well-built Next.js website passes Core Web Vitals by default, with less effort and more consistent results.

Practical Steps to Improve Each Core Web Vitals Metric

Improving LCP

• Compress and resize your hero image. A 1,200px-wide WebP image at under 100KB is the target. Tools: Squoosh.app, TinyPNG.
• Add a CDN. Cloudflare's free plan works for most Mumbai business sites and dramatically reduces response times.
• Switch to faster hosting. Managed hosting on a server in India (Mumbai AWS, Google Cloud Mumbai) vs shared hosting on international servers makes a measurable difference.
• Preload your LCP image using <link rel="preload"> in the HTML head so the browser fetches it as a priority.
• Defer non-critical JavaScript that blocks the main thread before your content loads.

Improving INP

• Audit and remove unused plugins on WordPress sites. Each plugin adds JavaScript that competes for the browser's main thread.
• Defer third-party scripts (live chat, analytics, ad pixels) so they don't block interactivity during the critical first 3 seconds.
• Break up long JavaScript tasks. Any task over 50ms is considered "long" and can cause INP to spike.
• Use a lightweight theme or move to a framework like Next.js that ships minimal JavaScript by default.

Improving CLS

• Always define width and height attributes on every <img> tag. This lets the browser reserve space before the image loads.
• Reserve space for ads, banners, and dynamic content using CSS min-height or fixed-height containers.
• Use font-display: swap carefully — or preload your web fonts so they're available before first render.
• Test on a throttled 4G connection in Chrome DevTools to reproduce what Indian mobile users actually experience.

Frequently Asked Questions

Do Core Web Vitals affect my Google ranking in India?

Yes. Google uses Core Web Vitals as part of its Page Experience ranking signal globally, including for Indian search results. If two websites rank similarly on content and backlinks, the one with better Core Web Vitals scores will typically rank higher. For competitive local keywords in Mumbai — services, clinics, agencies, retailers — this can be the difference between page 1 and page 2.

My PageSpeed score is 45 on mobile. How bad is that?

A score of 45 is in the poor range. It almost certainly means your LCP is above 4 seconds and your INP is high, meaning your site loads slowly and feels sluggish on mobile devices. In practical terms, a significant portion of your mobile visitors are leaving before the page finishes loading. For a Mumbai business website getting 500 visitors a month, a score of 45 versus 85 can be the difference between 5 enquiries and 20 enquiries per month.

Can I improve Core Web Vitals without rebuilding my website?

Yes, often significant improvements are possible without a full rebuild. Image optimisation, adding a CDN, deactivating unused plugins, configuring caching, and deferring non-critical scripts can push a WordPress site from failing to passing Core Web Vitals. However, if your site is built on a heavy page builder (Elementor, Divi) or your theme ships excessive JavaScript, there's a ceiling on how much you can optimise without changing the tech stack.

How long does it take for Core Web Vitals improvements to affect my Google ranking?

Google collects Core Web Vitals field data over a rolling 28-day window. After you make improvements, it takes roughly 28 days for the improved scores to fully reflect in Google Search Console and influence your ranking. For brand-new sites without field data, Google falls back to lab data (PageSpeed Insights scores) to estimate page experience quality.

Is a Next.js website really worth the switch from WordPress just for Core Web Vitals?

Core Web Vitals alone may not justify a platform migration, but when you combine the performance benefits with better security, lower maintenance overhead, superior mobile experience, and the development velocity of the Next.js ecosystem, the case becomes strong for most Mumbai service businesses. For e-commerce or high-traffic informational sites, the SEO and conversion gains from a Next.js rebuild typically pay back the migration cost within 6–12 months.