Core Web Vitals are three numbers Google collects from real visitors to your site. They are a genuine ranking input, but the better reason to care is simpler: they measure the three ways a page annoys people.
The three numbers
- LCP — how long until the main thing appearsUsually your hero image or headline. Aim under 2.5 seconds. Almost always broken by one oversized image, a slow server, or fonts and scripts loading before the content.
- INP — how quickly the page responds when tappedAim under 200 milliseconds. Broken by too much JavaScript running at once — typically chat widgets, pop-up builders and tag-manager scripts stacked on top of each other.
- CLS — how much the page jumps while loadingAim under 0.1. Broken by images without dimensions, banners injected above content, and fonts that swap and re-flow the text. This is the one visitors hate most and mention least.
How to check yours in five minutes
Open PageSpeed Insights and enter your URL. Read the top section — field data from real Chrome users — and largely ignore the score below it, which is a lab simulation and swings wildly. Then check Search Console's Core Web Vitals report, which shows the same data grouped across your whole site so you can see whether it is one page or a template.
Test the pages that matter: your homepage, your top-selling product or service page, and your contact page. On mobile. That is where the traffic and the revenue are.
The fixes that actually move the numbers
- Resize and re-encode imagesThe most common single fix, and often the only one needed. A 3 MB photo displayed 600 pixels wide is wasting nearly all of itself. Modern formats do the rest.
- Delete a third-party scriptCount the chat widget, the heatmap, the two analytics tools, the pop-up plugin and the review badge. Each costs response time on every visit. Most sites can drop half of them without noticing.
- Give images and embeds fixed dimensionsReserving the space stops the jump. It is a one-line change per image and it fixes most CLS.
- Stop fighting the platformIf a page is slow because of six plugins layered on a shared host, tuning will not save it. That is a rebuild conversation, and it is worth having honestly rather than billing for months of optimisation.
Frequently asked questions
Will fixing Core Web Vitals get me to the top of Google?
On its own, no. Speed is a tie-breaker, not a substitute for relevance — a fast page about the wrong thing still loses. Where it clearly pays is conversion: people abandon slow pages, and that costs you enquiries whatever your ranking.
My score is 95 on desktop and 40 on mobile. Which matters?
Mobile. Google indexes mobile-first, and for most Indian businesses the large majority of traffic is on a mid-range Android phone. Judge the site on the device your customers actually hold.
Do you fix Core Web Vitals on sites you did not build?
Yes, and we will tell you honestly which category yours is in: a few hours of image and script work, or a rebuild. Both are real answers, and quoting months of optimisation for a site that needs rebuilding helps nobody.
Want this applied to your project?
Send us what you have — even a rough note. You'll get a written scope, a fixed quote and a delivery date within one business day, with no obligation.
