Lighthouse Audit & Performance Budgets (CI-ready)
Pricing
from $25.00 / 1,000 lighthouse audit runs
Lighthouse Audit & Performance Budgets (CI-ready)
Run real Google Lighthouse on public URLs (no API key, no PageSpeed quota): performance, accessibility, best-practices and SEO scores, Core Web Vitals, top fixes, mobile + desktop, median of up to 3 runs, pass/fail performance budgets for CI, and an AI-ready summary. Failed audits are free.
Pricing
from $25.00 / 1,000 lighthouse audit runs
Rating
0.0
(0)
Developer
Jerry Lin
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Features
Share
What does Lighthouse Audit & Performance Budgets do?
It runs real Google Lighthouse in Chrome on Apify – the same engine behind PageSpeed Insights and Chrome DevTools – for a list of public URLs and returns one clean row per URL and device:
- 📊 Scores 0–100 for performance, accessibility, best practices and SEO
- ⚡ Core Web Vitals lab metrics – LCP, CLS, TBT, FCP, Speed Index, TTI, server response time – with
good / needs-improvement / poorratings - 🛠️ Top fixes with estimated time and byte savings, plus failed accessibility / SEO / best-practice checks
- 📱🖥️ Mobile and desktop in the same run
- 🎯 Median of up to 3 runs – Lighthouse scores jump between runs; the median run is reported together with the min–max range
- ✅ Performance budgets for CI/CD – set min performance 90, max LCP 2500 ms, max CLS 0.1… Each row gets
budgetPassed+ human-readablebudgetFailures, and the run can fail on purpose so your pipeline blocks the deploy - 🗺️ Audit a whole site – optionally pull pages from the site's sitemap
- 🤖 AI-agent ready –
OUTPUT_SUMMARYwith averages, worst pages, most common fixes and a one-paragraphllmSummary; works through the Apify MCP server
No Google API key, no PageSpeed Insights quota. Pages that cannot be audited (robots.txt disallow, 404, PDFs, errors) return a free row that says why.
How to use it
- Add the URLs to audit.
- Pick devices (mobile, desktop) and categories.
- Optional: set budgets and turn on Fail the run when a budget fails for CI.
- Click Start. Open the Scores and Fixes tables, or
OUTPUT_SUMMARY. - Schedule it daily/weekly or call it from GitHub Actions after each deploy via the Apify API.
Example input (CI budget)
{"urls": ["https://example.com/", "https://example.com/pricing"],"devices": ["mobile", "desktop"],"runsPerUrl": 3,"minPerformance": 90,"maxLcpMs": 2500,"maxCls": "0.1","failRunIfBudgetFails": true}
Example output row
{"url": "https://example.com/","device": "mobile","status": "ok","performance": 86, "accessibility": 98, "bestPractices": 100, "seo": 92,"lcpMs": 2890, "tbtMs": 140, "cls": 0.03,"ratings": { "lcp": "needs-improvement", "cls": "good", "tbt": "good", "fcp": "good" },"budgetPassed": false,"budgetFailures": ["performance 86 < 90", "LCP 2890ms > 2500ms"],"opportunities": [{ "title": "Eliminate render-blocking resources", "savingsMs": 450 }],"runs": 3, "performanceRange": [84, 89]}
Polite and compliant
- ✅ robots.txt honored – disallowed URLs are not audited (and not charged).
- ✅ One audit at a time, with a pause between audits (default 3 s, minimum 1 s) – a Lighthouse run loads a page like one normal visitor.
- ✅ Public pages only – no login, cookies or CAPTCHA solving.
How much does it cost?
Pay-per-event pricing – no subscription, no separate compute bill:
| Event | Price |
|---|---|
audit-run – one successful Lighthouse run (one URL × one device × one run) | $0.025 |
| Actor start (per GB of memory; default 4 GB = 4 events) | $0.001 |
Examples: 10 URLs on mobile ≈ $0.25; 10 URLs on mobile + desktop ≈ $0.50. Failed, robots-blocked and non-HTML URLs are free. With runsPerUrl: 3 you pay for three runs, so keep it at 1 for quick checks. Set a max cost per run and the Actor stops cleanly at the limit.
Use it from AI agents (MCP)
https://mcp.apify.com?tools=rationalistic_tail/lighthouse-budget-auditor
An agent can ask "How fast is example.com on mobile and what should I fix first?" and read OUTPUT_SUMMARY.llmSummary. Runs with limited permissions, so prepaid agent tokens (Apify AGI, x402) work.
FAQ
Why do scores differ from PageSpeed Insights? Both use Lighthouse lab data, but hardware and network location differ. Use the same Actor (and runsPerUrl: 3) for consistent trends. Keep the default 4096 MB memory: on Apify, CPU scales with memory, and less CPU makes mobile performance scores look worse than they are (each row reports Lighthouse's benchmarkIndex).
Does it include real-user (CrUX) data? No – it measures lab data in Chrome. INP needs real interactions, so TBT is the lab proxy.
Lighthouse version? Pinned (currently 12.8.x) and reported in every row as lighthouseVersion.