FIX · CORE WEB VITALS
Core Web Vitals from real users, template by template.
Field Core Web Vitals from the Chrome UX Report for your origin, homepage and a representative page from each template, on phone and desktop, next to the site-audit findings that explain them.
- Real-user field data
- Phone and desktop
- One page per template
| Template | LCP | INP |
|---|---|---|
| Homepage | 2.1 s | 160 ms |
| Product | 3.4 s | 240 ms |
| Category | 2.8 s | 310 ms |
| Blog article | 1.9 s | 120 ms |
3 metrics
LCP, INP and CLS
2 devices
phone and desktop, separately
Templates
one representative URL per template
Lighthouse
optional lab checks for diagnostics
INSIDE THE PRODUCT
Speed measured where it matters: real visits.
Field data shows what visitors experience; the audit shows why.
Field data
See what real visitors experience
Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift come from real Chrome users wherever Google publishes enough data.
- LCP, INP and CLS
- Origin and page level
- Phone and desktop
Templates
Fix the template, not a thousand pages
The audit picks a representative URL for each template, so a slow product or category layout shows up once, with the findings that affect it.
- Representative URL per template
- Linked audit findings
- Compare after the next audit
- PoorProductLCP 3.4 s · hero image 1.2 MB
- Needs workCategoryINP 310 ms · filter script
- GoodBlog articleLCP 1.9 s
- GoodHomepageLCP 2.1 s
Lab checks
Diagnose with Lighthouse when you need to
Add optional Lighthouse checks to a site audit for lab diagnostics on the pages that matter most, then confirm the improvement in field data.
- Optional Lighthouse runs
- Diagnostics per page
- Field data to confirm
Devices
Phone and desktop, read separately
Real-user values differ by device, so phone and desktop are shown side by side for the origin, the homepage and each template.
- Phone and desktop side by side
- Origin, homepage and templates
- Good, needs improvement or poor
| Template | LCP | INP |
|---|---|---|
| Homepage | 2.1 s | 160 ms |
| Category | 2.9 s | 240 ms |
| Product | 3.4 s | 310 ms |
| Article | 1.9 s | 120 ms |
Lab diagnostics
Lighthouse when you need the reason
Add Lighthouse checks to an audit for the templates that fail in the field, and read the opportunities and diagnostics that explain them.
- Optional per audit
- Run on key templates
- Cost shown before start
- OpportunityLargest image not preloadedHero image found late
- OpportunityRender-blocking CSS2 stylesheets
- DiagnosticLong main-thread tasks6 tasks over 50 ms
- PassedText compressionEnabled
WHAT IT MEASURES
The three Core Web Vitals, and where they come from.
What each metric tells you, and where it comes from.
| Metric | What it tells you | Source |
|---|---|---|
| Largest Contentful Paint (LCP) | How long the main content takes to appear; good is 2.5 s or less. | Chrome UX Report |
| Interaction to Next Paint (INP) | How quickly the page responds to taps and clicks; good is 200 ms or less. | Chrome UX Report |
| Cumulative Layout Shift (CLS) | How much the layout jumps while loading; good is 0.1 or less. | Chrome UX Report |
| Assessment | Whether the 75th percentile passes each threshold. | Chrome UX Report |
| Lab scores and diagnostics | Simulated load and the reasons behind slow metrics. | Lighthouse (optional) |
UNDER THE HOOD
How Core Web Vitals are collected.
How the numbers are produced, so you can judge them for yourself.
Field data from Chrome users
Ndovu reads the Chrome UX Report for your origin, the homepage and one representative URL per template, on phone and desktop.
The 75th percentile
Each metric is the 75th percentile of real visits over a rolling 28-day window, judged against Google’s thresholds: LCP 2.5 s, INP 200 ms, CLS 0.1.
Cached, then refreshed
Values are fetched on demand and with audits, then cached for a day, so pages load quickly without hiding stale data.
Lab checks on request
Lighthouse runs on chosen templates through a provider, for the diagnostics that field data cannot give.
HOW IT WORKS
From a slow template to a faster one.
Four steps from connecting your data to a decision you can stand behind.
Run an audit
The audit picks a representative URL for each template.
Read the field data
Check LCP, INP and CLS by template and device.
Find the cause
Add Lighthouse to the failing templates for diagnostics.
Fix and compare
Ship the template fix, then compare on the next audit as field data updates.
WITH YOUR AI AGENT
Ask which template is slowing the site.
Your agent can run an audit with Lighthouse on up to 10 representative pages, then read the findings.
- Uses the same data as the web app
- Paid tools estimate their cost first
- Saves the report to the project
YouWhich template fails Core Web Vitals on phones?
run_site_auditget_audit_statusget_audit_issues
AgentThe product template fails LCP on phones at 3.4 s; the hero image is discovered late. Category pages pass LCP but sit at 240 ms for INP, just over the threshold.
YouWhat should the developers change first?
AgentPreload the product hero image and remove one render-blocking stylesheet. Then check the next audit’s field data.
Illustration · sample data
USE CASES
Built for the way you work.
How teams put it to work.
Speed up product pages
Find the product or category template that is slow on phones and fix it once.
Prove the fix
Compare field data before and after a release, template by template.
Speed up the product template
Fix the template behind thousands of product pages, and see it in field data on the next audit.
Get the reason, not just the score
Use Lighthouse diagnostics on the templates that fail for real users.
DATA & LIMITS
Know what the numbers can and cannot tell you.
Where the data comes from, how fresh it is, and the questions it cannot answer on its own.
| Source | What it provides | Freshness & limits |
|---|---|---|
| Chrome UX Report | Real-user LCP, INP and CLS at the 75th percentile. | Only pages and origins with enough Chrome traffic; a rolling 28-day window; cached for a day. |
| Lighthouse provider | Lab diagnostics. | Optional; paid per run. |
No data is not good data
Low-traffic pages show no field data rather than a guessed score.
Field data moves slowly
The Chrome UX Report is a rolling 28-day window, so a fix shows gradually.
Lab is not field
Lighthouse simulates one load on one device; real users vary.
Chrome users only
Field data comes from Chrome users who share usage statistics.
WORKS WITH
Connected to the tools you already use.
The sources and clients this feature reads from or works alongside.
CHOOSE THE RIGHT VIEW
Which view answers which question.
Start where the question points. Each view keeps its own source.
| Your question | Start with | Why |
|---|---|---|
| Is my site slow for real users? | Core Web Vitals | Field data by template. |
| Why is one page slow? | Inspect URL | Every signal for one URL. |
| What else is wrong with the template? | Technical site audit | Issues grouped by template. |
LEARN & TRY
Guides and free tools for the same job.
Read how the evidence works, or try a free check before you connect a project.
Prioritise a technical audit
Fix the issues on the pages that earn search attention first.
FAQ
Core Web Vitals: common questions.
Straight answers about what it does, what it costs and where its limits are.
Where does the data come from?
From Google’s Chrome UX Report, real-user data collected from Chrome, for your origin and representative pages.
Why do some pages have no data?
The Chrome UX Report only covers pages and origins with enough traffic. Low-traffic pages show no field data rather than a guessed score.
How fresh is the data?
It reflects a rolling 28-day window from Google, fetched on demand and cached for a day.
Do Lighthouse checks cost credits?
Lighthouse checks may incur provider charges, shown before you run them. Field data does not.
Why does my page have no field data?
The Chrome UX Report only publishes data for pages and origins with enough real-user traffic. Ndovu shows nothing rather than a guess.
Is INP included?
Yes. Interaction to Next Paint replaced First Input Delay as a Core Web Vital, and it is shown with LCP and CLS.
Does Ndovu monitor speed continuously?
Field data is read on demand and with each audit, and cached for a day. Schedule audits to track it over time.
Do I need Lighthouse?
No. Field data is free to read. Lighthouse is an optional diagnostic with a provider cost.
Which pages are checked?
The origin, the homepage and one representative URL per template, on phone and desktop.
What are the limits of the data?
The Chrome UX Report only covers pages and origins with enough real-user traffic. Low-traffic pages show no field data rather than a guessed score. Values are fetched on demand and cached for a day; Lighthouse checks may incur provider charges.
How do I get access?
Platform access is reviewed. Request access with your website and the data sources you use, and the team will help you connect them.
See it with your own data.
Tell us about your website. We will review access and help you connect the right sources.