The OnPage Lighthouse API is a tool that leverages the capabilities of Lighthouse, Google’s open-source project designed to help webmasters access data on the quality and performance of web pages and web apps.
The API runs Lighthouse against a URL you specify and returns the full report as JSON, preserving the field names and structure that the Lighthouse CLI produces. Every request loads the target page once in a clean headless Chrome session, with storage cleared and no warm cache. After that, the target page is scored on performance, accessibility, SEO, and best-practice audits.
Unlike other DataForSEO APIs, the OnPage Lighthouse API features a unified pricing for Standard queue and Live mode. Your account will be billed only for setting a task.
Pricing by mode
| Endpoint | Mode | Turnaround time * | Billing unit | Price |
|---|---|---|---|---|
Lighthouse
/on_page/lighthouse/*
|
Standard queuePOST + GET | Up to 45 minutes on average | Per task | $0.005$5,000 per 1M pages |
| Live modeSingle POST request | Up to 11 seconds on average | Per task | $0.005$5,000 per 1M pages |
Turnaround times are averages and can vary slightly with load and task complexity
FAQ
Questions about OnPage Lighthouse API
Can I simulate a custom device and connection settings?
Yes. By default, Lighthouse models a mid-tier mobile device on a throttled 4G connection, and every response returns the applied configuration in the configSettings object. You can override the default settings by applying additional parameters: the for_mobile parameter switches between the mobile and desktop profiles, while browser_network_throttling_method sets how the connection is throttled. Screen dimensions, user agent, and CPU throttling are also adjustable. You can find the full parameter reference in this Help Center article.
Why does the same page return different scores on repeat runs?
Each request measures a single page load rather than an average across many, so timing metrics such as Largest Contentful Paint and Total Blocking Time shift depending on when individual resources arrive and how busy the main thread is. The page itself also changes between requests through third-party scripts, ad slots, and CDN cache status. For comparable numbers, keep the request parameters identical across runs, pin a specific Lighthouse version with the version parameter, and use the median of several runs rather than a single result.
Does requesting fewer categories or audits reduce the price?
No. Your account is billed per scanned page, so a request returns the same price whether you ask for the full report or a single audit. The categories and audits parameters control the contents of the response, not the cost. You can retrieve the full list of available audit identifiers by using the Lighthouse Audits endpoint for free.
How is the price for Lighthouse API endpoints calculated?
Your account is billed only for setting a task, and the price per scanned page is the same in both modes. Note that a single Task POST call can carry up to 100 tasks, each of which is billed separately, while a Live call carries one.
Given that the price is $0.005 per scanned page in the Standard queue and in the Live mode alike, the price for 1M pages is calculated as follows:
1,000,000 × 0.005 = $5,000