Bulk PageSpeed & Lighthouse Checker — Core Web Vitals avatar

Bulk PageSpeed & Lighthouse Checker — Core Web Vitals

Pricing

Pay per event

Go to Apify Store
Bulk PageSpeed & Lighthouse Checker — Core Web Vitals

Bulk PageSpeed & Lighthouse Checker — Core Web Vitals

Use this when you need Lighthouse/PageSpeed scores and Core Web Vitals for a page. $0.05/audit (URL x device), or $0.005 with your own Google API key. Input: {"url":"https://example.com"}. Output: performance, accessibility, seo, lab.lcpMs, lab.cls, lab.tbtMs, opportunities, fieldData.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Isaac

Isaac

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

12 hours ago

Last modified

Share

Bulk PageSpeed & Lighthouse Checker: Core Web Vitals for Many URLs

Run Google Lighthouse / PageSpeed Insights audits on hundreds of URLs at once, for mobile and desktop, and get every score and Core Web Vital in one table. You don't need an API key and there's no setup. Paste your URLs and click Start. For each URL and device you get Performance, Accessibility, Best Practices and SEO scores, the lab metrics LCP, CLS, TBT, FCP, Speed Index and TTFB, the top performance opportunities ranked by estimated savings, the failing accessibility, SEO and best-practice checks, and optionally the full shareable Lighthouse HTML report.

Add your own free Google API key and audits run on Google's PageSpeed Insights servers instead. You also get real-user Chrome UX Report (CrUX) field data: p75 LCP, INP, CLS, FCP and TTFB, with Good / Needs improvement / Poor ratings for the page and the whole origin.

Why use it

  • 🚀 Bulk PageSpeed Insights: audit a whole sitemap, a list of competitors or every client site in one run, instead of pasting URLs into pagespeed.web.dev one by one
  • 📱 Mobile and desktop in the same run
  • 🔑 No API key required: Lighthouse 12 runs in headless Chrome inside the Actor. Bring a key only if you want CrUX field data
  • 🧭 Actionable output: top opportunities ("Reduce unused JavaScript, est. savings 1,359 KiB") plus failing a11y and SEO checks
  • 📄 Optional full HTML and JSON Lighthouse reports you can share with developers or clients
  • 🔁 Built for automation: schedule it daily or weekly to monitor Core Web Vitals, or call it from the API, Make, Zapier, n8n or an AI agent
  • 💸 Pay per audit, no subscription. Failed or unreachable pages are free

How to use

  1. Enter your page URLs (the form is prefilled with a working example).
  2. Pick Mobile, Desktop or both. API and agent calls that leave out strategies audit mobile only, which is one audit and the fastest option.
  3. Optionally paste a Google PageSpeed Insights API key to get Google-hosted audits plus real-user CrUX data.
  4. Click Start. Results appear in the Output tab as a table you can export to CSV, Excel or JSON.

Output example

{
"url": "https://apify.com/",
"strategy": "desktop",
"success": true,
"engine": "lighthouse-local",
"performance": 80, "accessibility": 96, "bestPractices": 74, "seo": 85,
"lab": { "lcpMs": 1707, "fcpMs": 606, "cls": 0.003, "tbtMs": 288, "speedIndexMs": 1417, "ttfbMs": 83 },
"opportunities": [
{ "title": "Reduce unused JavaScript", "displayValue": "Est savings of 1,359 KiB", "estimatedSavingsMs": 250, "estimatedSavingsKiB": 1359 }
],
"accessibilityIssues": ["Links rely on color to be distinguishable."],
"seoIssues": ["robots.txt is not valid"],
"fieldData": null,
"lighthouseVersion": "12.8.2"
}

With an API key, fieldData and originFieldData contain the real-user p75 values, for example { "overallCategory": "FAST", "lcpMs": 1900, "inpMs": 120, "clsP75": 0.02, ... }.

Pricing

Pay-per-event with no monthly fee, and platform usage is included: you only pay for successful audits.

EventPrice
Lighthouse audit run by the Actor (no key needed), per URL per device$0.05
PageSpeed Insights audit with your own free Google API key, per URL per device$0.005

Examples:

  • 10 URLs × mobile + desktop, no key: $1.00
  • 100 URLs × mobile + desktop, no key: $10.00
  • The same 200 audits with your own key: $1.00

Unreachable pages, 404s and pages Lighthouse can't load are not charged. Set Maximum cost per run and the Actor stops before exceeding it.

How it compares

Prices are from the Apify Store as of October 2026:

  • Page Speed Analyzer (nexgendata): $0.10 per report.
  • Google PageSpeed Insights API (dev00): $0.10 per query on the Apify Free plan, or $0.002 on paid plans plus platform usage paid by you.
  • This Actor: $0.05 with nothing extra to pay, or $0.005 with your own key. Platform usage is included either way, you get real-user CrUX data, and failed pages are free.

How do I get a free PageSpeed Insights API key?

  1. Open the Google Cloud console and enable the PageSpeed Insights API.
  2. Go to APIs & Services → Credentials → Create credentials → API key.
  3. Paste the key into the API key field. The key is stored as a secret input. Google allows about 25,000 free requests per day per project.

FAQ

How much does it cost? $0.05 per URL per device when the Actor runs Lighthouse for you, or $0.005 per URL per device with your own free Google API key. Platform usage is included and failed pages are free. Auditing one URL on mobile and desktop costs $0.10 without a key or $0.01 with one.

Do I need an API key? No. Without a key, the Actor runs Lighthouse itself in headless Chrome. Google's keyless PageSpeed quota is shared by everyone and is almost always exhausted, so a key is optional. A key makes audits 10× cheaper ($0.005), runs them in parallel on Google's servers and adds real-user CrUX data.

Why do scores differ slightly from pagespeed.web.dev? Lighthouse scores vary between runs and machines, especially Performance. PageSpeed Insights uses Google's own hardware and may run a newer Lighthouse version. For the closest match, use your own API key. For trends, compare runs made with the same engine.

Is INP included? INP is a real-user metric, so it comes from CrUX field data (API key mode) when Google has enough traffic data for the page or origin. Lab runs report Total Blocking Time (TBT), the lab proxy for INP.

Can I audit pages behind a login? No. Only publicly reachable pages can be audited.

How fast is it? A local Lighthouse audit takes about 15–90 seconds depending on page weight. Audits run one at a time so that CPU contention doesn't distort scores. API-key audits run in parallel.

Can I monitor my site over time? Yes. Create a task and schedule it, then compare runs or send the results to Google Sheets or Slack using Apify integrations.

Calling it from an AI agent or a script (async pattern)

A single mobile audit (the default) takes about 20–60 seconds, because a real Lighthouse run loads the whole page. That is often longer than an MCP client waits, so use the pattern below. The Apify MCP server waits only about 30–45 seconds for a run before it returns. So for batches, slow pages, or whenever a call returns before the run is done, start the run and fetch the results afterwards rather than waiting on it:

  1. Start the run: POST https://api.apify.com/v2/acts/poised_beardlichen~pagespeed-lighthouse-checker/runs with input such as {"url": "https://example.com"}. The response contains data.id (the run ID) and data.defaultDatasetId.
  2. Wait for it to finish: poll GET https://api.apify.com/v2/actor-runs/<runId>?waitForFinish=60 until status is SUCCEEDED.
  3. Fetch the results: GET https://api.apify.com/v2/datasets/<defaultDatasetId>/items?clean=true.

Send your token as Authorization: Bearer <APIFY_TOKEN>. Through MCP, if the call returns a run ID instead of results, use the server's run-status and dataset tools (e.g. get-actor-run, then get-dataset-items) with that ID. For small, quick jobs you can use the synchronous endpoint POST /v2/acts/poised_beardlichen~pagespeed-lighthouse-checker/run-sync-get-dataset-items instead, which waits for up to 300 seconds.

Other tools by us

Support

Something not working for a particular URL? Open an issue on the Issues tab and include the URL.