BUILDGIN
Request an audit

Buildgin / Resources / Writing

Performance · 4 August 2026 · 8 min read

Core Web Vitals, translated out of the jargon

Three numbers, three plain meanings. How fast the main thing appears, whether the page jumps around, and whether it responds when tapped.

Core Web Vitals is Google’s name for three measurements of whether a page is pleasant to use. They feed into rankings, though not as heavily as some agencies claim. They matter more because they measure something real.

Here’s each one without the acronym soup.

How fast the main thing appears

The formal name is Largest Contentful Paint. It measures how long until the biggest element on screen has loaded. Usually that’s your hero image or your main heading.

Google wants this under 2.5 seconds. On the dated Indian sites we audit, it’s regularly 8 to 12 seconds on a real 4G connection. The cause is almost always uncompressed images. A single 4MB photograph in the hero will do it on its own.

We build to under 2 seconds on a 6 Mbps connection. That’s a realistic throughput for 4G in a tier two city. Advertised speeds are a different number.

Whether the page jumps around

Cumulative Layout Shift. You’ve experienced this. You go to tap a link, an advert or an image finishes loading above it, everything shifts down, and you tap the wrong thing.

It happens when images don’t have their dimensions declared in the code. The browser doesn’t know how much room to reserve, so it reserves none, then shoves everything aside when the image arrives. The fix is one line per image.

Whether it responds when tapped

Interaction to Next Paint. How long between a tap and something visibly happening. Under 200 milliseconds is the target.

This one is usually a script problem. Too much JavaScript loading at once, often from tracking tags and chat widgets that got added over the years and never removed. We’ve found sites running four separate analytics tools, three of them installed by vendors who left.

Every widget somebody added in 2017 is still loading on every page, for every visitor, forever.

How to test yours

PageSpeed Insights is free and takes thirty seconds. Paste in your URL. It gives you a lab score and, more usefully, field data from real Chrome users if your site has enough traffic.

Look at the mobile tab, not desktop. Google ranks using the mobile version of your site. Your buyers are on phones. A site that scores 90 on desktop and 28 on mobile is a mobile problem, and desktop score is close to irrelevant, because Google uses mobile first indexing.

What a realistic target is

Perfect scores aren’t the point and chasing 100 wastes money. Passing all three thresholds is the point. Most dated sites can get there with three changes: compress the images, declare image dimensions, and remove the scripts nobody uses.

That’s usually a week of work, and it’s the cheapest meaningful improvement available to most businesses. It’s also verifiable, which matters. You can check the result yourself in a browser rather than taking a vendor’s word for it.

Written by Sameer Gaikwad, founder of Buildgin. Thirty three years in electrical power systems across global MNCs, now applying the same condition monitoring habit to websites.

Five working days. Findings either way.

Request an audit