Why Your Slow Website Is Costing You Leads: Core Web Vitals Explained For Business Owners
Google measures three things about how your site feels to visitors. Here is what they mean in plain language, how to check yours in two minutes, and which fixes are worth paying for.
Speed is not a technical nicety. Visitors on a phone in Dubai traffic or on a train in London decide within seconds whether to stay. Google folds that experience into rankings through Core Web Vitals. This guide explains the three measurements without jargon, shows you how to check your own site, and tells you which fixes are worth the money.
The three measurements
Largest Contentful Paint (LCP)
How long until the main content, usually the hero image or headline, is visible. Google wants this under 2.5 seconds. Slow LCP is almost always a large unoptimised image, slow hosting, or render-blocking scripts.
Interaction to Next Paint (INP)
How quickly the page responds when someone taps or clicks. Target under 200 milliseconds. Poor INP comes from too much JavaScript running on the main thread: chat widgets, tracking scripts, sliders and page builders are the usual suspects.
Cumulative Layout Shift (CLS)
How much the page jumps around while loading. You have felt this: you go to tap a button and an ad pushes it down. Target under 0.1. Causes are images without dimensions, late-loading fonts and injected banners.
Check yours in two minutes
Open Google's PageSpeed Insights, enter your URL and look at the top section, which shows real-visitor data if you have enough traffic. Then open Search Console and find the Core Web Vitals report to see which pages fail. Test on mobile; that is where most of your visitors are and where scores are worst.
Fixes that are worth paying for
- Image optimisation. Modern formats, correct sizes, lazy loading below the fold. This alone fixes most LCP problems.
- Better hosting. Shared hosting with slow server response times caps how fast your site can ever be. Time to first byte over 800 milliseconds is a hosting problem, not a code problem.
- Removing scripts you do not need. Audit every third-party tag. Each one costs performance; most were added by someone who left.
- Font loading. Self-host fonts, limit weights, and set a fallback so text does not jump.
- Caching and a CDN. Serve static assets from a location near your visitors. This matters if you serve the Gulf, the US and the UK from a single server.
Fixes that usually are not
Buying a "speed optimisation plugin" on top of a heavy page builder treats the symptom. Rebuilding an entire site because one score is orange is overkill. And chasing a perfect 100 in the lab score has little business value once you pass the thresholds; real visitor data is what Google uses.
Why it matters beyond Google
Faster pages convert better. Every large study of web performance finds the same thing: as load time goes up, form completions and purchases go down. A slow site also wastes advertising spend, because you pay for the click and lose the visitor before the page appears.
What we do
Performance is built into every site we deliver, not bolted on afterwards, and we audit existing sites before recommending anything. If your scores are red, a free audit will tell you what is causing it and what it would take to fix. Our technical SEO service covers the full set of fixes above.
