Core Web Vitals explained for business owners
What Google's Core Web Vitals actually measure, the scores that count as good, and the fixes that make the biggest difference on a business website.

Core Web Vitals are three metrics Google uses to measure real visitors' experience of a page: Largest Contentful Paint (loading speed), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability). Good scores are LCP within 2.5 seconds, INP within 200 milliseconds and CLS below 0.1.
Key takeaways
- The three Core Web Vitals are LCP, INP and CLS; INP replaced FID in March 2024.
- Google judges pages on real-user field data at the 75th percentile, not a single lab test.
- Good vitals support rankings but never outweigh relevant, helpful content.
- Oversized images, heavy scripts and late-loading banners cause most failures on business sites.
- Mobile scores matter most in the UAE, so test on a mid-range phone over 4G.
A business owner in Dubai usually hears about Core Web Vitals in one of two ways: a developer mentions them during a redesign, or a red warning appears in Google Search Console saying pages are "poor". Neither explains what the numbers mean or whether they are worth money to fix.
This guide covers the three metrics in plain terms, what counts as a pass, how much they affect rankings, and a practical order of fixes. It is written for owners and marketing managers, not developers, so you can have a sensible conversation with whoever builds your site.
What are Core Web Vitals?
Core Web Vitals are a small set of user-experience metrics that Google defines and measures using data from real Chrome users. Each one answers a simple question a visitor would ask without thinking about it.
- Largest Contentful Paint (LCP): how long until the main content, usually the hero image or headline, appears. "Is this page loading?"
- Interaction to Next Paint (INP): how quickly the page responds visually after a tap, click or key press. "Did my tap work?"
- Cumulative Layout Shift (CLS): how much the layout jumps around while loading. "Why did the button move just as I pressed it?"
INP replaced First Input Delay (FID) as the responsiveness metric in March 2024. FID only measured the delay before the first interaction, while INP looks at interactions across the whole visit, which is a much tougher and fairer test for sites with menus, filters, sliders and forms.
What scores should you aim for?
A page passes when at least 75% of real visits meet the "good" threshold for all three metrics. Google publishes these thresholds:
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| LCP (loading) | 2.5 seconds or less | 2.5 to 4 seconds | Over 4 seconds |
| INP (responsiveness) | 200 ms or less | 200 to 500 ms | Over 500 ms |
| CLS (visual stability) | 0.1 or less | 0.1 to 0.25 | Over 0.25 |
The 75th percentile rule matters. Your page might load in one second on the office fibre connection, but if a quarter of visitors are on older phones in a basement car park in Deira, those visits pull the score down. That is the experience Google is measuring.
Do Core Web Vitals affect Google rankings?
Yes, but modestly. They form part of Google's page experience signals, and Google has been clear that great page experience does not override relevance. A fast page with thin content will not outrank a slower page that answers the query properly.
Where vitals do make a difference is between pages of similar quality, which is common in competitive UAE sectors such as real estate, clinics and home services. The bigger commercial effect is usually on conversions rather than rankings. Visitors who wait for a slow page or tap the wrong button because the layout shifted often leave, and that lost enquiry costs you whether it came from SEO or a paid click.
How do you check your Core Web Vitals?
Start with the free Google tools, and learn the difference between field data and lab data before acting on any number.
- Google Search Console, Core Web Vitals report: groups your URLs into good, needs improvement and poor, separately for mobile and desktop. This is field data and the best place to start.
- PageSpeed Insights: enter a URL to see field data from the Chrome UX Report at the top, if the page has enough traffic, and a Lighthouse lab test underneath with specific recommendations.
- Chrome DevTools: useful for developers to reproduce a problem, throttle the connection and see exactly which element is the LCP or which script is blocking interaction.
Lab scores are a simulation. They are helpful for diagnosis, but a Lighthouse score of 95 does not mean you pass, and a score of 60 does not mean you fail. Field data decides.
What usually causes poor scores on business websites?
Most failures come from a short list of repeat offenders, especially on WordPress and page-builder sites.
Slow LCP
- Uncompressed hero images or background videos, often several megabytes.
- Slow hosting or no caching, so the server takes a long time to respond.
- The hero image being lazy-loaded, which delays the very thing LCP measures.
- Web fonts and render-blocking CSS loading before anything can appear.
Poor INP
- Too many third-party scripts: chat widgets, several tracking pixels, heatmaps, review badges.
- Heavy page builders and sliders running large amounts of JavaScript on every tap.
- Forms and filters that do a lot of work in the browser before showing feedback.
High CLS
- Images and embeds without width and height set, so the page reflows when they load.
- Cookie banners, promo bars or WhatsApp buttons injected at the top after the page appears.
- Fonts swapping late and changing line lengths, which is common with Arabic web fonts on bilingual sites.
How do you fix Core Web Vitals, step by step?
Fix in order of impact, and re-measure between steps so you know what worked. A practical sequence we use:
- Find the templates that fail. Search Console groups similar URLs, so one fix to a service page template can fix hundreds of pages.
- Sort out hosting and caching. A fast server response is the foundation for LCP. Use page caching and a CDN, ideally with edge locations close to the Gulf.
- Optimise the hero. Serve correctly sized, modern-format images, do not lazy-load above-the-fold images, and preload the LCP image if needed.
- Audit third-party scripts. List every tag in Google Tag Manager and the theme. Remove what nobody uses, and delay non-essential widgets until after interaction.
- Reserve space. Set dimensions on images, video embeds and ad slots, and make banners overlay the page rather than push it down.
- Retest on real conditions. Field data in Search Console takes around 28 days to fully reflect changes, so validate the fix there and be patient.
For a wider view of speed beyond these three metrics, see our guide to website speed optimisation. If you are commissioning a new site, include vitals targets in the brief rather than fixing them after launch.
Why do Core Web Vitals matter more for UAE audiences?
UAE browsing is overwhelmingly mobile, and much of it happens on the move: in taxis, on the Metro, between meetings. Many sites here also carry extra weight that sites elsewhere do not, such as bilingual fonts, WhatsApp chat widgets, multiple ad pixels for Google Ads, Meta ads, TikTok and Snapchat, and large lifestyle photography.
Each of those is reasonable on its own. Together they are why so many Dubai websites look impressive on a designer's desktop and fail on a mid-range Android phone. Testing on the devices your customers actually use is the single most useful habit to build.
How Upscaleads can help
We audit Core Web Vitals as part of our SEO services, then fix the underlying causes in the theme, hosting and tag setup rather than chasing a lab score. For ongoing monitoring after launch, our website maintenance and support plans keep new plugins and campaigns from undoing the work. If your Search Console report is showing red, get in touch and we will tell you which issues are worth fixing first.
Frequently asked questions
Is a PageSpeed Insights score of 100 required to rank well?
No. The overall PageSpeed score is a lab simulation from Lighthouse and is not a ranking factor in itself. What Google uses is field data from real Chrome users for LCP, INP and CLS. Many pages that rank well score in the 60s or 70s in the lab while passing Core Web Vitals in the field. Aim to pass the three metrics rather than chase a perfect number.
What replaced First Input Delay in Core Web Vitals?
Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital in March 2024. FID measured only the delay before the browser began handling the first interaction. INP measures how long the page takes to visibly respond to taps, clicks and key presses throughout the visit, so it better reflects how responsive a page feels. A good INP is 200 milliseconds or less.
Why does Search Console show no Core Web Vitals data for my site?
Search Console only reports Core Web Vitals when there is enough real-user data in the Chrome UX Report. Newer or low-traffic sites often do not meet that threshold, so the report stays empty. In that case, use PageSpeed Insights lab tests and Chrome DevTools to diagnose issues, and focus on the known causes such as heavy images, excess scripts and missing image dimensions.
Can a WordPress website pass Core Web Vitals?
Yes. WordPress sites can pass comfortably when they use good hosting, a lightweight theme, page caching, optimised images and a limited number of plugins and third-party scripts. Problems usually come from heavy page builders, sliders, many tracking tags and unoptimised media rather than WordPress itself. A performance audit can show which plugins or template elements are responsible.



