Page Speed Audit (Google Lighthouse) — Performance, SEO & Accessibility Scores

Runs a real Google Lighthouse audit (the same engine behind Chrome DevTools/PageSpeed Insights) on a public page and returns the 4 category scores (0-100), 6 Core Web Vitals metrics, and a prioritized list of what to fix first. No third-party API keys, no login.

What it does

• Launches a real headless Chrome and runs Lighthouse against the given URL.
• Returns 0-100 scores for performance, seo, accessibility and best-practices.
• Returns the key metrics: Largest Contentful Paint, First Contentful Paint, Total Blocking Time, Cumulative Layout Shift, Speed Index and Time to Interactive.
• Returns the 10 lowest-scoring opportunities (score < 0.9), sorted from worst to best, with the real Lighthouse audit id so you can look up the official fix in Lighthouse's documentation.

Who it's for

• Freelancers/agencies that need a speed and technical SEO report before a pitch or after a change.
• Teams that want to run the audit in their own pipeline (CI, pre-deploy) without installing Lighthouse or maintaining Chrome.

Input

Field	Type	Required	Description
url	string	Yes	One page per run (pay-per-event = 1 event per page).
device	string	No (default mobile)	mobile or desktop.
categories	array	No	Subset of performance, seo, accessibility, best-practices. If omitted, runs all 4.

{ "url": "https://example.com", "device": "mobile" }

Output

{
  "url": "https://example.com",
  "device": "mobile",
  "categoriesAudited": ["performance", "seo", "accessibility", "best-practices"],
  "scores": { "performance": 93, "seo": 80, "accessibility": 96, "best-practices": 96 },
  "metrics": {
    "largest-contentful-paint": { "score": 1, "displayValue": "0.8 s", "numericValue": 773.5 },
    "speed-index": { "score": 0.32, "displayValue": "7.0 s", "numericValue": 7031.6 }
  },
  "opportunities": [
    { "id": "meta-description", "title": "Document does not have a meta description", "category": "seo", "score": 0 }
  ],
  "opportunityCount": 6,
  "lighthouseVersion": "13.5.0",
  "auditedAt": "2026-09-20T03:30:55.498Z"
}

Pricing

Pay-per-event, provisional. Starting reference: USD 0.05 per page audited (03-plan.md §2) — this is the most compute-heavy of the 12 Actors (it launches a real browser), so its margin gets extra scrutiny before the final price is set (see build/README.md → "Calibrar precios").

How to call it

curl "https://api.apify.com/v2/acts/cuantic-data~page-speed-lighthouse-audit/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com"}'

Terms and limits

See ./TERMS.md: uses Google Lighthouse (Apache License 2.0), running against the user's own page, with no third-party data involved.

What it does NOT do

• The desktop profile changes the formFactor but doesn't hand-tune every Lighthouse network/CPU throttling setting — disclosed in TERMS.md, not a hidden bug.
• It doesn't fix anything automatically: it gives you the diagnosis, not the fix.
• It can take 15-40 seconds per page (it launches a real browser) — don't use it for very high-frequency monitoring of the same URL.

FAQ

Why does the score shift slightly between runs of the same page? Lighthouse measures real load times; there's normal network and CPU variability between runs, same as with PageSpeed Insights. It's not an Actor error.

Found a bug? Email cuanticwindows@gmail.com — we reply within 72 hours.

---

See build/README.md for how to run tests and publish this Actor.