PageSpeed Insights Bulk Checker – Core Web Vitals avatar

PageSpeed Insights Bulk Checker – Core Web Vitals

Pricing

Pay per usage

Go to Apify Store
PageSpeed Insights Bulk Checker – Core Web Vitals

PageSpeed Insights Bulk Checker – Core Web Vitals

Bulk PageSpeed Insights and Lighthouse audits for URLs or a sitemap: mobile/desktop scores, Core Web Vitals (CrUX + lab), top fixes. Uses your free API key.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Innovative Cookie

Innovative Cookie

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

20 hours ago

Last modified

Share

What does PageSpeed Insights Bulk Checker do?

PageSpeed Insights Bulk Checker runs Google PageSpeed Insights / Lighthouse audits for hundreds or thousands of pages in one run. For every URL and device (mobile and/or desktop) you get:

  • Lighthouse scores: Performance, Accessibility, Best Practices, SEO (0–100)
  • Core Web Vitals from real users (Chrome UX Report / CrUX field data): LCP, INP, CLS, FCP, TTFB at p75, for the page and for the whole origin, plus a clear passed / failed assessment
  • Lab metrics: FCP, LCP, TBT, CLS, Speed Index, TTI, server response time, page weight
  • The top opportunities to fix, ranked by estimated savings (e.g. "Improve image delivery – Est savings of 955 KiB")

Paste a list of URLs, or give a sitemap or a domain and the Actor pulls the pages from its sitemap (robots.txt, nested sitemap indexes and .gz supported). It calls the official Google API over HTTP; no browser runs on your side, so runs are cheap.

Why use a bulk PageSpeed checker?

  • SEO audits at scale. Check every template of a site (home, category, product, article) in one go instead of pasting URLs into pagespeed.web.dev one by one.
  • Core Web Vitals monitoring. Schedule a weekly run and export to Google Sheets or a dashboard to track LCP, INP and CLS over time.
  • Client reporting for agencies. Mobile and desktop scores for a whole sitemap in a CSV/Excel file.
  • Before/after deployments. Run on staging and production and compare.
  • Competitor benchmarking. Audit competitor home pages and landing pages side by side.
  • Find what to fix first. Opportunities are sorted by estimated time savings, so developers get a prioritised list.

Google API key: bring your own (free)

The Actor uses your own Google API key (input apiKey, stored as an encrypted secret and never written to logs or results). Google gives each Cloud project a free PageSpeed quota, commonly cited as 25,000 audits per day; check the real figure on your project's Quotas page.

How to get a key (about 2 minutes, free):

  1. Open the Google Cloud console and select or create a project.
  2. Go to APIs & Services → Library, search PageSpeed Insights API, click Enable.
  3. Go to APIs & Services → Credentials → Create credentials → API key. Optionally restrict it to the PageSpeed Insights API.
  4. Paste the key into the Google API key field.

Without a key, the Actor falls back to Google's keyless access, one request every 10 seconds. Google currently sets the shared keyless quota to zero (tested October 2026: every keyless request returns HTTP 429 "Queries per day"), so in practice a key is required. When the keyless quota is unavailable, the Actor stops after the first request with a clear message.

How to run bulk PageSpeed audits

  1. Add page URLs, or a sitemap URL / domain in Sitemaps or domains.
  2. Paste your Google API key.
  3. Choose mobile, desktop or both, and the Lighthouse categories.
  4. Click Start. Results appear in the Output tab; export as CSV, Excel, JSON or HTML.

Input example

{
"apiKey": "AIza...your key...",
"urls": ["https://apify.com", "https://web.dev"],
"sitemapUrls": ["https://vite.dev/sitemap.xml"],
"maxUrlsFromSitemap": 50,
"excludePatterns": ["/tag/", "\\.pdf$"],
"strategies": ["mobile", "desktop"],
"categories": ["performance", "accessibility", "best-practices", "seo"],
"opportunitiesLimit": 5
}

Output example

One row per URL and device:

{
"url": "https://shop.example.org/",
"strategy": "mobile",
"status": "ok",
"performanceScore": 32,
"accessibilityScore": 75,
"bestPracticesScore": 31,
"seoScore": 75,
"coreWebVitals": "failed",
"fieldDataScope": "url",
"fieldLcpMs": 2100,
"fieldInpMs": 260,
"fieldCls": 0.05,
"fieldFcpMs": 1500,
"fieldTtfbMs": 700,
"originCoreWebVitals": "passed",
"labFcpMs": 6795,
"labLcpMs": 10885,
"labTbtMs": 1055,
"labCls": 0.1,
"labSpeedIndexMs": 8296,
"totalByteWeight": 1871037,
"topOpportunity": "Use efficient cache lifetimes (Est savings of 1,791 KiB)",
"opportunities": [
{ "id": "cache-insight", "title": "Use efficient cache lifetimes", "displayValue": "Est savings of 1,791 KiB", "score": 0, "savingsMs": 3600, "savingsBytes": 1834075 },
{ "id": "image-delivery-insight", "title": "Improve image delivery", "displayValue": "Est savings of 955 KiB", "score": 0, "savingsMs": 1200, "savingsBytes": 978394 }
],
"lighthouseVersion": "13.6.0"
}

coreWebVitals uses Google's rule: passed when LCP, INP and CLS are all "good" at the 75th percentile of real users. It reads insufficient-data when some metrics have no data, and no-field-data when the page and its origin have too little Chrome traffic (common for small sites; lab data is still returned). Turn on saveFullReport to keep the complete Lighthouse JSON of each audit in the key-value store.

How much does it cost?

The Actor itself is free to use: there is no Actor fee for now. You only pay the Apify platform usage of your runs (compute units and data transfer), which stays small because the Actor uses plain HTTP requests, without a browser or proxy. The Apify Free plan includes $5 of monthly credit, which covers a lot of test runs.

Google's PageSpeed API is free within the quota of your own key.

Tips

  • Each audit takes Google 10–60 seconds. With a key the Actor runs 4 audits in parallel by default (max 10); 1,000 audits take roughly 1–2 hours.
  • Lighthouse results vary from run to run (network, server load). For decisions, compare several runs or rely on the field data.
  • Use includePatterns to audit one section only (e.g. /products/).

FAQ

Is this the same data as pagespeed.web.dev? Yes. It is the official PageSpeed Insights API v5, which runs the same Lighthouse version and returns the same CrUX field data.

Why is field data empty for my page? CrUX only publishes data for pages and origins with enough real Chrome visits over the last 28 days. Then fieldDataScope is origin (site-level data) or the field columns are empty.

Can I audit pages behind a login or on localhost? No. Google's servers load the page, so it must be publicly reachable. Local and private addresses are rejected.

Does the Actor crawl my site? Only to read sitemaps, with a clear user-agent (PageSpeedBulkAuditor/1.0) and following robots.txt for guessed sitemap locations. The pages themselves are loaded by Google's PageSpeed service.

What happens if my key's quota runs out? The Actor detects the daily-quota error, stops, marks the remaining URLs as skipped, and explains why in the run status. Short-term rate limits are retried automatically.

I found a bug or need a feature. Open an issue in the Issues tab. Issues are usually answered quickly.

The Actor uses Google's public PageSpeed Insights API under your own API key and Google APIs Terms of Service. It reads only public pages and returns no personal data. Only audit sites you have a legitimate reason to test, and keep request volumes reasonable. If unsure, consult a lawyer.

More Actors by the same author (innovative_cookie on Apify):