A slow website rarely announces itself. The owner checks it on office Wi-Fi on a fast laptop, it looks fine, and nobody notices that a customer on a mid-range phone over 4G waits four seconds for the first screen and then taps a menu that doesn't respond. Those visitors don't complain. They leave, and the enquiry goes to whichever competitor's site responded first.
Google measures this experience with three numbers called Core Web Vitals. This guide explains what each one means in plain language, how to see your real scores, and the fixes that usually make the biggest difference for business websites, whether they run on WordPress, Shopify or a custom framework like Next.js.
The three numbers Google uses
According to Google's Web Vitals documentation, a page offers a good experience when, for at least three out of four visits:
- Largest Contentful Paint (LCP) is under 2.5 seconds. This is how long it takes for the main content, usually the hero image or headline, to appear.
- Interaction to Next Paint (INP) is under 200 milliseconds. This is how quickly the page visibly reacts when someone taps a button, opens a menu or types in a form.
- Cumulative Layout Shift (CLS) is under 0.1. This measures how much the page jumps around while it loads, the effect that makes you tap the wrong button because an image pushed everything down.
LCP is about loading, INP about responding and CLS about stability. A site can be fast to load and still fail INP, which is why "it loads quickly for me" is not the end of the conversation.
Check real visitors' data, not just a lab score
Tools like Lighthouse run a test on one device under fixed conditions. That is useful for debugging, but Google judges your site on field data: what real Chrome users experienced over the last 28 days. A green Lighthouse score on your laptop says very little about a customer in a tier-2 city on a budget Android phone.
Start with two free tools:
- Search Console's Core Web Vitals report groups your pages into good, needs improvement and poor, separately for mobile and desktop.
- PageSpeed Insights shows the field data for a single URL at the top, and a lab diagnosis with specific suggestions below it.
Look at mobile first. In India most traffic is mobile, and it is where the problems show. Then prioritise the pages that earn money: the home page, your main service or product pages, and the enquiry or checkout pages.
Fixing slow loading (LCP)
When the main content takes too long to appear, the cause is usually one of four things:
- Oversized images. A 3 MB hero photo straight from a camera or a stock site is the most common culprit. Resize images to the size they are shown at, use modern formats like WebP or AVIF, and make sure the hero image is not lazy-loaded (lazy-loading is right for images further down the page, but it delays the one you want first).
- Slow server response. Cheap shared hosting that takes a second or more to send the first byte puts you behind before anything else happens. Caching, a better host or a CDN usually fixes this.
- Render-blocking files. Large CSS and JavaScript files loaded in the page head make the browser wait before showing anything.
- Web fonts. Several font families and weights downloaded before text can show. Two weights of one family is usually enough.
Google's guide to optimising LCP breaks the time down into stages, which helps your developer see whether the delay is the server, the download or the rendering.
Fixing slow responses to taps and clicks (INP)
INP problems feel like a website that has frozen for a moment. The tap registers, but nothing visible happens for half a second, so the visitor taps again or gives up. The cause is almost always JavaScript keeping the browser busy.
The usual sources on business sites:
- Third-party scripts. Chat widgets, popups, heatmaps, multiple analytics tags and old pixels all compete for the same browser thread your buttons need. We regularly find tools on sites that nobody remembers adding. List every script, remove what you don't use, and load the rest after the page is interactive.
- Page-builder bloat. WordPress sites stacked with page-builder add-ons, sliders and animation libraries ship far more JavaScript than the page needs.
- Heavy interactive features. Ecommerce filters, mega menus and search-as-you-type boxes that redo a lot of work on every keystroke.
Google's INP guide explains how developers break long tasks into smaller pieces so the page can respond in between. Modern frameworks help here too. Next.js 16.3, for example, added what the Next.js team calls Instant Navigations: the next page's shell appears immediately after a click and the data fills in behind it, instead of the screen waiting on the server. It is a good example of a framework upgrade that improves how fast a site feels, but it only helps sites already built on that framework, and it won't fix a page weighed down by ten third-party scripts.
Fixing pages that jump around (CLS)
Layout shifts are the easiest of the three to fix once you know the causes:
- images and videos without a set width and height, so the page reflows when they arrive,
- cookie banners, offer bars or chat bubbles that push content down after loading instead of overlaying it,
- ads or embeds without reserved space,
- web fonts that load late and change the size of text.
Google's CLS guide lists these with fixes. For most sites, setting image dimensions and reserving space for banners solves the bulk of it.
Treat speed as a lead metric, not a technical score
Core Web Vitals are a ranking signal, but the bigger reason to care is conversion. A page that hesitates after a tap feels untrustworthy, and the effect is strongest on the actions you care about: the call button, the WhatsApp button and the enquiry form. Speed problems are one of the quieter reasons a good-looking website still isn't generating leads.
A simple test anyone can do: take a mid-range phone, switch to mobile data, open your site from a Google search, and try to send an enquiry. Note every pause you can feel. That list is a better brief for your developer than any score.
Enquiry-driven sites feel this most. One example on our work page is Airlink, an internet provider, where the website's job is subscriber lead generation. On a site like that, the enquiry form is the page that most needs to respond instantly.
A worked example
These figures are illustrative, not from a real business. A coaching institute gets 3,000 mobile visits a month from Google and ads, and 1.5% of them (45) send an enquiry. Its hero image is 2.8 MB, a chat widget and two unused tracking scripts load on every page, and the enquiry form's dropdown takes a moment to open.
After compressing the hero image, removing the unused scripts and delaying the chat widget until after the page is interactive, mobile LCP falls from about 4.5 to 2.2 seconds and the form responds immediately. If the enquiry rate rises to even 2%, that is 60 enquiries instead of 45 from the same traffic and the same ad spend. The work itself took a developer a day.
Keep it fast after the fix
Websites get slower over time because things get added and nothing gets removed. A few habits keep the gains:
- Check the Core Web Vitals report in Search Console once a month.
- Before adding any new plugin, widget or tag, ask what it costs in speed and whether it earns that cost.
- Resize and compress every image before upload, or use a plugin or image service that does it automatically.
- Retest your key pages on a real phone after every redesign or major update.
Keep the site lean, and it will keep passing, both Google's thresholds and the more important test of a customer who has a few seconds and a competitor one tap away.



