Core Web Vitals Explained
for Indian Business Owners
(Not Developers)
Core Web Vitals are three specific measurements Google uses to evaluate the real experience visitors have on your website - and they directly affect your Google search rankings. The three metrics are LCP (how fast the main content loads), INP (how quickly the page responds when a visitor taps or clicks), and CLS (whether content moves around while the page is loading, causing visitors to accidentally tap the wrong thing). Google requires 75% of your real visitors to have a "good" score on all three metrics for your pages to pass Core Web Vitals. For Indian businesses, these metrics matter more than the generic guides explain, because the 75% measurement threshold is based on real visitor data from real Indian devices - budget Android phones on real 4G connections - not the ideal conditions a PageSpeed lab test uses. A Chennai business website that scores 85 on PageSpeed Insights may still be failing Core Web Vitals in Google's actual data if the 25% of visitors on slower devices and weaker connections are having poor experiences. This guide explains each metric in plain language, with India-specific examples of what causes failures on Indian business websites and what to ask your developer to fix.
What This Guide Covers
- What Core Web Vitals actually are in plain language - not developer terminology
- The lab data vs field data difference - why your PageSpeed score can look good while you are failing in Google's real data
- LCP (Largest Contentful Paint) - what it measures, what the thresholds are, and the most common causes of LCP failures on Indian business websites
- INP (Interaction to Next Paint) - what replaced FID in March 2024, and why Indian websites with WhatsApp plugins and popups are specifically at risk
- CLS (Cumulative Layout Shift) - why content jumps on Indian business websites and the India-specific causes most guides miss
- How to check your own Core Web Vitals for free - step by step, no technical knowledge needed
- The Rs 25,000 problem - the real rupee cost of failing CWV that no other guide calculates
- What to tell your developer - the specific fixes for Indian WordPress websites, in plain language
Why Core Web Vitals Hit Indian Businesses Harder Than Generic Guides Explain
Every article about Core Web Vitals covers the same three metrics and the same thresholds. What they do not cover is why Indian business websites fail Core Web Vitals at higher rates than Western websites, why a good PageSpeed score does not mean you are passing Core Web Vitals in Google's actual data, and why the specific design patterns that are most common on Indian websites - sliders, WhatsApp plugins, rotating banners, Google Fonts loaded without optimisation - are precisely the patterns that cause Core Web Vitals failures.
As a website development company in Chennai that audits websites before every SEO and paid advertising campaign, BYB Traction consistently finds that more than 70% of existing Chennai business websites fail at least one Core Web Vital in Google's field data - even when the same website scores 70 or above in a PageSpeed lab test.
Core Web Vitals are measured from real user data on real devices visiting your actual website - not from a lab test on a fast computer. Google calls this Chrome User Experience Report (CrUX) data. If 25% of your visitors are experiencing poor loading or responsiveness - because they are on a budget Redmi phone on a congested 4G connection in Chennai - your website fails Core Web Vitals regardless of what your PageSpeed score says. The 75th percentile rule means your worst 25% of user experiences determine whether you pass or fail. For Indian businesses with predominantly mobile Indian visitors, this makes Core Web Vitals significantly harder to pass than the same test on a UK or US website where visitors typically use faster devices and connections.
Lab Data vs Field Data: The Confusion That Makes Indian Business Owners Think They Have Fixed a Problem They Have Not Fixed
The single most common misunderstanding about Core Web Vitals in India is the difference between lab data and field data. This confusion leads business owners to believe their website is performing well when it is actually failing in Google's ranking assessment. Understanding this difference requires no technical knowledge - it is a straightforward concept that takes two minutes to explain.
Lab data is what PageSpeed Insights (pagespeed.web.dev) measures when you type in your URL and click Analyse. It loads your website on Google's test server, on a simulated "Average Mobile" device, on a simulated slow 4G connection (1.6 Mbps), at a fixed time of day with no traffic variation. This is a controlled experiment in ideal conditions that produces a consistent score you can use to track improvements. It is genuinely useful. But it does not represent the experience of a real Indian visitor on a real Indian device visiting your real website.
Field data is what Google actually collects from real Chrome browser users visiting your website over the previous 28 days. When a visitor in Chennai uses Chrome on their Redmi phone to open your website, Chrome silently measures their actual LCP, INP, and CLS and sends this data to Google. Google aggregates thousands of these real measurements into the CrUX dataset. Core Web Vitals rankings are based on this field data, not on the lab data from PageSpeed Insights.
A Chennai service business website might have most visitors on modern phones with good connections - these contribute good field data. But 25% of visitors might be on older Android phones with slower CPUs and congested 4G. Those 25% experience significantly longer load times, slower tap responses, and more layout instability. Because Google measures at the 75th percentile, those 25% of poor experiences determine whether the website passes or fails. This is why Indian websites specifically struggle with the 75th percentile threshold - the variance in device quality and network speed among Indian visitors is much wider than in Western markets.
In practical terms: if your PageSpeed lab score is 78 and you are wondering why your Core Web Vitals report in Google Search Console still shows failures - this is why. The lab score and the Core Web Vitals pass/fail are measuring different things on different data sources. You need to look at field data to know your actual CWV status. The good news is that both are visible for free, and this guide shows you exactly where to find each.
LCP: Largest Contentful Paint - How Fast Does Your Page Load for Indian Visitors?
What it means in plain language: LCP measures the time from when a visitor clicks your link or types your URL to when the main visible content of your page - usually the hero image or the main heading - appears on their screen. If you have ever visited a website where the page feels blank for a few seconds before anything appears, you experienced a poor LCP. Google measures this for every visitor using Chrome across all your pages. The 2.5-second threshold is based on the point at which users start to reliably abandon a page.
Why Indian business websites fail LCP at higher rates:
- Uncompressed hero images: The most common cause. A Chennai business owner or their designer uploads a hero image directly from a camera or stock site at 3 to 5 MB. On a real Indian 4G connection at typical peak-hour speed (5 to 8 Mbps actual throughput), a 3MB image takes 3 to 5 seconds to load before any content is visible. Converting this image to WebP format and compressing it to under 200KB typically reduces LCP by 2 to 4 seconds in one change.
- Rotating slider heroes: As covered in BYB Traction's guide to homepage layout mistakes, sliders load 3 to 5 full hero images when the page opens - all of them before the first slide completes. This multiplies the image load problem. Sliders are the most common single cause of LCP failure on Indian business websites.
- Google Fonts loaded without preconnect: Most Indian WordPress websites load Google Fonts from Google's servers. Without a preconnect directive in the page header, the browser discovers the font load requirement late in the render process, delaying text rendering. This can add 0.5 to 1.5 seconds to LCP.
- Indian shared hosting with slow TTFB: Time to First Byte (TTFB) is how long the server takes to start sending the page. Budget Indian hosting providers (Hostgator India, BigRock) on shared hosting can have TTFB of 800ms to 2000ms. A caching plugin like LiteSpeed Cache (free for LiteSpeed hosting) typically reduces TTFB to under 300ms. If your server itself is slow, no amount of image compression fully fixes LCP.
- No CDN: A Content Delivery Network serves your website's files from a server geographically close to the visitor. Cloudflare free tier serves Indian visitors from Cloudflare's Mumbai or Chennai edge nodes rather than your hosting server location - typically reducing load time by 0.5 to 1.5 seconds for Indian users without any code change.
What to ask your developer to fix for LCP: "Please compress all images on the website to WebP format under 200KB, configure lazy loading for images below the first screen, add a preconnect directive for Google Fonts, verify LiteSpeed Cache or WP Rocket is configured, and set up Cloudflare free tier if it is not already active."
INP: Interaction to Next Paint - Is Your Website Responding When Indian Visitors Tap It?
What it means in plain language: INP measures how long it takes for your page to visually respond after a visitor interacts with it. When an Indian visitor on a Redmi phone taps your "WhatsApp Us" button or taps a navigation menu item, INP measures the time from that tap to when the page visually changes to show the response. If you have ever tapped a button on a mobile website and nothing happened visually for what felt like a long time before the page responded, you experienced a poor INP. Google measures this throughout the entire session - not just on the first tap - across all interactions the visitor makes on the page.
The India-specific INP problem - plugins that load JavaScript:
INP failures are almost always caused by too much JavaScript executing on the device's processor. Budget Android phones have processors that are 3 to 5 times slower at executing JavaScript than a laptop or premium phone. What executes in 50ms on a developer's MacBook might take 300ms on a Redmi phone - causing an INP failure. The Indian business website patterns that consistently cause INP failures:
- WhatsApp chat plugins: Third-party WhatsApp plugins load 200 to 600ms of JavaScript. On a budget Android phone this JavaScript competes with everything else the page is doing, slowing tap responses across the entire page. The fix is to use a native WhatsApp anchor link (href="https://wa.me/91...") with no plugin - identical functionality, zero JavaScript overhead.
- Popup and lead capture plugins: Plugins that display exit-intent popups or time-delayed popups run JavaScript continuously monitoring mouse movement and scroll position. This constant JavaScript activity blocks the browser's main thread, making every other interaction on the page slower.
- Live chat widgets: Tawk.to, Freshchat, Intercom, and similar chat widgets load substantial external JavaScript. On Indian mobile devices this is a consistent INP failure contributor. If you are not actively managing chat enquiries in real-time, the performance cost of a live chat plugin exceeds its conversion benefit.
- Multiple tracking pixels: Meta Pixel, Google Ads conversion tracking, and additional analytics tags each load JavaScript. Three tracking scripts each adding 50ms of main thread work create 150ms of additional INP latency before the visitor's tap can be processed.
What to ask your developer to fix for INP: "Please audit every JavaScript plugin on the website and remove any that are not essential. Replace the WhatsApp plugin with a native anchor link. Defer all non-critical JavaScript so it loads after the page is interactive. Check whether the live chat widget is necessary and remove it if it is not being actively used."
CLS: Cumulative Layout Shift - Why Does Content Jump Around on Your Website?
What it means in plain language: CLS measures how much the visible content of your page moves around while it loads. If you have ever tried to tap a button on a mobile website and the button moved just as you were tapping it - causing you to accidentally tap something else - that is a CLS event. Google measures the total amount of unexpected layout movement on your page. A score of 0 means nothing moved. A score of 0.25 means significant visible content shifted, which is bad enough to cause poor user experiences. The key word is "unexpected" - a page that smoothly reveals new content as the user scrolls does not cause CLS. Content that jumps because an element loaded late does.
The most common CLS causes on Indian business websites:
- Images without declared dimensions: When an image does not have its width and height specified in the HTML, the browser does not reserve space for it while the page loads. When the image finally downloads, it pushes all the content below it down the page. This is the most common cause of CLS on Indian WordPress websites - images uploaded through page builders like Elementor often lack explicit dimension declarations.
- Rotating sliders and carousels: As the slider JavaScript initialises and slides load, the slider container changes size. Everything below the slider shifts down. This is why sliders cause both LCP failures (loading multiple images) and CLS failures (layout shifting as the slider initialises). They fail two Core Web Vitals simultaneously.
- Google Ads loading dynamically: If your website shows Google AdSense advertisements, these ads load after the rest of the page and push surrounding content to accommodate their dimensions. Every time an ad loads in a position the browser had not reserved space for, it creates a CLS event. This is particularly significant for blogs and news websites that use AdSense.
- Fonts loading and causing text reflow: When a page loads with a fallback system font and then switches to the downloaded Google Font, the text reflows because the two fonts have different character widths. This makes headings and body text shift position, sometimes pushing entire sections of the page down or up. Setting font-display:swap in the font loading CSS reduces this shift.
- WhatsApp floating button appearing after load: A floating WhatsApp button that appears at the bottom-right corner of the page a second after the page loads technically contributes to CLS if it overlaps or displaces any page content. Using a native link styled as part of the page structure rather than a plugin-injected floating element eliminates this contribution.
- Dynamic content in Elementor widgets: Elementor's dynamic content features - testimonial sliders, post grids, and animated counters - often inject content that shifts surrounding layout. This is particularly common on Indian business homepages built with Elementor that have animation effects enabled on mobile.
What to ask your developer to fix for CLS: "Please ensure all images have width and height attributes declared in the HTML code. Replace any sliders with static layouts. Check for Google AdSense and add reserved space containers around any ad slots. Add font-display:swap to all Google Fonts loading code. Check whether Elementor animations are causing layout shifts on mobile and disable them."
How to Check Your Core Web Vitals Right Now - No Technical Knowledge Needed
There are two places to check your Core Web Vitals. They measure different things (lab data versus field data) and both are free. You should check both.
Method 1: PageSpeed Insights for lab data (pagespeed.web.dev)
Go to pagespeed.web.dev. Type your website's full URL (https://yourdomain.com) and click Analyse. Select the Mobile tab (not Desktop - Google ranks based on mobile). You will see a score from 0 to 100 and individual metric readings. The Core Web Vitals section shows LCP, INP, and CLS readings. Look at the Field Data section at the top of the results first - this shows real user data if your website has enough Chrome visitors. If it says "The Chrome User Experience Report does not have sufficient real-world speed data for this page" it means your website is too new or does not have enough Indian Chrome users yet for Google to have field data. In this case, the lab data below is the best proxy you have.
Method 2: Google Search Console Core Web Vitals report for real user data
Log in to your Google Search Console account (search.google.com/search-console). In the left menu, scroll down to "Experience" and click "Core Web Vitals." This shows you the aggregate CWV status for your entire website based on real user data over the past 28 days. Pages are categorised as Good, Needs Improvement, or Poor. Click on any Poor or Needs Improvement category to see which specific pages are affected and which metric they are failing. This is the most actionable report - it tells you exactly which pages to prioritise fixing.
If your website shows "insufficient field data" in PageSpeed Insights or shows no URLs in the Search Console CWV report, it means Google has not collected enough real Chrome visitor data from your website yet to report on. This typically happens for websites that are under 6 months old or that receive fewer than roughly 1,000 monthly Chrome visits. It does not mean your website is passing - it means Google has not measured it yet. Continue improving your lab scores using PageSpeed Insights while building traffic. Once sufficient visitors have been measured, your field data will appear.
The Real Rupee Cost of Failing Core Web Vitals for a Chennai Business
Every discussion of Core Web Vitals focuses on Google rankings. The conversion rate impact - and its direct rupee cost - is equally significant and less discussed.
| Failing Metric | Direct User Impact | Business Cost | India-Specific Factor |
|---|---|---|---|
| LCP over 4 seconds | 53% of mobile visitors abandon before content appears | Half your paid advertising clicks leave before seeing what you offer. At Rs 50/click: Rs 25,000 wasted per month on 500 abandoned visits | Indian 4G peak-hour throttling makes LCP failures worse in the evening when buyer intent is highest |
| INP over 500ms | Taps feel broken. Visitors think the button didn't register and tap again, or leave frustrated | Form submissions fail to register. WhatsApp link taps appear unresponsive. Direct enquiry conversion rate drops | Budget Android CPUs are 3-5x slower at JavaScript execution - a 200ms INP on a developer's laptop can become 500ms on a Rs 8,000 Redmi phone |
| CLS over 0.25 | Visitors tap the wrong element as content shifts - frustrating the majority and preventing intended actions | Form submits when visitor meant to type. Phone number calls when visitor meant to scroll. Direct interface failures reduce contact rate | Sliders (most common on Indian websites) cause both CLS and LCP failures simultaneously - the highest-impact single fix available |
| All 3 failing | Google demotes page in search results | Organic ranking loss means less traffic, meaning all ad-generated traffic carries full cost with no organic offset. Compounding revenue impact over 6-12 months | KD 31-50 keywords in Chennai are fought for by 5-10 agencies. 2-3 position drop from CWV failures can move a result from page 1 to page 2 where click rates are 90% lower |
How BYB Traction Targets Core Web Vitals on Every Website We Build
As a digital marketing agency in Chennai that runs Google Ads and SEO on the websites we build, CWV failures directly increase our clients' cost per click (Google Ads Quality Score is partly based on landing page experience) and suppress the organic rankings we are building through content. Every website BYB Traction builds targets 80 or above on mobile PageSpeed as a minimum handover standard and includes Cloudflare, LiteSpeed Cache or WP Rocket, Smush WebP compression, deferred JavaScript, and no WhatsApp plugins. These configurations address all three Core Web Vitals simultaneously.
For existing websites where CWV failures are identified in Google Search Console, our website SEO services in Chennai include a technical performance audit and implementation of fixes as the first phase of every campaign. Improving CWV before starting any content campaign produces faster ranking improvements because Google sees both improved content and improved experience signals simultaneously.
CWV-optimised from day one
- WebP image compression on all assets
- LiteSpeed Cache or WP Rocket configured
- No sliders - static hero layouts only
- Native WhatsApp link (no JS plugin)
- Google Fonts preconnect + font-display:swap
- Target: 80+ mobile PageSpeed
85+ mobile PageSpeed + CWV audit
- All Startup CWV optimisations
- Cloudflare CDN setup for India edge
- JavaScript defer and plugin audit
- Critical CSS inlining for LCP
- Target: 85+ mobile PageSpeed
- 1 month SEO from our Growth Plan
Advanced CWV for high-traffic sites
- All Growth CWV optimisations
- Advanced INP optimisation for heavy pages
- eCommerce checkout CWV review
- Target: 90+ mobile PageSpeed
- 1 month SEO from our Premium Plan
Conclusion: Core Web Vitals Are a Business Metric, Not a Developer Metric
Core Web Vitals started as a technical performance measurement and have become a business performance measurement. LCP failures cost you 53% of your mobile visitors before they see your services. INP failures make your website feel broken on the devices your Indian visitors actually use. CLS failures cause visitors to accidentally tap the wrong element and leave frustrated. And failing any of them suppresses your Google rankings relative to competitors who pass them.
The fixes are not complicated. The three highest-impact changes for most Indian business websites - compressing hero images to WebP, removing the WhatsApp plugin and replacing with a native link, and removing or replacing slider heroes - can be done by any developer in a day and typically move all three Core Web Vitals scores from failing to passing simultaneously. The reason most Indian business websites still fail Core Web Vitals is not that the fixes are expensive or technical - it is that the business owners running them do not know which specific questions to ask their developers.
Now you do.
4th Floor, 4A, Rashmi Towers, Nungambakkam, Chennai 600034 · +91-9600448666 · contact@bybtraction.com · Mon to Fri 9AM to 6PM
Frequently Asked Questions
Core Web Vitals are three performance measurements Google uses to evaluate real user experience on your website: LCP (how fast the main content loads), INP (how quickly the page responds to taps and clicks), and CLS (how much content moves unexpectedly while loading). They matter because Google uses them as ranking signals - websites that pass Core Web Vitals rank better in competitive searches than equivalent websites that fail them. For Indian businesses, they also directly affect conversion rate: LCP failures cause 53% of mobile visitors to leave before seeing your content, and INP failures make the website feel broken on budget Android phones used by the majority of Indian website visitors.
PageSpeed Insights (pagespeed.web.dev) tests your website in controlled lab conditions using simulated devices and simulated network speeds. Core Web Vitals in Google Search Console are measured from real Chrome users on real devices visiting your actual website. These two data sources measure different things. If 25% of your real Indian visitors are on older Android phones with slower processors and congested 4G connections, their actual experience is significantly worse than the PageSpeed lab simulation. Google measures Core Web Vitals at the 75th percentile - meaning your worst 25% of user experiences determine whether you pass or fail. A 78 PageSpeed lab score can coexist with failing field data CWV if your real Indian users are having worse experiences than the lab simulation captures.
INP (Interaction to Next Paint) replaced FID (First Input Delay) as a Core Web Vital in March 2024. FID measured only the delay before the browser started processing the first interaction on a page. INP measures the full response time from any interaction (tap, click, or keystroke) throughout the entire page session to when the page visually shows a response. INP is a stricter, more comprehensive metric that captures the experience of slow responsiveness throughout a visit rather than only at the first tap. The threshold for INP is under 200 milliseconds for Good, compared to FID's 100 millisecond threshold. Any guide that refers to FID as a current Core Web Vital is outdated and can be disregarded.
For LCP: uncompressed hero images (2-5MB images that take 4-8 seconds to load on real Indian 4G connections) and rotating image sliders that load multiple large images simultaneously. For INP: too many JavaScript plugins, particularly WhatsApp chat plugins, live chat widgets, and popup plugins that keep JavaScript running continuously on budget Android phones. For CLS: images without declared dimensions that shift page content when they load, and rotating sliders that cause layout shifts as they initialise. The single highest-impact fix for most Indian business websites is removing sliders and replacing them with a single static hero image - this typically improves both LCP and CLS simultaneously.
Two free methods. First, go to pagespeed.web.dev, enter your website URL, and click the Mobile tab. Check the Field Data section at the top for real user measurements if available, then the lab data below. Second and more important, log in to Google Search Console (search.google.com/search-console), go to Experience in the left menu, and click Core Web Vitals. This shows your actual pass/fail status for real users across all your pages, with specific pages categorised as Good, Needs Improvement, or Poor. Click on any Poor or Needs Improvement category to see which specific pages are failing and which metric they are failing on.
Yes, in two ways. Google Ads Quality Score includes landing page experience as one of its three components (alongside expected CTR and ad relevance). A landing page that fails Core Web Vitals has a lower Quality Score, which increases your cost per click and decreases your ad position relative to competitors with the same bid. The second impact is direct: if 53% of visitors from your paid ads abandon the landing page due to slow LCP before seeing your offer, you are paying for those clicks with zero return. At Rs 50 per click and 500 abandoned visits per month, this represents Rs 25,000 in wasted ad spend per month for a moderate-size campaign. Fixing Core Web Vitals improves both organic rankings and paid advertising efficiency simultaneously.
PageSpeed lab scores improve immediately after fixes are deployed - you can verify the improvement by re-running the test within minutes. Field data in Google Search Console is based on a 28-day rolling window of real user data. This means even after you fix all Core Web Vitals issues, the GSC report will continue showing failures for up to 28 days while the old data ages out and new good data replaces it. After 28 days of consistent passing scores in field data, the GSC report should show improvement. The impact on Google rankings typically follows 2-6 weeks after the Core Web Vitals report shows Good status across your key pages.
Some fixes are possible without a developer through WordPress plugins. Installing LiteSpeed Cache (free) if your host uses LiteSpeed, installing Smush for image compression (free), and switching from a slider to a static hero section through your page builder can all improve Core Web Vitals scores without code changes. However, the deeper fixes - Critical CSS inlining, JavaScript deferral, setting image dimensions in HTML, and font-display:swap in Google Fonts loading code - require developer access. For most Chennai business websites, a developer can implement the full set of Core Web Vitals fixes in 4 to 8 hours of work, making it a cost-effective improvement with compounding SEO and conversion rate returns.
