What are Core Web Vitals?
Core Web Vitals are three measurements Google uses to describe how a page feels to a real visitor: how fast the main content appears, how quickly it responds and how stable it is.
| Metric | What it measures | Good threshold | Common causes of a poor score |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How long until the biggest visible element, often a hero image or heading, has loaded | 2.5 seconds or less | Large images, slow server, render-blocking scripts and styles |
| INP (Interaction to Next Paint) | How quickly the page reacts after a tap, click or key press | 200 milliseconds or less | Heavy JavaScript, many third-party scripts, long tasks blocking the page |
| CLS (Cumulative Layout Shift) | How much the layout jumps around while loading | 0.1 or less | Images without set dimensions, late-loading fonts, adverts and banners inserted above content |
Thresholds come from Google's published guidance at web.dev/vitals. Check there for the current definitions, as they can be updated.
Does page speed really affect Google rankings?
Yes, but in proportion. Google has said that page experience, including Core Web Vitals, is one of many ranking signals, and that relevance and content quality come first. A fast page about the wrong topic will not outrank a slower page that answers the question properly.
Where speed matters is on the margin. When several pages are similarly relevant, the one that loads quickly and stays stable on a phone is in a stronger position. And a page that fails badly, taking many seconds to show anything, can hold back a site that is otherwise strong.
Speed also affects crawling indirectly. Slow servers can limit how many pages a search engine fetches, which matters mainly for large sites.
How does speed affect enquiries and sales?
Even if rankings were unaffected, speed would still matter, because people give up on slow pages. A visitor who taps a search result and sees a blank screen for too long goes back and tries the next result. You paid for the work to get that visit, and lost it.
That is true everywhere, but it shows most on mobile. In the UAE, many searches happen on phones moving between Wi-Fi and mobile data. In the United States, coverage varies between cities and rural areas. In India, mobile-first browsing is the norm and connection quality differs widely between cities and towns such as Bengaluru, Mangaluru and Udupi.
The practical lesson is to test on a mid-range phone with a normal connection, not on the developer's fast laptop. If the page feels slow there, it is slow for many of your customers.
How do you make a website faster? Fixes by area
Start with the fixes that affect the most pages and take the least effort. Images and scripts usually give the biggest gains.
| Area | Problem | Fix | Metric helped |
|---|---|---|---|
| Images | Oversized photos, old formats, no dimensions | Resize to the displayed size, use modern formats such as WebP, set width and height, lazy-load images below the fold | LCP, CLS |
| Hero content | Main image or heading loads late | Do not lazy-load the top image, preload it if needed and keep the above-the-fold area simple | LCP |
| JavaScript | Large bundles and unused code | Remove unused libraries, split code, defer non-essential scripts | INP, LCP |
| Third-party scripts | Chat widgets, trackers, embeds and fonts add weight | Remove what you do not use, load the rest late, review each tool's value | INP, LCP |
| CSS and fonts | Render-blocking styles and late font swaps | Inline critical styles, remove unused CSS, limit font files and use font-display settings | LCP, CLS |
| Hosting | Slow server response | Choose quality hosting with servers near your audience. See infrastructure and hosting | LCP |
| Caching and CDN | Files downloaded again on every visit | Set browser caching, compress text files, serve static files from a content delivery network | LCP |
| Layout stability | Banners and adverts push content down | Reserve space for dynamic elements before they load | CLS |
How do you measure and improve speed step by step?
Measure first, so you fix what is actually slow, and keep measuring after each change.
Check real-user data
Open the Core Web Vitals report in Google Search Console to see which groups of pages are poor on mobile. Set-up is included with every website we build.
Test key pages
Run the homepage and your top service pages through PageSpeed Insights and Lighthouse. Note the biggest items they flag.
Fix images and scripts first
These give the largest gains for the least effort on most business sites.
Review hosting and caching
If the server itself is slow, front-end fixes only go so far.
Re-test and monitor
Real-user data in Search Console updates over time, so allow for that. Re-check after new plugins, scripts or redesigns.
Is it better to build a fast site than to fix a slow one?
Usually yes. A site built simply, with optimised images, little script and sensible hosting, is fast by default. A site stacked with heavy themes, page builders and many plugins fights a constant battle.
That is why speed is planned into our builds rather than added at the end. Small business sites are often hand-built static HTML and CSS, and editable ones use Next.js with a headless CMS. See web development for how we approach this, how to build an SEO-friendly website for the full checklist, and our technical SEO service if you need an existing site fixed.
Be sceptical of any promise to guarantee a perfect score or a ranking. Test scores vary between runs, and what counts is the experience your real visitors have.
Website speed and SEO: common questions
Is page speed a Google ranking factor?
Yes. Google uses page experience signals, including Core Web Vitals, among many signals. Relevance and content quality remain more important, so speed works best as a tie-breaker and as protection against a very poor experience.
What is a good LCP, INP and CLS score?
Google's guidance describes good as an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less and a CLS of 0.1 or less, measured at the 75th percentile of real visits. Check web.dev/vitals for current figures.
What is the difference between lab and field data?
Lab data, from Lighthouse, is a controlled test on one device. Field data comes from real visitors and is what Search Console reports. Use lab tests to find causes and field data to judge real impact.
Why is my mobile score worse than desktop?
Phones have less processing power and often slower connections, so heavy images and scripts hurt more. Mobile is also what Google mainly uses for indexing, so prioritise it.
Will a CDN make my website faster?
It often helps by serving files from locations nearer your visitors, which is useful if your audience is spread across regions such as the UAE, the US and India. It will not fix oversized images or heavy scripts.
How much does speed optimisation cost?
It depends on the site. A clean build needs little, while a heavy template-based site may need substantial work. We include speed in every build and quote fixes for existing sites in writing. See pricing.
Do I need perfect PageSpeed scores?
No. Aim for good Core Web Vitals on real mobile users and a page that feels quick. Chasing a perfect score can waste effort that would be better spent on content.