Core Web Vitals Checker — Bulk PageSpeed & CrUX Reports

Audit Core Web Vitals for up to 100 URLs in one run. Each URL gets a client-ready report with the Lighthouse performance score (0–100), lab metrics (LCP, CLS, TBT, FCP, Speed Index), real-user CrUX field data (LCP, INP, CLS percentiles) with Google's own pass/fail Core Web Vitals assessment, and the top 5 speed opportunities ranked by estimated savings.

Data comes straight from the official Google PageSpeed Insights API v5 — the same engine behind pagespeed.web.dev — on our own provisioned API quota, so runs don't fail on the shared anonymous limit.

Why this one

• $0.01 per report, flat. No actor-start fee, no per-metric micro-charges. Comparable actors charge a $0.10 start fee plus $0.02–$0.08 per URL before extras.
• Failed URLs are free. You pay only for delivered reports — an unreachable page is recorded with its error and never billed.
• Field + lab in one row. Lab scores tell you what Lighthouse simulated; CrUX field data tells you what real Chrome users experienced, including the assessment Google actually ranks with.

Input

{
  "urls": ["https://example.com", "https://example.com/pricing"],
  "strategy": "mobile",
  "maxUrls": 25
}

strategy is mobile (Google's ranking basis, default) or desktop.

Output (one dataset item per URL)

{
  "ok": true,
  "url": "https://example.com",
  "performanceScore": 84,
  "lab": { "lcpMs": 2100, "cls": 0.01, "tbtMs": 150, "fcpMs": 900, "speedIndexMs": 1800 },
  "field": {
    "available": true,
    "coreWebVitalsAssessment": "FAST",
    "lcpMs": 1900, "inpMs": 140, "cls": 0.02
  },
  "topOpportunities": [
    { "id": "render-blocking-resources", "title": "Eliminate render-blocking resources", "estimatedSavingsMs": 780 }
  ],
  "source": "Google PageSpeed Insights API v5"
}

field.available is false for low-traffic pages Google has no real-user data for — the lab metrics still come through.

Common uses

• Agency reporting: monthly vitals rows for every client page, exportable as JSON/CSV/Excel from the dataset.
• Site migration QA: audit the top-100 URLs before and after a redesign and diff the scores.
• Monitoring: schedule a weekly run and alert when a page's assessment leaves "FAST".

Works well with

• SEO Audit Tool — title, meta, schema, robots and sitemap checks for the same URLs.
• Page Weight Analyzer — byte-level breakdown of what makes a page heavy.
• Redirect Chain Checker — where every URL actually lands before you audit it.
• Complete Site Audit — the whole-site grade in one run.

FAQ

Is this the same data as pagespeed.web.dev? Yes — the official PageSpeed Insights API v5, called with your chosen device strategy.

What's the difference between lab and field data? Lab (Lighthouse) is a controlled simulation run at audit time; field (CrUX) is aggregated from real Chrome users over the past 28 days. Google's ranking systems use field data — that's the coreWebVitalsAssessment value.

How long does a run take? PageSpeed audits take 30–60 seconds per URL on Google's side; this actor runs three in parallel, so 25 URLs finish in roughly 7 minutes.

Why did a URL come back ok: false? The page was unreachable or PageSpeed couldn't analyze it — the error is in the record and the URL was not charged.