What are good Core Web Vitals scores?

According to web.dev, a page should have a Largest Contentful Paint within 2.5 seconds, an Interaction to Next Paint of 200 milliseconds or less, and a Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads and split by mobile and desktop.

Does XeoRank monitor Core Web Vitals continuously?

No. XeoRank measures one URL at a time when you or your AI assistant ask for it, on mobile or desktop. It does not watch every page around the clock, send alerts, or add a real-user monitoring script to your site. Monitoring with XeoRank means measuring the pages that matter and measuring again after each change.

What is the difference between lab data and field data?

Lab data comes from a simulated page load, so you get it for any URL and it includes diagnostics. Field data comes from the Chrome UX Report, which web.dev describes as anonymized measurements from real Chrome users, so it shows what visitors experience but only exists when Google has data for the page or site. Interaction to Next Paint needs real user input, so it comes from field data; lab runs report Total Blocking Time instead.

Is there a free Core Web Vitals checker?

Yes. XeoRank's free Core Web Vitals checker at xeorank.com/tools/core-web-vitals-checker measures a URL without an account. Inside XeoRank, the same kind of measurement is available from the dashboard and to your AI assistant through the MCP server.

Can the AI agent fix Core Web Vitals problems?

Some of them. On WordPress, page-level changes such as uploading a smaller image and swapping it into a page, or simplifying a heavy section, can be prepared by your AI assistant, and your AI client asks you to allow each change first. Problems in themes, plugins, caching, hosting and server response time usually need a developer or your host.

Core Web Vitals Monitoring and Checker

XeoRank measures Core Web Vitals for one URL at a time, whenever you or your AI assistant ask, up to your plan's monthly allowance (5 measurements on Starter, 100 on Pro, 500 on Growth), on mobile by default or on desktop. Each measurement combines PageSpeed lab data with Chrome UX Report field data from real Chrome users when it is available, along with the diagnostics that explain a poor score.

To be clear about the word monitoring: XeoRank does not watch your whole site around the clock or send alerts. You measure the pages that matter, change something, and measure again. Earlier measurements are saved, so a before-and-after comparison is one question away. If you only need a quick reading, the free Core Web Vitals checker works without an account.

Who it is for

Site owners whose key pages feel slow on mobile and who want to know which metric is failing and why.
Agencies checking client landing pages before and after a redesign or a new theme.
Anyone who has just added a plugin, a chat widget or a tracking script and wants to know whether it slowed the page.
Developers and marketers who want their AI assistant to measure a page, read the diagnostics and suggest the fix in one conversation.

The thresholds

Google's web.dev guide sets the targets for the three Core Web Vitals. It recommends measuring them at the 75th percentile of page loads, separately for mobile and desktop (web.dev, Web Vitals).

Metric	What it measures	Good, per web.dev
Largest Contentful Paint (LCP)	how quickly the main content appears	within 2.5 seconds
Interaction to Next Paint (INP)	how quickly the page responds to input	200 milliseconds or less
Cumulative Layout Shift (CLS)	how much the layout jumps while loading	0.1 or less

Source for all three thresholds: web.dev, Web Vitals.

What a measurement includes

Pick a URL and a device. Mobile is the default; switch to desktop when you need it.

Field data. When the Chrome UX Report has data for the page, or failing that for the whole site, you see LCP, INP and CLS as real visitors experienced them, plus First Contentful Paint and Time to First Byte. The same web.dev guide describes the Chrome UX Report as anonymized, real-user measurement data for each Core Web Vital. When it has no data for either, you get lab data only.

Lab data. A simulated load from PageSpeed gives a performance score, LCP, CLS, First Contentful Paint, Speed Index, server response time and Total Blocking Time. Web.dev notes that lab tools cannot measure INP because there is no user input, and that Total Blocking Time is a lab-measurable proxy for it (source).

Diagnostics. The lab run also tells you what is slowing the page down, for example:

the element counted as the Largest Contentful Paint, and whether it was discovered late;
the elements that shifted the layout, and images without set dimensions;
render-blocking resources, unused CSS and JavaScript, and long main-thread tasks;
images that could use a modern format, better compression or responsive sizes;
third-party code and its share of the load.

Running a measurement

Dashboard: choose the page and the device.
AI assistant: through the MCP server it calls measure_cwv for a URL and get_cwv_results to read the site's measurement history, so you can compare a page before and after a change.
Free tool: the Core Web Vitals checker gives a one-off reading without an account.

If the field and lab numbers disagree, the field numbers describe what visitors actually got, and the lab run is where you look for the cause.

Where it fits with the rest of XeoRank

The technical SEO audit does not measure speed. Use the audit to find the pages that matter, then measure those pages here to see the field and lab numbers behind them.

With the XeoRank MCP server connected to Claude, ChatGPT, Codex, Cursor or VS Code, one request can do both:

"Measure Core Web Vitals for our homepage and /pricing on mobile. Tell me which metric fails on each and what the diagnostics say is causing it."

What the AI agent can and cannot fix

On a WordPress site with the free XeoRank Connector plugin, your assistant can make page-level changes: upload a lighter image file and swap it in for an oversized one, simplify a heavy section, or edit an Elementor layout. Your AI client asks you to allow each change first. Writes are off for each site until you turn them on, new pages are created as drafts, edits to an existing page are written to that page, and every change to a page's content keeps a snapshot you can restore. Measure again afterwards to confirm the change helped.

Many Core Web Vitals problems sit outside the page content: slow hosting, missing caching, a heavy theme, or plugins loading scripts on every page. The diagnostics point to them, but the fix is usually for a developer or your hosting provider.

What it does not do

It does not measure every page of the site in one go. You measure one URL at a time.
It does not run continuous monitoring, send alerts or install a real-user monitoring script.
It does not create field data. If the Chrome UX Report has nothing for a page, you get lab data only.
It does not change hosting, caching or server settings.
It does not promise rankings. A better score improves what visitors experience; it does not guarantee a better position.

Pricing

Starter is $19 a month for one site, with a 14-day free trial and no card needed. Pro is $49 a month and Growth is $109 a month. See pricing for what each plan includes.

Core Web Vitals monitoring, one URL at a time, whenever you ask