Bulk Core Web Vitals & PageSpeed Audit avatar

Bulk Core Web Vitals & PageSpeed Audit

Pricing

from $3.00 / 1,000 results

Go to Apify Store
Bulk Core Web Vitals & PageSpeed Audit

Bulk Core Web Vitals & PageSpeed Audit

Bulk Core Web Vitals and PageSpeed audit: Lighthouse performance, SEO and accessibility scores, LCP, CLS, INP, TBT and the top fixes — one row per URL and device.

Pricing

from $3.00 / 1,000 results

Rating

0.0

(0)

Developer

Murat Uzun

Murat Uzun

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

20 hours ago

Last modified

Share

What is Bulk Core Web Vitals & PageSpeed Audit?

Bulk Core Web Vitals & PageSpeed Audit is an Apify Actor that runs Google PageSpeed Insights (Lighthouse plus Chrome UX Report field data) over a whole list of URLs and returns one flat row per URL and device — Lighthouse performance, SEO, accessibility and best-practices scores, LCP, CLS, INP, TBT, FCP, Speed Index and TTFB, a pass/fail on Google's Core Web Vitals thresholds, and the five biggest fixes Lighthouse found. It is the same data pagespeed.web.dev shows you one URL at a time, for 500 URLs in one run, straight into a dataset, CSV or your API.

What data does the Core Web Vitals audit extract?

Every row mixes lab data (a fresh Lighthouse run on Google's hardware) with field data (real Chrome users, trailing 28 days, when the origin has enough traffic to be in CrUX):

FieldTypeDescription
url / finalUrlstringSubmitted URL and the URL Lighthouse measured after redirects
strategystringmobile or desktop
performanceScoreintegerLighthouse performance, 0–100
accessibilityScore / bestPracticesScore / seoScoreinteger0–100, null when the category was not requested
lcpMs / cls / tbtMsnumberLab Largest Contentful Paint, Cumulative Layout Shift, Total Blocking Time
fcpMs / speedIndexMs / ttiMs / ttfbMsintegerLab First Contentful Paint, Speed Index, Time to Interactive, server response time
fieldDataobjectReal-user lcpMs, cls, inpMs, fcpMs, ttfbMs, overallCategorynull when CrUX has no data for the origin
passesCoreWebVitalsbooleanTrue when field LCP ≤ 2500 ms, CLS ≤ 0.1 and INP ≤ 200 ms
labGradestringgood (≥ 90), needs-improvement (≥ 50), poor
topOpportunitiesarrayUp to 5 failed Lighthouse opportunities as {id, title, savingsMs}, biggest saving first
lighthouseVersion / fetchedAtstringLighthouse version and the timestamp of Google's run
error / scrapedAtstringWhy a URL has no metrics (e.g. a rate limit), and when the row was produced

How to use Bulk Core Web Vitals & PageSpeed Audit

  1. Get a free Google PageSpeed Insights API key (one click, no billing: https://developers.google.com/speed/docs/insights/v5/get-started) and paste it into Google PageSpeed Insights API key. Without a key Google's shared anonymous quota is almost always exhausted and every row comes back with an HTTP 429 error.
  2. Paste your URLs into URLs to audit — one per row, full URLs, the exact pages you care about.
  3. Pick the Device strategy (mobile is what Google ranks on; both returns two rows per URL) and any extra Lighthouse categories.
  4. Leave Max concurrency at 2–3, click Start, then download JSON, CSV, Excel or HTML from the Output tab.

Example input

{
"urls": ["https://apify.com", "https://example.com"],
"apiKey": "YOUR_FREE_PSI_API_KEY",
"strategy": "mobile",
"categories": ["performance", "seo"],
"maxConcurrency": 2
}

Example output

{
"url": "https://apify.com",
"finalUrl": "https://apify.com/",
"strategy": "mobile",
"performanceScore": 62,
"seoScore": 92,
"lcpMs": 4219,
"cls": 0.041,
"tbtMs": 891,
"ttfbMs": 310,
"fieldData": { "lcpMs": 2212, "cls": 0.04, "inpMs": 152, "ttfbMs": 612, "overallCategory": "AVERAGE" },
"passesCoreWebVitals": true,
"labGrade": "needs-improvement",
"topOpportunities": [
{ "id": "unused-javascript", "title": "Reduce unused JavaScript", "savingsMs": 2150 },
{ "id": "render-blocking-resources", "title": "Eliminate render-blocking resources", "savingsMs": 780 }
],
"lighthouseVersion": "12.2.1",
"fetchedAt": "2026-09-12T15:28:41.903Z",
"error": null,
"scrapedAt": "2026-09-12T15:30:00.000Z"
}

Input parameters

ParameterTypeDefaultDescription
urlsarray["https://apify.com"]Page URLs to audit, one row per URL × device
apiKeystring (secret)noneFree Google PSI API key — 25,000 requests/day
strategyenummobilemobile, desktop or both
categoriesarray["performance"]performance, accessibility, best-practices, seo
localestringenLanguage of Lighthouse titles
maxConcurrencyinteger2Parallel PSI requests (1–5)

Pricing

Pay-per-event: $0.005 per audited URL × device ($5 per 1,000 rows), plus a negligible $0.00005 actor-start fee, platform usage included. All the heavy lifting happens on Google's servers, so compute stays tiny — auditing 1,000 URLs costs $5 and a few cents of usage. strategy: "both" doubles the row count, so it doubles the price. Set Maximum cost per run and the Actor trims the list to what the budget covers instead of overspending.

Bulk Core Web Vitals audit vs. pagespeed.web.dev and monitoring subscriptions

pagespeed.web.dev tests one URL per click and keeps no history. SEO monitoring suites (SpeedCurve, DebugBear, Semrush Site Audit) sell monthly seats. This Actor is pay-per-event with no subscription: run 500 prospect homepages overnight, schedule the same 50 URLs weekly to watch a regression, or call it from your own code — results land in a dataset you can join to anything else.

Using Bulk Core Web Vitals & PageSpeed Audit with AI agents and MCP

The Actor is pay-per-event with limited permissions, the two requirements for an Actor to be callable through the Apify MCP server at mcp.apify.com. An agent passes urls (and ideally apiKey) and gets flat, numeric rows back — no HTML, no nesting to unpack — and the same call works from n8n, Make, Zapier or LangChain through Apify's integrations.

FAQ

Do I need a Google API key? Runs of up to 5 URLs work without a key on a shared demo quota, so you can try the Actor straight away. For bigger batches paste your own free PageSpeed Insights API key (25,000 requests per day) into the API key field - Google's anonymous quota is shared by everyone and is usually exhausted.

Do I really need an API key? For anything beyond a smoke test, yes. The keyless quota is shared by every anonymous caller on the internet and is usually spent; those rows come back with error set and null metrics instead of failing the run. A key is free and allows 25,000 requests/day.

Why is fieldData null? CrUX only has data for origins with enough real Chrome traffic. Small sites get lab data only — passesCoreWebVitals is then null, because INP cannot be measured in a lab run.

Why does the score differ between two runs of the same URL? Lighthouse is a live measurement on shared hardware; performance scores move a few points between runs. Field data is stable, lab data is directional.

How long does a run take? 10–30 seconds per URL × device, two or three in parallel — about 5–10 minutes per 100 URLs.

Is this legal? The Actor only calls Google's public PageSpeed Insights API and collects no personal data.

Can I export to CSV or Excel? Yes, from the Output tab or the API, and every field is flat except fieldData and topOpportunities.

Part of the webdatatools web-intelligence suite — every Actor is pay-per-event, runs without proxies or a headless browser, and returns one clean row per entity:

Website & domain intelligence

Content for AI, LLMs and RAG

Search, video and social

Leads, jobs and company data

Developer, app and research data

Support and feedback

Missing a metric or an opportunity you need in the row? Open an issue on the Issues tab.