Check Core Web Vitals and Lighthouse scores of web pages
Get Lighthouse performance, SEO and accessibility scores plus Core Web Vitals for a list of pages. Each row has the four Lighthouse scores, LCP, FCP, CLS, TBT and page weight. Run it on a schedule with a monitorId to get alerts when a score drops.
Input
Output fields
Sign up on Apify or log in
The Lighthouse PageSpeed Checker - Core Web Vitals in Bulk Actor is ready to run with the inputs already set for "Check Core Web Vitals and Lighthouse scores of web pages". Sign up or log in and you'll land in Apify Console with a copy of this exact task.
Start the "Check Core Web Vitals and Lighthouse scores of web pages" task
The Lighthouse PageSpeed Checker - Core Web Vitals in Bulk Actor will start running based on the input automatically. You can also change all the input fields, like page urls and strategy, to match your specific use case.
Receive the "Check Core Web Vitals and Lighthouse scores of web pages" output
Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as URL, final url, strategy, and more.
Integrate into your workflow
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Check Core Web Vitals and Lighthouse scores of web pages" task via API.

Integrate "Check Core Web Vitals and Lighthouse scores of web pages" into your workflow
Connect "Check Core Web Vitals and Lighthouse scores of web pages" with 100+ integrations, or run it via API or MCP.
Webhook
n8n
Make
Zapier
Airbyte
Keboola
IFTTT
Hubspot
GDrive
Gmail
Apify MCP
GitHub
Slack
LangChain
LlamaIndex
Flowise
Pinecone
OpenAI
Mastra
Clay
You pay per result: $0.01 per result on the Free plan (about $10.00 per 1,000). Paid Apify plans get lower tiered prices.
Edit urls, strategy (mobile or desktop), categories, monitorId and alertDrop.
Yes. Add this task to an Apify Schedule (for example daily) and read the dataset after each run. This task has no only-new switch, so each run returns the full result for your input.