PageSpeed and Core Web Vitals Auditor

Audit Core Web Vitals and PageSpeed scores for many pages in one run. Give it a list of URLs, a sitemap, or both. Each page comes back as one row, with mobile and desktop side by side, a pass or fail against Google's Core Web Vitals thresholds, and a short list of what to fix first.

Not legal advice; general information only.

Who it is for

Developers, SEO consultants and agencies who need a repeatable performance check after a release, a template change, or as a scheduled watch on the pages that matter.

What you get

• A list of page URLs, a sitemap URL, or both. Large sitemaps are limited by Max URLs.
• Mobile, desktop, or both. Both devices are stored in the same row.
• For each successful audit: performance score, LCP, INP when field data exists, Total Blocking Time from the lab audit, CLS, FCP, TTFB, and a pass or fail.
• Field data for the page when Google has it, otherwise field data for the origin when that is available.
• The top opportunities, ranked by estimated time saved.
• A run summary with a fix-these-first list. Pages that fail Core Web Vitals come first, then the lowest scores.
• Optional comparison with the previous run. Pages whose score dropped, or whose Core Web Vitals pass became a fail, are flagged.
• Private and internal addresses are skipped and are not charged.

Tutorial

1. Paste page URLs into Page URLs, or set Sitemap URL, or use both.
2. Choose Devices. both is the default and writes mobile and desktop into one row. Each device is charged on its own.
3. Set Max URLs to the budget you want. With both devices, 10 pages where both checks succeed cost $0.10 with the key supplied with the Actor, or $0.04 with your own key, plus the start fee.
4. Google API key is optional. Leave it empty to use the key supplied with the Actor. The price is $0.005 per page per device, so checking both mobile and desktop costs $0.01 per page. Add your own free Google PageSpeed API key and the price is $0.002 per page per device, so both devices cost $0.004 per page.
5. Leave Concurrency at 2 unless you know your quota can take more.
6. To compare with last time, turn on Compare with the previous run and keep the same store name and record key for that site.
7. Run the Actor. Open the dataset for each page, and the OUTPUT record for the summary and the fix-these-first list.
8. Schedule the task if you want a standing check. Failed audits are not charged.

Client-ready report

Use this when you want one file to send to a client. It is off by default. Off does not add a file and does not add a fee.

1. Add the pages or the sitemap you want to audit.
2. Set Client-ready report to HTML.
3. Run the Actor.
4. Open the Output tab. Client report (HTML) is REPORT.html in the key-value store. Client report summary lists that key.

The page has a cover with the site, the date and a performance grade, a short summary in plain language, and a table of findings. Each finding says what it means and how to fix it. Pages from more than one site are grouped by site. Pass, warning and fail stay readable in black and white. The footer says Generated with PageSpeed and Core Web Vitals Auditor.

The report fee is charged once per run, and only after the file is saved. A failed save is not charged. The dataset stays priced as below. This Actor saves HTML. It does not save a PDF.

Example input

{
  "urls": ["https://example.com/", "https://example.com/pricing"],
  "sitemapUrl": "https://example.com/sitemap.xml",
  "devices": "both",
  "maxUrls": 20,
  "concurrency": 2,
  "trackChanges": true,
  "changesKey": "example.com"
}

Leave googleApiKey out of shared examples. It is a secret input and is not written to the dataset.

Example output

One dataset row per page:

{
  "url": "https://example.com/",
  "keySource": "user",
  "coreWebVitalsPassed": true,
  "mobileScore": 91,
  "desktopScore": 98,
  "mobile": {
    "performanceScore": 91,
    "lcpMs": 1800,
    "lcpRating": "good",
    "inpMs": 150,
    "inpRating": "good",
    "tbtMs": 80,
    "cls": 0.04,
    "clsRating": "good",
    "fcpMs": 900,
    "ttfbMs": 120,
    "coreWebVitalsPassed": true,
    "opportunities": [
      { "id": "unused-javascript", "title": "Reduce unused JavaScript", "savingsMs": 400 }
    ]
  },
  "desktop": {
    "performanceScore": 98,
    "coreWebVitalsPassed": true
  },
  "regressed": false
}

keySource is user when you supplied the Google API key, and actor when the key supplied with the Actor was used. The key itself is never included.

The OUTPUT record holds fixFirst, audit counts, and changes when comparison is on. changes.regressions lists pages that got worse. Pages that were simply not part of this run are not treated as removed.

Pricing

You pay a small start fee, then one fee for each successful audit. One audit is one page on one device. With the key supplied with the Actor, the price is $0.005 per page per device, so checking both mobile and desktop costs $0.01 per page. With your own API key, the price is $0.002 per page per device, so both devices cost $0.004 per page. A failed audit is free. A skipped private address is free.

What	Price
Run started	$0.00005
Successful audit with your API key, per page per device	$0.002
Successful audit with the key supplied with the Actor, per page per device	$0.005
Both devices on one page, your API key (two audits in total)	$0.004
Both devices on one page, key supplied with the Actor (two audits in total)	$0.01
Client-ready report, once per run, only when the file is saved	$0.03

Examples

• 10 pages, mobile only, your key: 10 × $0.002 = $0.02, plus the $0.00005 start fee.
• 10 pages, mobile only, the key supplied with the Actor: 10 × $0.005 = $0.05, plus the start fee.
• 10 pages, both devices, your key: 10 × $0.004 = $0.04, plus the start fee.
• 10 pages, both devices, the key supplied with the Actor: 10 × $0.01 = $0.10, plus the start fee.
• A page that fails to load, or a request Google rejects, is not charged. A page where only one device succeeds is charged for that device only.

Integrations and scheduling

Save the input as an Apify task and schedule it daily or weekly. Use the same changes key so each run can flag regressions. The dataset and the OUTPUT record are available from the Apify API and from webhooks, so you can post a summary to Slack or email when a page regresses. Export the dataset as JSON or CSV.

FAQ

What does pass or fail mean?

A device passes when LCP, INP and CLS are all in Google's "good" range. The page passes when every device you requested passes. If a metric was not measured, the pass flag is empty rather than a guess.

What are the thresholds?

These are Google's published Core Web Vitals ranges.

• LCP: good at 2.5 seconds or less, needs improvement up to 4 seconds, poor above 4 seconds.
• INP: good at 200 milliseconds or less, needs improvement up to 500 milliseconds, poor above 500 milliseconds.
• CLS: good at 0.1 or less, needs improvement up to 0.25, poor above 0.25.

Why is INP sometimes empty?

INP comes from field data, which is measured on real visits. The lab audit does not produce INP. It reports Total Blocking Time instead, in tbtMs. When field data has no INP, the Core Web Vitals pass flag is empty and the lab numbers are still saved.

Where does field data come from?

From the page when Google has enough visits for that URL. Otherwise from the origin, when that is available. field.scope is url or origin.

Which key is used?

Google API key is optional. Leave it empty to use the key supplied with the Actor. The price is $0.005 per page per device, so checking both mobile and desktop costs $0.01 per page. Add your own free Google PageSpeed API key and the price is $0.002 per page per device, so both devices cost $0.004 per page. The key is not stored in the dataset, the summary, or the log.

Are failed audits charged?

No. A timeout, a rate limit that still fails, a quota error, or a page that does not load is stored with an error and is not charged. If you asked for both devices and only one succeeds, you pay for that device only.

Will you keep my page content?

No. Page bodies, screenshots and the raw audit payload are not stored.

No personal data

This Actor does not collect personal data.

• Page HTML, screenshots and raw responses are discarded.
• Email addresses, phone numbers and secret query parameters are removed before a page is sent for audit, and again before anything is stored.
• The API key is never written to results or logs.
• Change tracking stores the page URL, the scores and the pass flag. It does not store page content.
• Private and internal addresses are not requested.

Next additions

• Agency white-label logo
• Dutch report