# Changelog of Lighthouse Audit API: Core Web Vitals and Performance Scores (`rowcraft/lighthouse-performance-audit`) Actor

- **URL**: https://apify.com/rowcraft/lighthouse-performance-audit/changelog.md
- **Full Actor documentation**: https://apify.com/rowcraft/lighthouse-performance-audit.md

## Changelog

### 1.0.2 (2026-10-19)

- README: platform usage is included in the price (pay per event); list of Rowcraft actors updated

### 1.0.1 (2026-10-18)

- README: real screenshots of the input form and of a run's results; example rows taken from a platform run.

### 1.0.0 (2026-10-18)

- First release: Lighthouse 12 run in a headless Chrome on the pages you list, one audit at a time. robots.txt is read first (also for redirect targets), the page is checked for anti-bot and error answers, then Lighthouse scores it.
- One row per page and device: Performance, Accessibility, Best Practices and SEO scores (0 to 100), First Contentful Paint, Largest Contentful Paint, Total Blocking Time, Cumulative Layout Shift, Speed Index, Time to Interactive, server response time, total bytes, request count, the five biggest time savings, the ids of the failed audits, the link to the full HTML report in the key-value store of the run, the Lighthouse version and the time of the audit.
- Device mobile (default), desktop or both (two rows per page, charged as two pages); categories can be limited; `alertBelowPerformance` lists the pages under a Performance score in the notification and in the run summary.
- `COVERAGE` per page and device (ok, blocked, robots_disallowed, not_found, timeout, error, not_checked, with the reason); anti-bot pages, robots.txt refusals, missing pages, timeouts (90 seconds per page) and invalid entries are never charged; the run stops after 10 anti-bot pages in a row.
- Standard Rowcraft automation: only pages whose scores changed since the last run (`onlyNew`, `stateName`), end-of-run notification (`notifyUrl`), charge cap respected, stop before the run timeout with the summary saved, one request per second by default to the same site (minimum 250 ms).