Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors: how fast the main content appears, how quickly the page reacts when someone taps or clicks, and how much the layout jumps around while it loads. A page passes when most real visits meet Google’s targets for all three. Below you will find Core Web Vitals explained in plain terms, plus how to check your own site and what usually needs fixing on a typical UAE business website.
What the three Core Web Vitals measure
Google’s web.dev guide to Web Vitals lists the three metrics and the target for each. You do not need to know the technical details to use them, but it helps to know what each number is describing.
| Metric | What it describes | Good result |
|---|---|---|
| Largest Contentful Paint (LCP) | How long the biggest visible item, usually a banner image or headline, takes to appear | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds after a click, tap or key press | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much content moves unexpectedly while the page loads | 0.1 or less |
Google also defines “needs improvement” and “poor” bands above these targets. In practice, the goal is simple: get every important page into the good range on mobile and on desktop.
LCP in everyday terms
Think of a visitor opening your home page on their phone. LCP is the moment the large hero image or main heading finally shows up. If that takes too long, the page looks blank or half-built, and many people press back before they see your offer.
INP in everyday terms
INP is about the delay after someone does something: opening the menu, tapping “Book now”, choosing a size on a product page or typing into a form. When the page is busy running scripts, the tap appears to do nothing for a moment. Visitors tap again, or give up.
CLS in everyday terms
CLS measures the annoying jump when a late image, banner or cookie notice pushes the text down just as someone is about to tap a link. On a restaurant site, that can mean tapping “Call” when the visitor meant to tap “Menu”.
How Google measures them: real visitors, not test scores
This is the part most business owners miss. Google assesses Core Web Vitals using field data, meaning measurements from real Chrome users who visited your pages. The web.dev guide says to look at the 75th percentile of page loads, split between mobile and desktop. In plain terms, at least three out of four visits need a good experience for the page to pass.
That is why a single speed test on your office Wi-Fi can look fine while Google still reports a problem. Your customers may be on older phones, on mobile data, or opening the site from a link inside WhatsApp or Instagram. Lab tools such as Lighthouse are useful for finding causes, but the field data is what counts.
How to check your own website
You can check where you stand in a few minutes, without any technical setup.
- Google Search Console. Open the Core Web Vitals report. According to Google’s help page for the report, it uses real-user data from the Chrome UX Report and groups pages that behave similarly, so one example URL stands for a group of pages.
- PageSpeed Insights. Enter a page address. The top section shows real-user data if Google has enough of it; the lower section is a lab test that lists likely causes.
- Look at mobile first. Google reports mobile and desktop separately. Phones have less processing power and often slower connections, so a site that passes on desktop can still fail on mobile.
Two details from Google’s help page are worth knowing. A group of pages takes the status of its worst metric, so a page with good LCP and INP but poor CLS is reported as poor. And if a small site does not have enough visits for page-level data, Search Console falls back to data for the whole domain, or shows no data at all.
Common causes on UAE business websites
These are the usual causes we look for on clinic, real-estate, restaurant and trading company sites.
Slow LCP
- Large hero images or sliders uploaded straight from a camera or designer, without resizing or compression.
- Slow hosting, or a server located far from your visitors, so the first response takes too long. Our guide to moving a website to new hosting without downtime covers how to switch safely if this is the cause.
- Page builders and themes loading many fonts, icon sets and stylesheets before the main content can show.
Poor INP
- Too many third-party scripts: chat widgets, several analytics and ad tags, heatmap tools and pop-up builders all competing for the phone’s processor.
- Heavy sliders, animations and mega-menus that run a lot of JavaScript when tapped.
- Plugins that each add their own scripts to every page, even pages that do not use them.
High CLS
- Images and videos without fixed width and height, so the browser does not reserve space for them.
- Cookie notices, promotional bars or chat buttons that appear late and push content down.
- Custom web fonts, including Arabic fonts on bilingual sites, that load late and render at a different size from the fallback font.
What to fix first
You will rarely need to fix everything at once. A sensible order looks like this:
- Start with the pages that bring enquiries: the home page, main service pages, booking or contact page, and top product pages.
- Fix the worst metric on each page group, since that is what sets the group’s status.
- Remove before you optimise. Deleting an unused slider, an old tracking tag or a plugin nobody uses often helps more than any setting.
- Resize and compress images, and give every image and embed fixed dimensions.
- Review hosting and caching if the first server response is slow on every page.
If you are planning a redesign anyway, build these targets into the brief so the new site starts in the good range. Our guide on redesigning a website without losing Google rankings explains how to protect your existing search traffic at the same time.
How much Core Web Vitals matter for rankings
Google’s own Search Central page on Core Web Vitals recommends that site owners achieve good scores and says they align with what its core ranking systems aim to reward. It does not say how much weight they carry. Relevant, useful content still matters most. A fast page with weak content will not outrank a slower page that answers the question well.
The stronger business case is what happens after someone lands on your site. A page that shows its content quickly, responds to taps straight away and does not jump around makes it easier for a visitor to call, book or buy. That is worth fixing even before you think about rankings. Speed and Core Web Vitals work is part of our SEO services for UAE businesses.
Frequently asked questions
Is a PageSpeed score of 100 required?
No. The lab score in PageSpeed Insights is a diagnostic tool. What Google assesses is the real-user data for LCP, INP and CLS. A page can pass Core Web Vitals with a lab score below 100.
Why does Search Console show “no data” for my site?
Search Console needs enough real visits from Chrome users before it can report. New or low-traffic sites often show no data, or only a combined result for the whole domain. In that case, use the lab test in PageSpeed Insights to find obvious problems.
How long does it take for fixes to show up?
Field data builds up from visits over time, so improvements are not instant. When you start validation for an issue in Search Console, Google’s help page says it monitors the affected pages for 28 days before confirming the fix.
Can a WordPress site with Elementor pass Core Web Vitals?
Yes, but it takes care: a lean theme, fewer plugins, sensible image handling and good hosting. Many slow WordPress sites are slow because of add-ons stacked up over the years rather than WordPress itself.
If your Core Web Vitals report shows poor or “needs improvement” pages, send us the site address and a short brief through our contact page. We will look at the report and reply with what we would fix and a fixed quote.
