DocsMonitoringCore Web Vitals (CrUX)

Core Web Vitals. Field data from real Chrome users.

Search Sentinel loads Chrome UX Report (CrUX) data for your URLs and updates it every week. This feature is in beta.

On this page

The data

  • Source: Google's CrUX History API, the 75th percentile (p75) of real Chrome users.
  • Metrics: LCP, INP and CLS (the Core Web Vitals), plus FCP and TTFB.
  • Devices: phone and desktop.
  • History: when you turn tracking on for a URL, up to 40 weeks of history are loaded.
  • Updates: weekly. Google publishes new CrUX data on Mondays; Search Sentinel picks it up after the release.

Core Web Vitals do not use checks from your plan.

URL and origin data

CrUX only has URL-level data for pages with enough Chrome traffic. Otherwise Search Sentinel falls back to data for the whole origin and says so: "Using origin-level data from … (no URL-specific data available)". If neither exists, the tab shows "No CrUX data available". Origin-level data is shown but never triggers alerts.

Turning it on

  • Per project: Track Core Web Vitals (CrUX) for new URLs when creating the project.
  • When adding URLs: Enable Core Web Vitals (CrUX) tracking.
  • Per URL, on its Core Web Vitals tab.
  • For all URLs: project Settings → Bulk CrUX Tracking → enable or disable all.

The dashboard

The Core Web Vitals tab of a URL shows five metric cards with the p75 value, colored good, needs improvement or poor, and the change against last week ("Stable" under 2%). Below is a week-by-week list with the share of good, needs-improvement and poor visits and the p75 value. Ten weeks are shown; Show all weeks shows the rest. Alert History lists the last 20 alerts.

Thresholds

Set thresholds per project and per device under Settings → CrUX Thresholds. The defaults follow Google's:

MetricGood up toPoor above
LCP2,500 ms4,000 ms
INP200 ms500 ms
CLS0.100.25
FCP1,800 ms3,000 ms
TTFB800 ms1,800 ms

Each of the five metrics has a good and a poor field and its own Alerts Enabled switch. LCP, INP and CLS alerts are on by default; FCP and TTFB alerts are off until you switch them on. Regression Detection applies to every metric with alerts on and has three settings, each with its own switch:

  • Week-over-week regression: 10% by default, compared with the previous week.
  • Month-over-month regression: 20% by default, compared with the week 4 weeks earlier.
  • Share of good visits: a floor of 0.75 (75%) by default.

Alerts

Every week, after the new data arrives, each metric with alerts on is checked separately for phone and desktop. An alert is sent when:

  • its p75 is above the poor threshold,
  • its p75 is worse than the previous week by more than your week-over-week percentage,
  • its p75 is worse than 4 weeks earlier by more than your month-over-month percentage, or
  • its share of good visits is below your floor.

Regressions only alert while the p75 is outside the good range, so a CLS going from 0.01 to 0.02 does not count. A threshold or floor alert is sent once and stays open until the metric is back within the limit; then you get a "Recovered" alert for that metric and device. Regression alerts are one-off notices, at most one per metric, device and week. Alerts use URL-level data only, never the origin fallback.

Alerts go to the e-mail, Slack, Teams, Google Chat and custom webhook settings of the URL when Core Web Vitals Risks is on in its alert settings. The webhook gets a JSON body with "alert_type": "core_web_vitals" and one entry in changes per alert, with the metric, device, alert type, old and new value and the raw numbers.

Beta

Core Web Vitals is in beta. CrUX is a 28-day rolling window, so a fix shows up in the data, and in a "Recovered" alert, over the following weeks rather than the next day.

Your own CrUX API key

Search Sentinel uses shared API keys by default. You can add your own Google CrUX API key in Account (as the default for all projects) or per project. Keys are used in that order: project, account, shared. If your key stops working, Search Sentinel switches to the shared key and tells you once. See Account settings.