Core Web Vitals for Indian Websites (2026): What to Fix First

Page speed feels like a technical detail until you watch a customer on a mid-range Android phone wait for a product page to stop jumping around. Google measures that experience with three Core Web Vitals, and they matter twice: they shape whether visitors stay, and they are part of the page experience signals Google's ranking systems consider.

This guide explains the three metrics in plain terms, the thresholds Google uses, how to see your own real-user numbers, and which fixes usually help Indian business websites most. We include our own site's field data as a reference point.

The Three Metrics and Their Thresholds

• Largest Contentful Paint (LCP) measures loading: how long until the largest image or text block in view has rendered. Good is 2.5 seconds or less; above 4 seconds is poor.
• Interaction to Next Paint (INP) measures responsiveness: how quickly the page visibly reacts after someone taps, clicks or types. Good is 200 milliseconds or less; above 500 milliseconds is poor. INP replaced First Input Delay (FID) as a Core Web Vital in 2024.
• Cumulative Layout Shift (CLS) measures visual stability: how much content moves unexpectedly while the page loads. Good is 0.1 or less; above 0.25 is poor.

Google assesses each metric at the 75th percentile of real page loads, separately for mobile and desktop. A page passes when at least three quarters of visits meet the "good" threshold, so a fast experience on your office broadband proves little if most customers browse on phones.

Field Data vs Lab Data

There are two kinds of measurement, and they answer different questions:

• Field data comes from real Chrome users, collected in the Chrome UX Report (CrUX) over a rolling 28-day window. This is what Search Console's Core Web Vitals report and the top of PageSpeed Insights show. It is the data that counts.
• Lab data comes from a single simulated load, such as Lighthouse in PageSpeed Insights. It is ideal for diagnosing and testing a fix, but one simulated phone on one network is not your audience.

Small sites may not have enough traffic for page-level field data; Search Console then groups similar pages, or only origin-level data is available.

Our own numbers, as a reference

For the 28 days to 13 October 2026, CrUX reported these figures for brainguru.in across all devices: LCP 1.56 seconds at the 75th percentile, with 90% of visits rated good, and CLS 0.00, with 98% of visits rated good. On phones alone, LCP was 1.83 seconds with 89% good. These are real-user figures for one site, shared to show what the report looks like, not a promise of what any other site will see.

What Usually Fixes LCP

• Optimise the hero image. The LCP element is often a large banner. Serve it in a modern format (WebP or AVIF), at the size it is displayed, and give it high fetch priority instead of lazy-loading it.
• Cut server response time. Time to First Byte is the floor under LCP. Caching, a CDN with a point of presence close to your users, and avoiding slow database calls on every request all help.
• Remove render-blocking resources. Large CSS files, web fonts and scripts in the page head delay everything. Load only what the first screen needs.
• Be careful with sliders and heavy page builders. Carousels and builder-generated markup often delay the largest element.

What Usually Fixes INP

• Reduce JavaScript. Each analytics tag, chat widget, pixel and plugin adds work the phone must do before it can respond. Audit third-party scripts and remove what nobody uses.
• Load non-essential widgets later. Chat bubbles, review widgets and maps can load after the page is interactive or when the user scrolls to them.
• Break up long tasks. Developers can split heavy work so the browser can respond to input between chunks.

What Usually Fixes CLS

• Give images and embeds dimensions. Width and height attributes, or a CSS aspect ratio, let the browser reserve space before the file arrives.
• Reserve space for banners, ads and cookie notices. Elements that push content down after it has rendered are the most common cause of layout shift.
• Load web fonts carefully. A large difference between fallback and web font sizes makes text jump when the font arrives.

Priorities for Indian Websites

Most visitors to Indian business sites arrive on mobile, often on mid-range Android devices and variable connections. That shifts the priorities:

1. Measure phone field data first; desktop results can hide a mobile problem.
2. Keep the first screen light: one optimised image, minimal fonts, no auto-playing video.
3. Be strict about third-party scripts. A WhatsApp widget, three tracking pixels and a chat plugin can cost more than the rest of the page combined. A simple WhatsApp click-to-chat link costs nothing in page weight.
4. Choose hosting and a CDN with strong performance for Indian users.

Speed problems also slow crawling: if a server responds slowly, Google crawls less, which can leave new pages waiting in the queue. In Search Console, that shows up as pages waiting under "Discovered - currently not indexed".

A Quick Pre-Launch Checklist

• Test the key templates (home, service, product, article, contact) in PageSpeed Insights on mobile and fix the largest opportunities first.
• Check that the hero image is not lazy-loaded and is served at the size it is displayed.
• Confirm every image, video and iframe has width and height or a reserved aspect ratio.
• List every third-party script with an owner and a reason; remove the rest.
• Test a form and a menu on a mid-range Android phone, not only a laptop.
• After launch, watch Search Console's Core Web Vitals report for the next four weeks as field data builds up.

How Much Does It Matter for Rankings?

Core Web Vitals are part of page experience, which Google's ranking systems consider, but relevance and helpful content come first. A fast page with weak content will not outrank a slower page that answers the question far better. Treat Core Web Vitals as a way to stop losing visitors you already earned, and as a tie-breaker, not a shortcut. Our SEO guide for Indian businesses covers the bigger picture.

Frequently Asked Questions

What are good Core Web Vitals scores?

Google rates a page good when, at the 75th percentile of real visits, Largest Contentful Paint is 2.5 seconds or less, Interaction to Next Paint is 200 milliseconds or less and Cumulative Layout Shift is 0.1 or less, measured separately for mobile and desktop.

Why is my PageSpeed Insights score different from Search Console?

The score at the top of the Lighthouse section is lab data from one simulated load. Search Console uses field data from real Chrome users over 28 days. Field data is what Google uses for Core Web Vitals, so treat the lab score as a diagnostic tool.

What replaced First Input Delay?

Interaction to Next Paint (INP) replaced First Input Delay as a Core Web Vital in 2024. INP looks at the responsiveness of interactions throughout the visit, not only the first one.

Do Core Web Vitals directly decide rankings?

They are one part of the page experience signals Google considers. Relevance and helpful content matter more, so good Core Web Vitals support rankings rather than guarantee them.

How long until fixes show in Search Console?

Field data uses a rolling 28-day window, so improvements appear gradually and can take up to about four weeks to be fully reflected after a fix goes live.

Where Brainguru Can Help

Our web development and UI/UX design teams build sites that are fast on real Indian phones, and our SEO services include Core Web Vitals diagnosis and fixes. Planning a new site? Estimate it with the free App & Website Cost Calculator, or get in touch on +91-8010010000.

Sources: web.dev, "Web Vitals"; Chrome UX Report data for brainguru.in, 16 September to 13 October 2026.