All articles
SEO 5 min read

Core Web Vitals when your customers are on 4G

Your site is fast on your laptop. Your customer is on a mid-range Android in a lift. Only one of those is the benchmark.

Media Puppies · · Updated

Core Web Vitals are a ranking factor, but that is the smaller reason to care. The larger one is that a slow page loses people before they see anything you paid to show them — and in India, the device and the connection make that far more punishing than most dashboards suggest.

What the three Core Web Vitals actually mean

  • LCP — how long until the biggest thing on screen appears. Usually your hero image or headline. Aim under 2.5 seconds.
  • INP — how quickly the page responds when someone taps. This is where cheap phones struggle, because it is about processing, not bandwidth.
  • CLS — how much the layout jumps while loading. The reason people tap the wrong button.

Why your score lies to you

Most people test on a laptop, on office wifi, with a warm cache. That is a lab score, and it flatters.

What matters is field data — real visitors on real devices. In Search Console, the Core Web Vitals report uses actual user data. If lab says 95 and field says poor, believe the field. Your customers are not using your laptop.

A mid-range Android on a patchy 4G connection is the real benchmark. Test there or you are testing nothing.

The fixes that matter most

1. The hero image

Almost always the largest element and almost always unoptimised. Compress it, serve it in a modern format, size it for the actual display size rather than uploading a 4000px original. This single fix resolves a large share of LCP failures.

2. Fonts

Each font family is a render-blocking request. Two families maximum. Preconnect to the font host and use a swap behaviour so text appears immediately rather than after the font arrives.

3. Third-party scripts

Analytics, chat widgets, heatmaps, pixels, review widgets. Each one costs time, and they are the main cause of poor INP on cheap phones. Audit what is in your head tag and remove what nobody reads. Load the rest after the page renders.

4. Reserve space for anything that loads late

Images without width and height, ads, embeds and banners that appear after load all shift the layout. Set explicit dimensions. This is the cheapest CLS fix available and it directly reduces mis-taps.

5. Do not lazy-load what is visible first

Lazy loading below-the-fold images is good. Lazy loading the hero image delays the one thing LCP measures.

What is usually not worth it

  • Chasing a perfect 100. Past a point you are optimising for a number, not a person.
  • Rebuilding the site for speed before trying compression and script removal. The cheap fixes usually get you there.
  • Obsessing over TTFB on a decent host. It is rarely the bottleneck compared with a 3MB hero image.

How to test honestly

  1. Search Console Core Web Vitals report — real users, real devices.
  2. PageSpeed Insights, reading the field data section first.
  3. An actual mid-range Android on mobile data, in a place with imperfect signal.

The third one takes two minutes and tells you more than either report. It is also the only test that shows you what a customer arriving from an ad actually experiences before deciding whether to wait.

Want us to check your site properly? Get a free audit.

Questions people ask

What are the three Core Web Vitals?

Largest Contentful Paint, which measures how long the main content takes to appear; Interaction to Next Paint, which measures how quickly the page responds when someone taps; and Cumulative Layout Shift, which measures how much the page jumps around while loading.

Why does my PageSpeed score differ from Search Console?

They measure different things. PageSpeed Insights runs a simulated test on a fixed device and connection; Search Console reports field data from real visitors over 28 days. The field data is the one Google uses, and on Indian traffic it is usually the harsher of the two.

Which fixes move the numbers most?

Serving properly sized and modern-format images, removing render-blocking scripts and unused third-party tags, and reserving space for anything that loads late — images, ads, embeds. Those three account for most of the gap on a typical site.

Do Core Web Vitals really affect rankings?

They are a genuine but small ranking factor, and they almost never outrank relevance. The stronger argument is commercial: a page that takes too long on a 4G connection loses visitors you have already paid to bring there.

Want this run on your account?

Two minutes. We'll tell you what's realistic — including if the answer is no.

Start a project

Keep reading

SEO

Community pages that actually rank in Dubai

SEO

Duplicate content: what actually causes it

SEO

Ecommerce SEO for Indian D2C: category pages do the work

Start a project