Core Web Vitals in plain English: why a fast site earns more enquiries

Speed is one of those topics where business owners are told a score matters without being told why. This guide explains Core Web Vitals in plain English, what the numbers mean, and which fixes tend to matter on a service business website in India, the UAE or the UK.

The short version: every page has a job, usually to move a visitor towards an enquiry. A slow or jumpy page gets in the way of that job.

01What are Core Web Vitals?

Core Web Vitals are three measurements Google uses to describe how a page feels to a real person: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability). They are measured from real Chrome users, and Google publishes a "good" threshold for each one.

Here they are without the jargon:

• Largest Contentful Paint (LCP): how long until the biggest thing on the screen, usually the hero image or headline, has appeared. Google's "good" threshold is 2.5 seconds or less.
• Interaction to Next Paint (INP): when someone taps a button or opens a menu, how long before the page visibly responds. Good is 200 milliseconds or less. INP replaced an older metric, First Input Delay, in March 2024.
• Cumulative Layout Shift (CLS): how much the page jumps around while loading, such as a button moving just as you tap it. Good is 0.1 or less.

Google assesses each at the 75th percentile of visits, so most of your visitors, not just the lucky ones on fast connections, need a good experience for the page to pass.

Fig. 01Stack

What each Core Web Vital measures

From the bottom layer up:

1. Loading: LCP: Main content visible within 2.5 seconds
2. Responsiveness: INP: Taps answered within 200 milliseconds
3. Stability: CLS: Layout shift score of 0.1 or less

02Why does a fast site earn more enquiries?

A fast, stable site earns more enquiries because fewer people give up before reaching the form. Every second of waiting, every unresponsive tap and every jumping button is a moment where a busy buyer can leave. Speed does not create demand, but it stops you wasting the demand you already have.

This is the part worth quoting to anyone who thinks speed is a developer vanity metric. Your marketing spend, your Google Business Profile, your referrals and your search rankings all exist to bring the right person to a page. Once they arrive, the page has seconds to show it is worth their time. If the main image takes several seconds to appear on mobile data, some visitors close the tab. If the menu ignores their first tap, some assume the site is broken. If the enquiry button shifts just as they press it, some land on the wrong page and give up. None of these people show up in your enquiry inbox, so the loss is invisible unless you measure it. Core Web Vitals are a way of making that invisible loss visible, and a fast site simply keeps more of the visitors you have already paid to attract.

03How do you check your Core Web Vitals?

Use Google's free tools: PageSpeed Insights for a single page and the Core Web Vitals report in Google Search Console for the whole site. Look first at the field data from real visitors, then use the lab data to find causes.

The two kinds of data are easy to confuse:

• Field data comes from the Chrome User Experience Report, gathered from real Chrome users over recent weeks. This is what Google's assessment uses. Smaller sites may not have enough traffic to show it for every page.
• Lab data is a simulated test run on demand. It changes from run to run and is best used to diagnose problems, not to judge success.

In Search Console, the Core Web Vitals report groups similar URLs, so one slow template can flag hundreds of pages at once. That is useful: fixing the template fixes all of them.

04What usually slows a business website down?

On most business sites, the causes are predictable: oversized images, too many third-party scripts, heavy page builders, web fonts loaded badly, and slow hosting. Each maps to a specific Core Web Vital, which makes the fix list straightforward once you know where to look.

Common culprits we find in a technical SEO audit:

1. Hero images and sliders. A full-width photo exported straight from a camera, or a slider loading five large images, is the most common cause of poor LCP.
2. Third-party scripts. Old analytics tags, heatmaps, chat widgets and social embeds all compete for the browser's attention and hurt INP.
3. Images and embeds without dimensions. When the browser does not know how tall something will be, content below it jumps when it loads, which hurts CLS.
4. Fonts. Several font families and weights, loaded late, cause both delay and shifting text.
5. Heavy themes and plugins. Multipurpose themes often load code for features the site never uses.
6. Hosting far from visitors. A server on another continent with no content delivery network adds delay to every request.

Fig. 02Checklist

Core Web Vitals fix list for a business site

• Resize and compress the hero image, serve a modern format
• Do not lazy load the main above-the-fold image
• Set width and height on every image and embed
• Remove scripts nobody uses any more
• Load chat widgets after the page is usable
• Limit web fonts to the weights you need
• Use a CDN close to your buyers

05Do Core Web Vitals matter differently in India, the UAE and the UK?

The thresholds are the same everywhere, but the conditions differ. Visitors in India and the UAE often arrive on a phone from a WhatsApp link, on mobile data that varies through the day. UK visitors also expect a site that works with assistive technology. Build for the slowest realistic visit, not your office connection.

A few practical points:

• India: many visitors browse on mid-range Android phones. A page that feels instant on a new laptop can feel sluggish on these devices, especially with heavy JavaScript.
• UAE and Dubai: bilingual sites often load two sets of fonts. Arabic web fonts can be large, so load only what each page needs.
• UK: speed and accessibility go together. A stable layout, readable text and responsive controls help everyone, including people using screen readers or keyboard navigation.

If you serve buyers in several countries, a content delivery network that caches pages near each market is usually worth having.

06Should you rebuild for speed or fix what you have?

Most speed problems can be fixed on the existing site: images, scripts and fonts rarely need a rebuild. Rebuild only when the platform itself is the bottleneck, such as a page builder that cannot produce lean pages, or a theme that cannot be updated.

We cover that decision in modernise or rebuild?. When we do build new, performance is planned rather than patched: server-rendered pages, images sized for each screen, and as little JavaScript as the page needs. That approach runs through our websites and platforms work, and you can see it on builds such as WurkSpaces, where an interactive floor model had to stay usable by keyboard as well as by touch.

One caution. A perfect score on a page that does not explain what you do will still lose enquiries. Speed carries the message; it does not replace it.

07How do you keep a site fast after launch?

Speed decays unless someone watches it. New tracking tags, large images uploaded by the team and extra plugins slowly undo the work. Check the Core Web Vitals report in Search Console monthly, set simple rules for uploads, and review every new script before it goes on the site.

A few habits keep a fast site fast:

• agree a maximum image size for anyone who edits the site, and resize before uploading,
• keep a short written list of every third-party script and why it is there,
• test new features on a phone before they go live, not just on a laptop,
• read the monthly Search Console report alongside your enquiry numbers.

We include these checks in the monthly notes we send after launch, because a site that was fast on day one is only useful if it stays fast.

08What to do next

Run your home page and your main service page through PageSpeed Insights on a phone setting. Note which of the three metrics fails in the field data, then check the list above for the likely cause. If Search Console shows a whole group of URLs failing, look for the shared template.

If you would rather have someone read the numbers with you, book a call. We will show you what your real visitors experience and which fixes are worth doing first.