Core Web Vitals Explained: What LCP, CLS and INP Mean for Your Rankings

Why page speed became a ranking factor

In 2021 Google introduced Core Web Vitals — three measurements of the real experience a visitor has on your page. They were born from a simple observation: people abandon slow, janky websites, so Google decided to reward sites that load fast and feel solid.

The three metrics are LCP (how fast the main content appears), CLS (how stable the layout is) and INP (how quickly the page responds to taps and clicks). Together they describe whether your website feels instant or frustrating.

LCP — Largest Contentful Paint

LCP measures the time until the biggest element on the screen — usually a hero image, heading or product photo — becomes visible. A fast LCP is the difference between a customer seeing your offer and staring at a blank white screen.

• Target: under 2.5 seconds
• Compress and resize images before uploading; a 2 MB photo is the single most common cause of slow LCP
• Enable lazy loading so images below the fold wait until the visitor scrolls
• Preload your font and hero image so they download in parallel instead of one after another

CLS — Cumulative Layout Shift

CLS measures how much the page moves while it loads. When images pop in late, banners push content down, or fonts swap mid-read, you get layout shift — the classic case of going to tap a button and it jumping away. On a phone, those mistaps cost you enquiries.

• Target: under 0.1
• Reserve explicit width and height on every image and video
• Avoid injecting ads or banners into the middle of content; give them fixed space
• Use font-display: swap so text renders in a fallback font immediately instead of staying invisible
• Load web fonts only for the styles you actually use

INP — Interaction to Next Paint

INP replaced the old First Input Delay metric and measures how quickly your site reacts when a visitor taps a button, opens a menu or submits a form. It is the closest thing to a test of whether the site feels responsive on a phone.

• Target: under 200 milliseconds
• Break up large JavaScript files and load only what each page needs (code splitting)
• Defer heavy scripts so they do not block taps and clicks
• Keep third-party widgets such as chat bots and trackers to a minimum — each one adds work for the main thread

How Core Web Vitals affect your rankings

Google has confirmed Core Web Vitals are a ranking factor, but the truth is more nuanced. Passing the thresholds alone will not jump you to Page 1 — they act more like a quality gate that keeps slow, broken sites from ranking well against stronger competitors.

The bigger effect is direct: a fast site converts better. When two plumbers or two boutiques are equally relevant, the one that loads cleanly wins the tap. For a small business in Mumbai, fixing these metrics improves rankings and makes the phone ring more at the same time.

Fixing Core Web Vitals for Mumbai's mobile-first customers

In Mumbai, most of your traffic arrives on an Android phone over mobile data or public Wi-Fi, often on a mid-range device with limited RAM. A site that feels fine on a fast office connection can take ten seconds to load on 4G in a crowded local train. The fixes below are ordered by impact for real-world Indian mobile users.

• Compress images aggressively — convert to WebP and scale each one to the actual display width
• Enable lazy loading on everything below the first screen
• Minify and defer JavaScript and CSS, and deliver critical CSS inline so the first paint is instant
• Set up browser and server caching so repeat visitors load from the phone's cache
• Preload fonts and hero images, and keep only the font weights you need
• Test on a real mid-range Android device over 4G, not just on your laptop, and re-test after every major change