PageSpeed Insights Bulk Checker (Core Web Vitals)

Run Google PageSpeed Insights on hundreds of URLs in one go and get a clean table: Lighthouse performance (and optionally SEO, accessibility, best-practices) scores, lab metrics, and real-user Core Web Vitals from the Chrome UX Report — LCP, INP, CLS, FCP, TTFB — for mobile and desktop. Schedule it to keep a score history and flag regressions.

What it does

• Calls the official PageSpeed Insights API v5 for each URL and device.
• Returns 0–100 category scores, lab metrics (LCP, FCP, CLS, TBT, Speed Index, server response time) and field data (URL-level and origin-level p75 values with FAST/AVERAGE/SLOW ratings).
• History and regressions: with Compare with previous run on, each row carries the previous score, the change, and a regression flag when the score drops by your threshold or more.
• Runs four audits in parallel with your key; stops at once on an invalid key or an exhausted quota instead of burning through the list.

Typical uses: monthly performance reports for client sites, checking templates across a large site, catching regressions after deploys.

How to use

1. Create a free Google API key: Google Cloud Console → APIs & Services → enable PageSpeed Insights API → Credentials → API key. No billing needed.
2. Paste your URLs and the key.
3. Choose mobile and/or desktop and the extra categories you want.
4. Run, or schedule it (e.g. weekly) with Compare with previous run on to track scores over time.
5. Export the table as CSV, Excel or JSON, call the Actor through the Apify API, or send results to your tools with Apify integrations.

Input

Field	Description
urls	Pages to audit (required).
googleApiKey	Your Google API key (secret; strongly recommended).
mobile, desktop	Devices to audit (mobile on by default).
includeSeo, includeAccessibility, includeBestPractices	Extra Lighthouse categories.
compareWithPrevious, regressionThreshold	Score history and regression flag (default 5 points).
locale	Locale for formatted values.

{ "urls": ["https://example.com"], "googleApiKey": "••••••", "desktop": true, "includeSeo": true }

Output

One row per URL and device (illustrative values):

{
  "url": "https://example.com/",
  "strategy": "mobile",
  "status": "ok",
  "performanceScore": 100,
  "seoScore": 80,
  "lab": { "lcpMs": 1520, "fcpMs": 980, "cls": 0.002, "tbtMs": 30, "speedIndexMs": 1101, "serverResponseMs": 120 },
  "field": { "overallCategory": "FAST", "lcpMs": 1900, "lcpCategory": "FAST", "inpMs": 120, "cls": 0.02, "fcpMs": 1100, "ttfbMs": 700 },
  "lighthouseVersion": "12.8.2",
  "previousPerformanceScore": 96,
  "scoreDelta": 4,
  "regression": false
}

Rows with status quota_exhausted, rate_limited, invalid_key, skipped or error are free.

Pricing

Event	Price	Per 1,000	Charged when
audit	$0.003	$3.00	One URL is audited on one device

A URL audited on mobile and desktop counts as two audits. Failed audits, quota and key errors are free.

How much does a bulk PageSpeed check cost?

• 100 URLs on mobile: $0.30.
• 500 URLs on mobile and desktop (1,000 audits): $3.00.
• Google does not charge for the PageSpeed Insights API within your key's daily quota. Apify adds its standard small run-start fee.

Set a maximum cost per run in the run options: the Actor checks it before starting each audit and stops before going over it.

FAQ

Do I need a Google API key?

In practice, yes. Google's shared keyless quota was at 0 queries a day when we checked on 2026-10-14, so keyless runs return free quota_exhausted rows. A key is free and takes a few minutes to create (see How to use).

What is the difference between lab and field data?

Lab data (lab) comes from one Lighthouse run in Google's data centre. Field data (field, originField) is the 75th percentile of real Chrome users over 28 days from the Chrome UX Report, and exists only for pages and sites with enough traffic.

How do I monitor Core Web Vitals over time?

Turn on Compare with previous run and schedule the Actor. Each row then carries previousPerformanceScore, scoreDelta and a regression flag when the score drops by your threshold or more.

Why did the run stop after the first URL?

The first audit runs alone: an invalid key or an exhausted quota stops the run there, with a free row explaining why, instead of failing every URL.

Limits

• Use your own key. Without one, requests go to Google's shared keyless quota; on 2026-10-14 that quota answered HTTP 429 "Queries per day" with a limit of 0, so keyless runs usually return quota_exhausted rows (free). A key gives your Google Cloud project its own daily quota (commonly 25,000 audits a day).
• Each audit takes Google 10–30 seconds; with a key the Actor runs four at a time, so 1,000 audits take roughly 1–2 hours.
• Field data exists only for pages and origins with enough Chrome traffic; otherwise field is null. Google says CrUX data in this API will eventually be retired in favour of the CrUX API.

Data source

• PageSpeed Insights API v5, https://www.googleapis.com/pagespeedonline/v5/runPagespeed — https://developers.google.com/speed/docs/insights/v5/get-started and https://developers.google.com/speed/docs/insights/v5/reference/pagespeedapi/runpagespeed, read on 2026-10-14 (parameters url, strategy, category, locale, key; "a key is recommended for frequent, automated queries"). Keyless quota behaviour observed with one live call on 2026-10-14.

Privacy

Only the URLs you submit and your key are processed; the key is used for this run's requests and never logged or stored.

Support

Open an issue on the Actor's Issues tab; issues are answered within a few days and fixed within 14 days.