Quality
Run Lighthouse
Lighthouse runs in-process against a real Chrome instance, so a run reflects the same rendering engine Chrome-based audits use elsewhere.
How it works
- Each run scores performance, accessibility, best practices, and SEO
- A concurrency cap limits how many Lighthouse runs execute at once, protecting the worker under load
- Chrome's binary path is configured via an environment variable so the worker can locate a compatible browser
Good to know
- Because Lighthouse needs a real browser, it's noticeably heavier than the lightweight public audit endpoint