Lighthouse Audit — Lab Web Vitals and Scores, Mobile & Desktop avatar

Lighthouse Audit — Lab Web Vitals and Scores, Mobile & Desktop

Pricing

from $9.60 / 1,000 lighthouse audit runs

Go to Apify Store
Lighthouse Audit — Lab Web Vitals and Scores, Mobile & Desktop

Lighthouse Audit — Lab Web Vitals and Scores, Mobile & Desktop

Lighthouse — Mobile/Desktop Lab Audits, Scores & Fix Hints: `lighthouse-audit` previous $0.012 / requested $0.024; active Apify record sets fees; usage included; start extra; failed results uncharged.

Pricing

from $9.60 / 1,000 lighthouse audit runs

Rating

0.0

(0)

Developer

Logan Parker

Logan Parker

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Features

Limited permissions

Share

Lighthouse audits public pages for mobile, desktop or both, returning performance, accessibility, best-practices and SEO scores, lab timing metrics and failing audits with fix hints; these are lab measurements, not field-user data. AI agents can call and pay through Apify MCP.

The active Apify pricing record determines your bill; for the previous/requested schedules, lighthouse-audit previous $0.012 / requested $0.024; usage is included and failed results are free.

Example result

Example record for the minimal input under How to use it, as this Actor returned it on 2026-10-18 in a run of its production image; the record is kept unchanged with the release.

{
"url": "https://docs.apify.com/platform/actors/publishing/monetize",
"finalUrl": "https://docs.apify.com/actors/publishing/monetize",
"ok": true,
"formFactor": "mobile",
"scores": {
"performance": 44,
"accessibility": 93,
"bestPractices": 75,
"seo": 92
},
"metrics": {
"fcpMs": 2276.2038199999997,
"lcpMs": 5706.97198,
"tbtMs": 4802.846080000004,
"cls": 0,
"speedIndexMs": 4236.38681757417
},
"failedAudits": [
{
"title": "First Contentful Paint",
"score": 0.75,
"displayValue": "2.3 s",
"description": "First Contentful Paint marks the time at which the first text or image is painted. [Learn more about the First Contentful Paint metric](https://developer.chrome.com/docs/lighthouse/performance/first-contentful-paint/).",
"id": "first-contentful-paint"
},
{
"title": "Largest Contentful Paint",
"score": 0.16,
"displayValue": "5.7 s",
"description": "Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn more about the Largest Contentful Paint metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-largest-contentful-paint/)",
"id": "largest-contentful-paint"
},
{
"title": "Speed Index",
"score": 0.77,
"displayValue": "4.2 s",
"description": "Speed Index shows how quickly the contents of a page are visibly populated. [Learn more about the Speed Index metric](https://developer.chrome.com/docs/lighthouse/performance/speed-index/).",
"id": "speed-index"
},
{
"title": "Total Blocking Time",
"score": 0,
"displayValue": "4,800 ms",
"description": "Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. [Learn more about the Total Blocking Time metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-total-blocking-time/).",
"id": "total-blocking-time"
},
{
"title": "Max Potential First Input Delay",
"score": 0,
"displayValue": "1,310 ms",
"description": "The maximum potential First Input Delay that your users could experience is the duration of the longest task. [Learn more about the Maximum Potential First Input Delay metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-max-potential-fid/).",
"id": "max-potential-fid"
},
{
"title": "Browser errors were logged to the console",
"score": 0,
"displayValue": null,
"description": "Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. [Learn more about this errors in console diagnostic audit](https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console/)",
"id": "errors-in-console"
},
{
"title": "Time to Interactive",
"score": 0,
"displayValue": "33.9 s",
"description": "Time to Interactive is the amount of time it takes for the page to become fully interactive. [Learn more about the Time to Interactive metric](https://developer.chrome.com/docs/lighthouse/performance/interactive/).",
"id": "interactive"
},
{
"title": "Avoid multiple page redirects",
"score": 0,
"displayValue": "Est savings of 760 ms",
"description": "Redirects introduce additional delays before the page can be loaded. [Learn how to avoid page redirects](https://developer.chrome.com/docs/lighthouse/performance/redirects/).",
"id": "redirects"
},
{
"title": "Uses third-party cookies",
"score": 0,
"displayValue": "19 cookies found",
"description": "Third-party cookies may be blocked in some contexts. [Learn more about preparing for third-party cookie restrictions](https://privacysandbox.google.com/cookies/prepare/overview).",
"id": "third-party-cookies"
},
{
"title": "Minimize main-thread work",
"score": 0,
"displayValue": "10.7 s",
"description": "Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to minimize main-thread work](https://developer.chrome.com/docs/lighthouse/performance/mainthread-work-breakdown/)",
"id": "mainthread-work-breakdown"
},
{
"title": "Reduce JavaScript execution time",
"score": 0,
"displayValue": "8.0 s",
"description": "Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time](https://developer.chrome.com/docs/lighthouse/performance/bootup-time/).",
"id": "bootup-time"
},
{
"title": "Preconnect to required origins",
"score": 0,
"displayValue": "Est savings of 140 ms",
"description": "Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. [Learn how to preconnect to required origins](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/).",
"id": "uses-rel-preconnect"
},
{
"title": "Ensure text remains visible during webfont load",
"score": 0.5,
"displayValue": null,
"description": "Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. [Learn more about `font-display`](https://developer.chrome.com/docs/lighthouse/performance/font-display/).",
"id": "font-display"
},
{
"title": "Reduce the impact of third-party code",
"score": 0,
"displayValue": "Third-party code blocked the main thread for 4,630 ms",
"description": "Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. [Learn how to minimize third-party impact](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/).",
"id": "third-party-summary"
},
{
"title": "Some third-party resources can be lazy loaded with a facade",
"score": 0.5,
"displayValue": "1 facade alternative available",
"description": "Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. [Learn how to defer third-parties with a facade](https://developer.chrome.com/docs/lighthouse/performance/third-party-facades/).",
"id": "third-party-facades"
},
{
"title": "Image elements do not have explicit `width` and `height`",
"score": 0.5,
"displayValue": null,
"description": "Set an explicit width and height on image elements to reduce layout shifts and improve CLS. [Learn how to set image dimensions](https://web.dev/articles/optimize-cls#images_without_dimensions)",
"id": "unsized-images"
},
{
"title": "Missing source maps for large first-party JavaScript",
"score": 0,
"displayValue": null,
"description": "Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. [Learn more about source maps](https://developer.chrome.com/docs/devtools/javascript/source-maps/).",
"id": "valid-source-maps"
},
{
"title": "ARIA input fields do not have accessible names",
"score": 0,
"displayValue": null,
"description": "When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. [Learn more about input field labels](https://dequeuniversity.com/rules/axe/4.10/aria-input-field-name).",
"id": "aria-input-field-name"
},
{
"title": "Links do not have a discernible name",
"score": 0,
"displayValue": null,
"description": "Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. [Learn how to make links accessible](https://dequeuniversity.com/rules/axe/4.10/link-name).",
"id": "link-name"
},
{
"title": "Serve static assets with an efficient cache policy",
"score": 0.5,
"displayValue": "44 resources found",
"description": "A long cache lifetime can speed up repeat visits to your page. [Learn more about efficient cache policies](https://developer.chrome.com/docs/lighthouse/performance/uses-long-cache-ttl/).",
"id": "uses-long-cache-ttl"
},
{
"title": "Avoid enormous network payloads",
"score": 0.5,
"displayValue": "Total size was 4,564 KiB",
"description": "Large network payloads cost users real money and are highly correlated with long load times. [Learn how to reduce payload sizes](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/).",
"id": "total-byte-weight"
},
{
"title": "Defer offscreen images",
"score": 0.5,
"displayValue": "Est savings of 3 KiB",
"description": "Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. [Learn how to defer offscreen images](https://developer.chrome.com/docs/lighthouse/performance/offscreen-images/).",
"id": "offscreen-images"
},
{
"title": "Eliminate render-blocking resources",
"score": 0,
"displayValue": "Est savings of 1,320 ms",
"description": "Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. [Learn how to eliminate render-blocking resources](https://developer.chrome.com/docs/lighthouse/performance/render-blocking-resources/).",
"id": "render-blocking-resources"
},
{
"title": "Minify CSS",
"score": 0.5,
"displayValue": "Est savings of 6 KiB",
"description": "Minifying CSS files can reduce network payload sizes. [Learn how to minify CSS](https://developer.chrome.com/docs/lighthouse/performance/unminified-css/).",
"id": "unminified-css"
},
{
"title": "Reduce unused CSS",
"score": 0,
"displayValue": "Est savings of 81 KiB",
"description": "Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).",
"id": "unused-css-rules"
},
{
"title": "Reduce unused JavaScript",
"score": 0.5,
"displayValue": "Est savings of 1,164 KiB",
"description": "Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).",
"id": "unused-javascript"
},
{
"title": "Enable text compression",
"score": 0.5,
"displayValue": "Est savings of 1,444 KiB",
"description": "Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. [Learn more about text compression](https://developer.chrome.com/docs/lighthouse/performance/uses-text-compression/).",
"id": "uses-text-compression"
},
{
"title": "Avoid serving legacy JavaScript to modern browsers",
"score": 0.5,
"displayValue": "Est savings of 1 KiB",
"description": "Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://philipwalton.com/articles/the-state-of-es5-on-the-web/)",
"id": "legacy-javascript"
},
{
"title": "Issues were logged in the `Issues` panel in Chrome Devtools",
"score": 0,
"displayValue": null,
"description": "Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.",
"id": "inspector-issues"
},
{
"title": "Links are not crawlable",
"score": 0,
"displayValue": null,
"description": "Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. [Learn how to make links crawlable](https://support.google.com/webmasters/answer/9112205)",
"id": "crawlable-anchors"
},
{
"title": "Use efficient cache lifetimes",
"score": 0,
"displayValue": "Est savings of 2,761 KiB",
"description": "A long cache lifetime can speed up repeat visits to your page. [Learn more](https://web.dev/uses-long-cache-ttl/).",
"id": "cache-insight"
},
{
"title": "Document request latency",
"score": 0,
"displayValue": "Est savings of 50 ms",
"description": "Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.",
"id": "document-latency-insight"
},
{
"title": "Duplicated JavaScript",
"score": 0.5,
"displayValue": "Est savings of 76 KiB",
"description": "Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.",
"id": "duplicated-javascript-insight"
},
{
"title": "Font display",
"score": 0.5,
"displayValue": "Est savings of 10 ms",
"description": "Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).",
"id": "font-display-insight"
},
{
"title": "Forced reflow",
"score": 0,
"displayValue": null,
"description": "A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developers.google.com/web/fundamentals/performance/rendering/avoid-large-complex-layouts-and-layout-thrashing#avoid-forced-synchronous-layouts) and possible mitigations.",
"id": "forced-reflow-insight"
},
{
"title": "Legacy JavaScript",
"score": 0.5,
"displayValue": "Est savings of 11 KiB",
"description": "Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://philipwalton.com/articles/the-state-of-es5-on-the-web/)",
"id": "legacy-javascript-insight"
},
{
"title": "Network dependency tree",
"score": 0,
"displayValue": null,
"description": "[Avoid chaining critical requests](https://developer.chrome.com/docs/lighthouse/performance/critical-request-chains) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.",
"id": "network-dependency-tree-insight"
},
{
"title": "Render blocking requests",
"score": 0,
"displayValue": "Est savings of 1,450 ms",
"description": "Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://web.dev/learn/performance/understanding-the-critical-path#render-blocking_resources) can move these network requests out of the critical path.",
"id": "render-blocking-insight"
}
],
"lighthouseVersion": "12.8.2"
}

How to use it

Start a run in Apify Console, by API or from an agent with an input like this one — it is the input Apify runs every day to test this Actor:

{"urls": ["https://docs.apify.com/platform/actors/publishing/monetize"], "formFactor": "mobile"}

Start with the minimal JSON example above, then adjust the fields in the table below. Read the Example result and Output fields sections for the returned record, Errors for failure codes, and Events and prices for result events and the separate platform start.

FieldTypeMeaning
urlsarrayPublic HTTP(S) URLs to process; errors are uncharged.
formFactorstringAudit mobile, desktop, or both; both is two successful audit events.
categoriesarrayNon-empty subset of the four Lighthouse categories.
includeFullReportbooleanWrite and verify the complete JSON report in key-value storage.

Events and prices

The active Apify pricing record determines your bill; each schedule below is conditional on that exact record being active. A pending record does not authorise its charges. Before submission, while pending, and after activation, use the actual active record, not the requested calendar, to determine the bill.

Requested activation: 2026-12-06T06:00:00Z. This is a request until confirmed by the record; the record supplies the actual effective instant.

Previous schedule — only if that record is active

apify-actor-start: FREE $0.00005, BRONZE $0.00005, SILVER $0.00005, GOLD $0.00005, PLATINUM $0.00005, DIAMOND $0.00005; lighthouse-audit: FREE $0.012, BRONZE $0.012, SILVER $0.0108, GOLD $0.0096, PLATINUM $0.0096, DIAMOND $0.0096.

Requested schedule — only if that record is active

EventTitleCharged whenFREE / BRONZESILVERGOLD / PLATINUM / DIAMOND
lighthouse-auditLighthouse audit runOne successful URL audit for one form factor.$0.024$0.0216$0.0192

Platform event in the requested schedule: apify-actor-start: FREE $0.00005, BRONZE $0.00005, SILVER $0.00005, GOLD $0.00005, PLATINUM $0.00005, DIAMOND $0.00005.

The requested start at default memory is (4 events, $0.0002, at the default 4,096 MB).

Worked event subtotal, requested schedule at FREE: if 10 lighthouse-audit events are charged, 10 × $0.024 = $0.24 for that event alone. All other charged events and the platform start event add their listed fees; this subtotal is not a run total. The configured maximum-charge floor is $0.03. Platform usage is included; failed results are uncharged.

Call it from an agent

Through Apify's MCP server (https://mcp.apify.com) use call-actor:

{
"actor": "hermeskd/lighthouse-audit",
"input": {
"urls": [
"https://docs.apify.com/platform/actors/publishing/monetize"
],
"formFactor": "mobile"
},
"callOptions": {
"maxTotalChargeUsd": 0.05,
"timeout": 900
},
"waitSecs": 30
}

Then call get-dataset-items with the returned defaultDatasetId. Dedicated tool URL: https://mcp.apify.com?tools=hermeskd/lighthouse-audit

Output fields

FieldMeaning
urlInput URL.
finalUrlFinal displayed URL.
okTrue only for a completed readable audit.
formFactorAudited device profile.
scoresInteger percent scores; null for unselected/unscored categories.
metricsLaboratory metrics; time in milliseconds and CLS unitless.
failedAuditsEvery failing numeric/error audit; not-applicable audits omitted.
lighthouseVersionActual Lighthouse version.
reportKeyReadable JSON report key, only when requested.
errorFailure, always uncharged.

Limits and run time

1–20 URLs. mobile, desktop or both; both is two successful audits. Four categories or a non-empty subset. Each audit has a 120-second execution bound; every page request retains the shared 30-second deadline. JSON reports are bounded to 32 MiB. Scores are integers; missing/unselected scores and metrics are null. Browser traffic uses the connection guard and independently checked document/frame navigation. The browser uses its own user-agent with HermesBot appended. Page loads are limited to two per host per second; subresources belong to that page load.

The default run timeout is 900 seconds. The Actor runs at a default 4,096 MB (Apify allots one CPU core per 4,096 MB); the maximum remains 8,192 MB. Typical run time on Apify, measured in the deploy of 2026-10-29: the one-page input at 4,096 MB took 29.5–42.1 seconds across three memory-probe runs; at 8,192 MB it took 32.5–34.6 seconds. A cold image pull is included in the billed run time. The lower memory has the cheaper measured worst-case cost across the retained deploy history, including a slow 69.2-second call on 2026-10-28. The requested price covers that slow call as well as every retained 4,096 MB benchmark on every paying tier, with over 34% room after the developer share on the most expensive call. These are historical measurements, not a guarantee of future run cost. The deploy must measure and pass the floor again before release.

Errors

CodeMeaning
download_failedThe request or connection failed within its bounded deadline.
http_errorThe source answered an unsuccessful HTTP status.
login_requiredThe page is a sign-in wall; no authentication is attempted.
lighthouse_errorThe audit engine failed; its runtime code is carried when available.
robots_disallowedrobots.txt forbids fetching the URL; no request was made to it.
blocked_hostThe host is on the deny-list or resolves to a private or local address; no request was made.
timeoutThe input did not finish within the run's time budget.
source_schema_changedA source or tool response no longer has the verified protocol shape.
internal_errorUnexpected failure; the message carries the error class.
invalid_inputThe run input passed the input schema but cannot be used; the message names the field.
charge_limit_reachedThe run reached its maximum total charge; this input was not processed.
too_largeA documented response, expansion or traversal cap was exceeded.

No failure record is charged. A run fails only when all input outcomes are Actor-side failures; caller errors and a mixture of caller/Actor failures do not fail the run.

Sources and terms

Only process content you have the right to process. URL fetches obey HermesBot robots-group selection, the shared deny-list, public-address checks on connections and redirects, honest identity, deadlines and rate limits. No caller credentials, cookies, CAPTCHA solving, residential proxies or evasion. Public pages named by the caller are audited locally with Lighthouse 12.8.2 (Apache-2.0) and Chromium. This uses no Google account, PageSpeed API key or quota. Browser document navigations receive independent robots checks and every connection passes the address guard. Source reads and the exact release are recorded in the committed enumeration; a source-only HTTP read is not a public Actor run.

Not affiliated

This Actor is not affiliated with Google, Apify, IANA, Verisign or other named protocol/source providers. Third-party names describe compatibility and source material.

Changelog

  • 1.1 (2026-10-30) — Previous per-audit schedule: FREE / BRONZE $0.012, SILVER $0.0108, GOLD / PLATINUM / DIAMOND $0.0096; ten audits plus actor start at 4,096 MB total $0.1202. Historical reference only; the active Apify record determines which schedule applies.

  • 1.1 (2026-10-30) — default memory reduced to 4,096 MB following measured deploy costs; see Events and prices for the conditional proposal.

  • 1.0 (2026-10-26) — store listing rewritten for the people and agents searching for this job: title, description, search-engine title and description, categories, and the README in the order a searcher reads it (what it does, a real result, how to use it, prices, the agent call).

  • 1.0 (2026-10-21) — first public release on Apify Store, after the deploy's typical calls, memory probes, benchmarks and pricing floor passed on the platform.

  • 1.0 (2026-10-19) — repairs from an independent review: DNS privacy, malformed publisher URLs, empty sitemap failures, responsive assets and schema prefill, as applicable to this Actor.

  • 1.0 (2026-10-18) — the production image, smoke input, three example tasks and benchmarks passed on GitHub-hosted Linux.

  • 1.0 (2026-10-17) — first implementation.