PageSpeed Insights & Core Web Vitals Checker - Bulk, $3/1K avatar

PageSpeed Insights & Core Web Vitals Checker - Bulk, $3/1K

Pricing

from $2.00 / 1,000 page audit (pagespeed insights api)s

Go to Apify Store
PageSpeed Insights & Core Web Vitals Checker - Bulk, $3/1K

PageSpeed Insights & Core Web Vitals Checker - Bulk, $3/1K

Run Google Lighthouse on hundreds of URLs: performance, accessibility, best-practices and SEO scores, LCP, CLS, INP field data, top fixes and page weight. Mobile and desktop. $3 per 1,000 audits with a free Google key.

Pricing

from $2.00 / 1,000 page audit (pagespeed insights api)s

Rating

0.0

(0)

Developer

Plot Point Technologies

Plot Point Technologies

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 days ago

Last modified

Categories

Security

Limited permissions

Share

Bulk PageSpeed Insights & Core Web Vitals Checker

Run Google Lighthouse, the engine behind PageSpeed Insights, on a whole list of pages. Test each page on mobile, desktop or both and get one row per page and device with the four Lighthouse scores, Core Web Vitals lab metrics, real-user field data (LCP, INP, CLS) when Google has it, the biggest improvement opportunities with estimated savings, and page weight. From $3 per 1,000 audits.

What can this PageSpeed checker do?

  • Audit hundreds of URLs in one run, on mobile, desktop or both.
  • Two engines:
EnginePriceWhat it does
PageSpeed Insights API (psi)$3 per 1,000 auditsUses Google's official PageSpeed Insights API with your free Google API key. Results match pagespeed.web.dev and include Chrome UX Report field data.
Local Lighthouse (local)$25 per 1,000 auditsRuns Lighthouse inside the tool in headless Chrome. No key or Google quota needed.

auto (default) uses PSI when you enter a key and local Lighthouse otherwise.

  • Choose categories: performance, accessibility, best practices, SEO.
  • Get fixes, not just scores: the top opportunities (for example "Properly size images") with estimated savings, and optionally every failed audit.

What data do you get?

FieldDescription
url, finalUrl, strategyPage and device
performanceScore, accessibilityScore, bestPracticesScore, seoScore0 to 100
lcpMs, cls, tbtMs, fcpMs, speedIndexMs, ttiMs, serverResponseMsLab metrics
totalByteWeight, requestCount, domSize, resourceSummaryPage weight
opportunities, failedAuditsWhat to fix, with estimated savings
fieldLcpMs, fieldInpMs, fieldCls, fieldFcpMs, fieldTtfbMs, fieldCoreWebVitalsPassed, fieldDataScopeReal-user field data (PSI engine)
engine, lighthouseVersion, warnings, auditDurationSecs, checkedAtRun details

Who uses it?

  • SEO agencies and consultants checking client sites or prospect lists in bulk.
  • Web developers and QA teams tracking performance before and after releases.
  • Marketing and e-commerce teams monitoring landing and product pages on a schedule.
  • Site owners comparing their pages with competitors'.

How to use it

  1. Get a free Google API key (about 2 minutes): open the PageSpeed Insights API page in Google Cloud Console, click Enable, then APIs & Services > Credentials > Create credentials > API key. Google's free quota is 25,000 requests a day; no billing account is needed.
  2. Click Try for free (or Start) and paste your URLs and the Google API key.
  3. Choose Devices and Lighthouse categories.
  4. Run it and export to Excel, CSV or JSON, or connect the dataset to a dashboard.
  5. Schedule it weekly to watch Core Web Vitals over time.

Input example

{
"urls": [
"https://www.wikipedia.org/",
"https://www.bbc.com/"
],
"engine": "auto",
"strategies": [
"mobile",
"desktop"
],
"categories": [
"performance",
"accessibility",
"best-practices",
"seo"
],
"maxOpportunities": 5
}

Output example

{
"url": "https://www.wikipedia.org/",
"finalUrl": "https://www.wikipedia.org/",
"strategy": "mobile",
"performanceScore": 83,
"accessibilityScore": 95,
"bestPracticesScore": 100,
"seoScore": 100,
"lcpMs": 1745,
"cls": 0.001,
"tbtMs": 673,
"fcpMs": 1187,
"speedIndexMs": 1793,
"ttiMs": 2152,
"serverResponseMs": 41,
"totalByteWeight": 101333,
"requestCount": 6,
"domSize": 1177,
"resourceSummary": [
{
"type": "Image",
"requests": 2,
"transferBytes": 57767
},
{
"type": "Document",
"requests": 1,
"transferBytes": 30223
},
{
"type": "Script",
"requests": 2,
"transferBytes": 11485
}
],
"opportunities": [
{
"id": "uses-responsive-images",
"title": "Properly size images",
"estimatedSavingsMs": 150,
"estimatedSavingsBytes": 35155,
"displayValue": "Est savings of 34 KiB"
},
{
"id": "modern-image-formats",
"title": "Serve images in next-gen formats",
"estimatedSavingsMs": 0,
"estimatedSavingsBytes": 20421,
"displayValue": "Est savings of 20 KiB"
}
],
"lighthouseVersion": "12.8.2",
"benchmarkIndex": 1620,
"warnings": [],
"fetchTime": "2026-10-28T19:27:16.059Z",
"engine": "local",
"auditDurationSecs": 32.7,
"checkedAt": "2026-10-28T19:27:44.006Z"
}

How much does it cost?

EnginePrice per auditPer 1,000 audits
PageSpeed Insights API (your free key)$0.003$3
Local Lighthouse (no key)$0.025$25

Plus a $0.00005 start fee per run. One audit = one URL on one device. Examples with the PSI engine: 100 pages on mobile and desktop (200 audits) cost $0.60; a weekly check of 500 pages on mobile for a month (about 2,150 audits) costs about $6.50. Pages that cannot be loaded and API errors (invalid key, used-up quota) are not charged.

Volume discounts on higher Apify plans. The prices above are for the Apify Free plan; on paid plans the per-audit price drops automatically (PSI audits go down to $2 per 1,000 on Gold and above).

Use it via API, Make, Zapier, n8n or an AI agent

Apify API. Start a run and get the results back in one HTTP request (replace YOUR_API_TOKEN with the token from Apify Console > Settings > Integrations):

curl -X POST "https://api.apify.com/v2/acts/plotpointtech~bulk-pagespeed-lighthouse/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{"urls": ["https://www.wikipedia.org/", "https://www.bbc.com/"], "engine": "auto", "strategies": ["mobile", "desktop"], "categories": ["performance", "accessibility", "best-practices", "seo"], "maxOpportunities": 5}'

For longer jobs, start the run asynchronously and read the dataset when it finishes. Official apify-client libraries exist for Python and JavaScript; the API tab on this page has ready-made code.

No-code automation. Connect the tool to Make, Zapier, n8n, Google Sheets, Slack, Airtable or any webhook with Apify integrations, and use Schedules in Apify Console to run it hourly, daily or weekly.

AI agents (MCP). Give Claude, ChatGPT, Cursor, VS Code or any MCP-compatible agent direct access to this tool through the hosted Apify MCP server. Add this server URL to your client:

https://mcp.apify.com?tools=plotpointtech/bulk-pagespeed-lighthouse

The agent can then call the tool with the same input fields shown above and read the results.

FAQ

Is it legal to run PageSpeed audits on any website? The tool loads each page as a normal visitor would, or asks Google's official API to do so. Only test pages you are allowed to test, and keep volumes reasonable for sites you do not own.

Why do my local scores differ from pagespeed.web.dev? Lab scores vary between runs and machines. PageSpeed Insights runs on Google's hardware; use the PSI engine when you need matching numbers, and keep settings the same when comparing over time.

Can I use it without a Google API key? Yes, with the local Lighthouse engine. PSI also works without a key, but Google's shared keyless quota is small and often used up.

Why is field data missing? Field data comes from the Chrome UX Report and exists only for pages or origins with enough Chrome traffic. If the page has none, the origin's data is used; fieldDataError explains when neither exists.

How long does an audit take? Roughly 15 to 60 seconds per page. The PSI engine runs up to 10 audits in parallel.

Plot Point Technologies is not affiliated with Google.


If this tool saved you time, we would be grateful for a short review on this page; it helps other people find it. If something did not work as expected, please open an issue on the Issues tab and we will look into it quickly.