Skip to content

Websites

Website speed for Indian small businesses: Core Web Vitals on a phone and mobile data

Many people who find a small Indian business online do it on a phone, often on mobile data, often in a hurry. If the page stays blank, a visitor may go back and tap the next result. Google has a precise way of measuring that experience, called Core Web Vitals, and free tools that show your numbers. This guide explains them from Google’s own documentation, says how much they matter for search, and ends with a check you can run in half an hour without a developer.

What does a slow page look like to your customer?

Someone is standing at a bus stop in Hadapsar with a mid-range Android phone and two bars of signal. They search for a pest-control service, tap your ad, and wait. The header loads, then a blank space where a large photo will go. The photo is 3 MB because it came straight off a camera. While it loads, a chat bubble appears and pushes your phone number down the screen just as they reach for it. They tap the wrong thing, go back, and call the next business.

Nothing in that scene is unusual, and every part of it is measurable. Google groups those moments into three numbers.

What are Core Web Vitals?

Google’s Web Vitals guide defines three metrics and a “good” threshold for each. Interaction to Next Paint replaced First Input Delay as the responsiveness metric on 12 March 2024.

MetricWhat it measuresGoodPoor
Largest Contentful Paint (LCP)How long until the main content, usually the big image or headline, appears2.5 seconds or lessOver 4 seconds
Interaction to Next Paint (INP)How quickly the page reacts when someone taps or types200 milliseconds or lessOver 500 milliseconds
Cumulative Layout Shift (CLS)How much the page jumps around while loading0.1 or lessOver 0.25

The “poor” thresholds come from Google’s PageSpeed Insights documentation; anything between the two columns is rated Needs Improvement.

Two details matter more than the numbers. First, Google judges each one at the 75th percentile: “a good threshold to measure is the 75th percentile of page loads, segmented across mobile and desktop devices.” In plain terms, three out of four visits must be good, so a fast office laptop does not rescue a slow phone experience. Second, a page passes only if all three are good. The one exception, in PageSpeed Insights, helps small sites: if there is too little data for INP, the page passes when LCP and CLS are both good.

How much does speed affect Google ranking?

Some, and Google is careful not to say more. Its page experience documentation (last updated 22 September 2026) says: “Core Web Vitals are used by our ranking systems.” The same page adds that good scores do not guarantee “that your pages will rank at the top of Google Search results”, and that “trying to get a perfect score just for SEO reasons may not be the best use of your time.”

Our reading: speed will not lift a weak page above a strong one, but it can decide between two pages that answer the same question equally well. The bigger effect is on the people who already clicked. A paid click that bounces off a blank screen is money spent for nothing, and no ranking report will show it.

Why do the tools show different numbers?

Because there are two kinds of data. Google’s PageSpeed Insights documentation explains both.

  • Field data comes from real Chrome users who have opted in, collected in the Chrome UX Report (CrUX) over “the previous 28-day collection period.” Google’s CrUX documentation says this dataset “is used by Google Search to inform the page experience ranking factor.”
  • Lab data comes from Lighthouse, which loads the page once under set conditions. For mobile, it simulates a mid-range phone on a slowed-down mobile connection. It is good for finding causes, not for judging the experience. It also cannot reliably measure INP, because nobody taps the page during a standard test; it reports Total Blocking Time instead, which Google’s TBT guide calls “useful as an indicator of INP issues”.

When they disagree, trust the field data. Google’s guide to optimising LCP says: “If Lighthouse and CrUX disagree, then CrUX likely provides a more accurate picture of your user experience.” A green lab score of 95 next to a failing field result often means your real visitors have slower phones or connections than the test assumes, or that the page is slow to respond to taps, which the lab test does not measure.

Why does my site say “no data”?

Many small business sites see no field data at all. CrUX only includes pages and sites with enough visitors, and Google’s CrUX methodology says “An exact number is not disclosed”. Pages must also be publicly discoverable, so a page with noindex will not appear. Search Console’s Core Web Vitals report shows “No data available” when the property is new or there is too little CrUX data.

No data is not a problem in itself. It means you rely on the lab test and on testing with a real phone, which the check at the end of this guide covers.

Is the mobile network in India the problem?

Mobile is how India gets online. TRAI counted 1,107.68 million broadband subscriptions at the end of September 2026, of which 1,039.09 million were mobile wireless broadband connections, a figure that includes dongles and machine connections as well as phones (TRAI press release 140 of 2026). The TRAI release counts connections, not website speed, and we have not used anyone else’s average, because an average hides the customer in a basement shop or a crowded station.

The global data shows where phones struggle. HTTP Archive’s 2025 Web Almanac, which reads CrUX data for millions of sites, found 48 per cent of mobile websites had good Core Web Vitals in 2025 against 56 per cent on desktop, up from 44 per cent on mobile in 2024 and 32 per cent in 2021. Loading is the weak spot: 62 per cent of mobile pages had a good LCP, against 74 per cent on desktop, a gap the Almanac calls “consistent with the combined effects of slower networks and less capable devices on mobile.” We found no published India-only figure from a primary source.

So the network is part of it. But the network is not something you control. What you control is how much your page asks the phone to download and run before it shows anything.

What usually makes a small business site slow on a phone?

The big image at the top

On most pages the LCP element is an image: the 2025 Web Almanac found images were the LCP content on 76.0 per cent of mobile pages. On a small business site that is usually the hero image. Google’s LCP guide gives three rules for the image itself: “Never lazy-load your LCP image”; set fetchpriority="high" on the image “if you think it’s likely to be your page’s LCP element”, but on no more than one or two images; and reduce its file size (the guide points to serving the right image size, modern image formats and compression). Google notes that download time is often not the main delay for most sites. In our view, fix lazy-loading and priority first. A photo exported for a print brochure has no place at the top of a phone page.

If your site runs on WordPress 6.3 or later, part of this is automatic. The WordPress core team says it “automatically adds the fetchpriority attribute with a value of ‘high’ to the image it determines most likely to be the ‘LCP image’.” Page builders and sliders can still undo it, so check rather than assume.

The server and the redirects

Before anything appears, the phone waits for your server. Google’s LCP guide says “A high TTFB can make achieving a 2.5 second LCP challenging, or even impossible”, and names a common cause for ad traffic: “visitors arriving through multiple redirects, such as from advertisements or shortened links.” If your ads point to a short link that redirects to the old domain that redirects to the new one, fix that first. It costs nothing.

Scripts from other companies

Chat widgets, pop-up builders, review embeds, several tracking pixels and a tag manager loading all of them: each is small, together they are not. Google’s advice on third-party JavaScript is short: “Remove it if it doesn’t add clear value to your site. Optimize the loading process.” Its tag manager guidance warns against using a tag manager for “cookie notices, hero images, or site features”, because it delays them.

Heavy scripts are also a common cause of a poor INP: the phone is busy running someone else’s code when your customer taps “Call”. Keep the tracking you act on and remove the rest. Our guide to lead tracking with UTM tags, GA4 and a CRM covers what is worth measuring.

Things that jump

Layout shift comes from content that arrives late and pushes everything down. Google’s CLS guide says: “Always include width and height size attributes on your images and video elements”, and reserve space for embeds and banners before they load. A button that floats over the page without pushing other content does not cause a shift; a banner that slides in above the headline does.

A 30-minute check an owner can run

Do this on your home page and on the page that brings the most enquiries, usually a service page or an ad landing page. Write the numbers down with the date.

  1. Open PageSpeed Insights, paste the address and choose the Mobile tab. Read the top block, which shows what real users experienced. Note LCP, INP, CLS and whether the assessment passed.
  2. If it shows no data for the page, look for whole-site (origin) figures, and do not mistake them for the page’s own. If there are none, use the lab results below and re-check in a month as traffic grows.
  3. If you have Search Console, open the Core Web Vitals report for mobile and note which metric it flags on which group of pages.
  4. In the PageSpeed lab results, find which element is the LCP. If it is an image, check its file size and whether it is lazy-loaded. Note Total Blocking Time too: a high figure points to the heavy scripts that also hurt INP.
  5. Look at the server response time in the lab results. Then click your own ad or short link on a phone and count the redirects in the address bar.
  6. List every third-party script the report names: chat, pop-ups, pixels, embeds. Next to each, write what decision it has helped you make in the last three months. Remove the ones with nothing written.
  7. Load the page on an ordinary Android phone on mobile data, away from office Wi-Fi, and watch for anything that jumps or covers the phone number.
  8. After fixes, wait about four weeks and re-check the field data, which covers a rolling 28 days.

Fixing the hero image, the redirects and unused scripts is cheap, and worth doing before anyone talks about a redesign. If the template itself is heavy, that is a rebuild conversation, and one worth having with numbers in hand.

QUESTIONS

Common questions

What is a good Core Web Vitals score?

Google calls 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. All three must be good for the page to pass, except that PageSpeed Insights judges a page on LCP and CLS alone when it has too little INP data.

Do Core Web Vitals affect Google ranking?

Google says Core Web Vitals are used by its ranking systems, but that good scores do not guarantee top rankings and that chasing a perfect score for SEO alone may not be worth the time. It says it always seeks to show the most relevant content, even if the page experience is sub-par, but that where lots of helpful content is available, a great page experience can contribute to success.

Why does PageSpeed Insights show no data for my site?

Real-user data comes from the Chrome UX Report, which only includes pages and sites with enough visitors. Google does not disclose the minimum. If the page has too little data, PSI may show figures for the whole site instead. Until your site qualifies, use the lab results and test on a real phone.

Why is my mobile score worse than desktop?

Phones have less processing power and often slower connections. Google’s mobile lab test simulates a mid-tier phone on a mobile network, and real visitors on mobile data face the same limits. Large images and third-party scripts hurt more on a phone.

Does WordPress handle Core Web Vitals automatically?

Partly. Since version 6.3, WordPress adds a high fetch priority to the image it judges most likely to be the main one, and it has lazy-loaded images by default since 5.5. Themes, page builders and plugins can still slow a page, so test it.

REFERENCES

Sources and further reading

Each link was opened and checked on .

← All field notes