PageSpeed & Core Web Vitals Monitor (own Google API key)

Bring your own Google API key. You enter your own key for your own run; it is never stored, logged or shown.

Check PageSpeed scores and Core Web Vitals (LCP, INP, CLS) for hundreds of URLs in one run, on mobile and desktop, using your own free Google API key. Turn on monitor mode and schedule it: each run outputs only pages whose scores moved or whose Core Web Vitals status changed.

Not affiliated with or endorsed by Google LLC. PageSpeed Insights and Lighthouse are Google trademarks, named only to describe compatibility.

What does this PageSpeed Insights bulk checker do?

For each URL and device it calls Google's official PageSpeed Insights API v5 and returns one clean row: Lighthouse scores (0-100) for performance, accessibility, best practices and SEO; lab metrics (FCP, LCP, TBT, CLS, Speed Index, TTI, server response time); real-user field data from the Chrome UX Report (p75 LCP, INP, CLS, FCP, TTFB and pass/fail) for the URL or its origin; and the top 5 speed opportunities with estimated savings.

Your Google API key: used only for your run

• You create the key yourself in Google Cloud Console (APIs & Services > Credentials, enable "PageSpeed Insights API"). Google's default quota is often about 25,000 checks a day at no cost; check your own Cloud console Quotas page for the number that applies to your project.
• The key is used only for your run and is sent only to www.googleapis.com (any other API address is refused).
• It is never stored, logged or shown by this Actor: it is not written to the dataset, the key-value store, the monitor memory, logs, status messages or error messages. If Google ever echoes it back in an error, it is masked as ***. Apify keeps the input field encrypted as a secret.
• Tip: restrict the key to the PageSpeed Insights API only.

Core Web Vitals monitor mode

Lab scores wobble a few points between runs, so a URL counts as changed only when a score moves by at least the threshold (default 5 points) or a Core Web Vitals category flips (for example LCP goes from FAST to AVERAGE). Changed rows include changedFields and the previous values. Unchanged URLs are not output and cost less. Use a different monitor name per client or site.

Example output

url	strategy	performanceScore	fieldCwvAssessment	fieldLcpP75	labTbtMs	changeType
https://example.com/pricing	mobile	62	failed	3100	480	changed
https://example.com/	desktop	94	passed	1700	30	new

Pricing

Users on the free Apify plan get up to 100 results per run (then the run stops with a clear status message).

Pay per event: $0.005 per URL audit delivered (one URL on one device), $0.002 per unchanged monitor check. Failed pages and checks blocked by Google quota are never charged. Example: 200 URLs on mobile + desktop checked daily = 400 checks. First run $2.00; a typical day after that with 20 changes = 20 x $0.005 + 380 x $0.002 = $0.86. Free Apify plan users get up to 100 checks per run.

Input

apiKey (required), urls, strategies (mobile/desktop), categories, monitorMode, monitorStateName, scoreChangeThreshold, alertBelowPerformanceScore (sets belowThreshold), maxConcurrency.

FAQ

Why do I need my own key? Google's keyless quota is shared and often exhausted; Google's terms say your credentials identify your own API client, so each user brings their own. How long does a check take? Google runs a real Lighthouse test, usually 10-40 seconds per URL; checks run in parallel. Why is field data empty? The Chrome UX Report only has data for pages with enough real Chrome traffic; the origin-level values are used as a fallback. Can it test pages behind a login or on my local network? No. Only public URLs; private and local addresses are refused.

Is it legal?

It's built to use only public data via Google's official PageSpeed Insights API with your own credentials. It uses Google's official, documented PageSpeed Insights API with your own credentials, under the Google APIs Terms of Service. It tests public pages only and collects no personal data. You are responsible for your own Google Cloud account and quota. This isn't legal advice.

Example input / example output

Example input

{
  "apiKey": "YOUR_GOOGLE_PSI_API_KEY",
  "urls": ["https://example.com/"],
  "strategies": ["mobile"],
  "monitorMode": false
}

Example output (one URL × device)

{
  "url": "https://example.com/",
  "strategy": "mobile",
  "performanceScore": 62,
  "fieldCwvAssessment": "failed",
  "fieldLcpP75": 3100,
  "labTbtMs": 480,
  "changeType": "new"
}

Use it with Make, Zapier, n8n, or AI agents (Apify MCP)

• Make: In Make, add the Apify module, connect your Apify account, then run this Actor (or an Actor task) and map dataset items into your scenario. See Make integration.
• Zapier: In Zapier, use Apify as a trigger (finished Actor/task run) or action (Run Actor / Run Task / Fetch dataset items). See Zapier integration.
• n8n: Install the Apify node, authenticate, then use Run an Actor or Run an Actor and get dataset. See n8n integration.
• AI agents (Apify MCP): Connect your MCP client to https://mcp.apify.com, then use search-actors, fetch-actor-details, and call-actor. Pull results with get-dataset-items. See Apify MCP server.

Related actors: Email Auth Checker · ATS Jobs Feed · SEC Form D Funding Monitor · Texas New Business Entities Feed · Copycat Store & Lookalike Domain Suspect Checker

Disclaimer

Provided as is. Scores come from Google and vary between runs. Not affiliated with or endorsed by Google LLC.