Core Web Vitals Monitor: CrUX + Lighthouse, Trends & Alerts
Pricing
from $4.50 / 1,000 url checked (lab + field)s
Core Web Vitals Monitor: CrUX + Lighthouse, Trends & Alerts
Bulk Core Web Vitals for whole sites: real-user CrUX field data (URL with origin fallback), Lighthouse lab audits, 40-week trends and regression alerts between scheduled runs. Sitemap-driven sampling per page template. Bring your own Google API key for unlimited volume.
Pricing
from $4.50 / 1,000 url checked (lab + field)s
Rating
0.0
(0)
Developer
Marcel Tomas
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Check Core Web Vitals for a whole site in one run, with real-user field data (Chrome UX Report), Lighthouse lab audits, 40-week trends, and regression alerts between scheduled runs. Point it at a sitemap and it samples a few URLs per page template (product, post, category…), so you see which template is slow instead of auditing 5,000 near-identical pages.
Built for SEO and WordPress/WooCommerce agencies and in-house web teams who track many sites.
What you get per URL and device
| Data | Source | Notes |
|---|---|---|
| p75 LCP, INP, CLS, FCP, TTFB + GOOD / NEEDS_IMPROVEMENT / POOR + CWV pass/fail | CrUX API (real Chrome users, rolling 28 days) | URL-level when available; otherwise origin-level fallback (field.level) |
| Lighthouse performance score, lab LCP / TBT / CLS / FCP / Speed Index, top 5 opportunities | PageSpeed Insights API | Lab data varies between runs (±5 points is normal) |
| Weekly p75 series + trend label (improving / stable / worsening) | CrUX History API | One representative URL per site and template (origin fallback), up to 40 weeks |
| Regression flags vs the previous run | This Actor (monitorId) | p75 worse by >10 %, a metric dropping a category, or a lab score drop >15 points |
The key-value store also gets SUMMARY (per site, template and device: CWV pass rate, median and worst p75, median lab score) and REGRESSIONS (a ready-to-alert list).
Quick start
- One-off audit: add your sitemap under Sitemaps and run it. Lab and field data are on by default.
- Weekly monitoring: set a Monitor ID (e.g.
client-acme), turn Lab audit off for the cheapest field-only check, and create an Apify Schedule (CrUX History refreshes on Mondays, so Tuesday works well). Hook the Regressions only view or theREGRESSIONSrecord to Slack, email or the free n8n / Make template. - Large sites or agencies: add your own Google API key (see below). It removes the free-plan lab limit and uses your own Google quota.
Input highlights
urlsand/orsitemapUrls(sitemap index and.gzsupported; up to 3 levels, 50 files, 50,000 URLs).samplesPerTemplate(default 3, per site when you add several sites). Deterministic: the same URLs are re-tested every run, so trends compare like with like.templateRulesto override detection with regexes, e.g.[{"name":"pdp","pattern":"/shop/"}].formFactors:PHONE,DESKTOP.includeField,includeLab,includeHistory,historyPeriods.monitorIdandregressionThresholds.googleApiKey(secret, optional).
Pricing (pay per event)
You pay only for records delivered with data:
| Event | When |
|---|---|
url-checked | A URL × device record with lab data (field data included when available) |
field-only-check | A record with field data only (lab off or failed): the cheap monitoring path |
history-trend | One weekly trend series delivered |
Never charged: URLs with no data (no-field-data), errors, invalid input, or the part of a run that exceeds your max-charge limit. The run stops cleanly at your budget. (Prices: see the Pricing tab.)
Your own Google API key (BYOK)
- In Google Cloud Console, create a project and enable Chrome UX Report API and PageSpeed Insights API. Both are free of charge; no billing account is needed.
- Create an API key. Restricting it to those two APIs is recommended.
- Paste it into Your Google API key. It is stored as an encrypted secret input and never logged or written to outputs.
Without your own key, runs on the Apify free plan are limited to 25 lab audits per run (field data is not limited). Paid Apify plans aren't limited this way.
Good to know
- CrUX popularity threshold: many low-traffic URLs have no URL-level data. You then get origin-level data (
field.level: "origin"), orno-field-data(not charged). - Field data lags: it is a rolling 28-day window, so a fix shows up gradually over about 4 weeks. Lab data reacts immediately.
- Quotas: CrUX allows 150 queries/min per Google project (this Actor uses ≤120). If Google's quota runs out mid-run, the Actor stops cleanly, keeps what it delivered and charges nothing for the rest.
- Pages behind login, RUM and screenshots are out of scope.
Data & attribution
Contains Chrome UX Report data by Google, licensed under CC BY 4.0. Lab data is produced by PageSpeed Insights (Lighthouse). This Actor is not affiliated with or endorsed by Google.
Related
- Sitemap & Indexability Auditor: which sitemap URLs Google cannot index, and why (noindex, canonical, robots.txt, redirects, hreflang).
Support
Open an issue on the Actor's Issues tab. Include the run ID; never paste your API key.
