Skip to content
https://launchdarkly.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

47

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:21.693 source:map[column:31326 line:4 type:source-location url:https://go.launchdarkly.com/js/forms2/js/forms2.min.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:94.164 source:map[type:text value:[unattributed]]] map[reflowTime:19.815 source:map[column:9443 line:4 type:source-location url:https://go.launchdarkly.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:0.442 source:map[column:27995 line:5 type:source-location url:https://go.launchdarkly.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:0.22 source:map[column:28053 line:5 type:source-location url:https://go.launchdarkly.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:0.215 source:map[column:28117 line:5 type:source-location url:https://go.launchdarkly.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:4.683 source:map[column:9465 line:4 type:source-location url:https://go.launchdarkly.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:1.757 source:map[column:70169 line:0 type:source-location url:https://client-registry.mutinycdn.com/mutiny-client/223.5.6.3.js urlProvider:network]] map[reflowTime:3.114 source:map[column:23219 line:1 type:source-location url:https://scripts.clarity.ms/0.8.60-beta/clarity.js urlProvider:network]] map[reflowTime:0.921 source:map[column:24761 line:6 type:source-location url:https://go.launchdarkly.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:0.35 source:map[column:29061 line:5 type:source-location url:https://go.launchdarkly.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:0.35 source:map[column:30784 line:5 type:source-location url:https://go.launchdarkly.com/js/forms2/js/forms2.min.js urlProvider:network]] map[reflowTime:0.617 source:map[column:10930 line:4 type:source-location url:https://go.launchdarkly.com/js/forms2/js/forms2.min.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:176.434 label:Time to first byte subpart:timeToFirstByte] map[duration:2734.439 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-H1
nodeLabel: Move at AI speed. Stay in control.
path: 1,HTML,1,BODY,3,DIV,0,DIV,2,MAIN,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,H1
selector: div.styles-module--container--978fd > div.styles-module--content--2f2bb > div.styles-module--headings--85b5a > h1.styles-module--title--5170e
snippet: <h1 class="styles-module--title--5170e">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Bayer div.styles-module--quoteContainer--5e366 > div.styles-module--quoteImage--754cf > a.styles-module--newDesignLink--7f85f > img.styles-module--desktopImage--483d7
/launchdarkly/aTdcanNYClf9n8XZ_new-case-slider-img--bayer...158.3 KiB122.0 KiB
CCP Games div.styles-module--quoteContainer--5e366 > div.styles-module--quoteImage--754cf > a.styles-module--newDesignLink--7f85f > img.styles-module--desktopImage--483d7
/launchdarkly/aTdKSXNYClf9n8PS_new-case-slider-img--ccp.p...138.2 KiB103.7 KiB
Paramount div.styles-module--quoteContainer--5e366 > div.styles-module--quoteImage--754cf > a.styles-module--newDesignLink--7f85f > img.styles-module--desktopImage--483d7
/launchdarkly/aTcwQ3NYClf9n8Gq_new-case-slider-img--param...131.0 KiB98.3 KiB
HP div.styles-module--quoteContainer--5e366 > div.styles-module--quoteImage--754cf > a.styles-module--newDesignLink--7f85f > img.styles-module--desktopImage--483d7
/launchdarkly/aTcmbXNYClf9n8DN_new-case-slider-img--hp.pn...126.0 KiB94.5 KiB
Dior div.styles-module--quoteContainer--5e366 > div.styles-module--quoteImage--754cf > a.styles-module--newDesignLink--7f85f > img.styles-module--desktopImage--483d7
/launchdarkly/aTN9NHNYClf9n4Kl_new-case-slider-img--dior....101.3 KiB76.0 KiB
platform-demo li#splide02-slide01 > div > div.styles-module--imageContainer--fd95e > img
/launchdarkly-marketingsite/aatHW1xvIZEnjb9t_Video_03-26_...54.1 KiB51.8 KiB
The AI Control Gap Report a.styles-module--banner--5b6d4 > div.styles-module--bannerInner--eef9c > div.styles-module--img--edfec > img
/launchdarkly/aTNj73NYClf9n4Ih_Events_banner_graphic.jpeg...51.2 KiB36.4 KiB
The AI Control Gap Report a.styles-module--banner--5b6d4 > div.styles-module--bannerInner--eef9c > div.styles-module--img--edfec > img
/launchdarkly-marketingsite/aVwcunNYClf9ozIx_AIControlGap...30.6 KiB22.1 KiB
ai-configs li#splide02-slide03 > div > div.styles-module--imageContainer--fd95e > img
/launchdarkly/aTNhCHNYClf9n4ID_Video_09-25_AI_Configs_Pro...25.8 KiB19.6 KiB
feature-flags li#splide02-slide02 > div > div.styles-module--imageContainer--fd95e > img
/launchdarkly/aTNhCnNYClf9n4IF_Video_09-25_Feature_Flags_...24.4 KiB18.5 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 335.3 KiB
URLTransfer SizeEst Savings
launchdarkly.com/styles.3138031de270ca2879d7.css345.4 KiB335.3 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation2.0 s
Other1.5 s
Style & Layout286 ms
Parse HTML & CSS176 ms
Script Parsing & Compilation113 ms
Rendering90 ms
Garbage Collection58 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
platform-demo li#splide02-slide01 > div > div.styles-module--imageContainer--fd95e > img
/launchdarkly-marketingsite/aatHW1xvIZEnjb9t_Video_03-26_...
coding-with-ai li#splide02-slide04 > div > div.styles-module--imageContainer--fd95e > img
/launchdarkly/aWqWYQIvOtkhBqkn_Video_01-26_Coding-with-AI...
The AI Control Gap Report a.styles-module--banner--5b6d4 > div.styles-module--bannerInner--eef9c > div.styles-module--img--edfec > img
/launchdarkly-marketingsite/aVwcunNYClf9ozIx_AIControlGap...

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
Font display
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 7 user timings
Avoid long main-thread tasks 10 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 180 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 100 ms
INP breakdown
LCP request discovery
Avoid non-composited animations
Avoid large layout shifts
78

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Platform Solutions Resources Developers Pricing nav.styles-module--nav--73dba > div.styles-module--navInner--8e961 > div#mainNavigation > div.styles-module--mainNav--041e0

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.styles-module--tabContent--cbecb > div.styles-module--tabContentRight--9dfd7 > div.styles-module--tabletUpVideo--62c02 > video div.styles-module--tabContent--cbecb > div.styles-module--tabContentRight--9dfd7 > div.styles-module--tabletUpVideo--62c02 > video
div.styles-module--tabContent--cbecb > div.styles-module--tabContentRight--9dfd7 > div.styles-module--tabletUpVideo--62c02 > video div.styles-module--tabContent--cbecb > div.styles-module--tabContentRight--9dfd7 > div.styles-module--tabletUpVideo--62c02 > video
div.styles-module--tabContent--cbecb > div.styles-module--tabContentRight--9dfd7 > div.styles-module--tabletUpVideo--62c02 > video div.styles-module--tabContent--cbecb > div.styles-module--tabContentRight--9dfd7 > div.styles-module--tabletUpVideo--62c02 > video

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
©2026 Catamorphic Co. div.styles-module--container--f7e03 > div.styles-module--logoContainer--1d884 > div.styles-module--socialMedia--ee6bc > p.styles-module--copyright--1d439

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
privacy policy div#cookiebanner_consent > div#c-middle > p.c-message > a
click here div#cookiebanner_consent > div#c-middle > p.c-message > a.open-preference-link

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Docs div.styles-module--linkBoxes--5d678 > a.styles-module--linkBox--78baf > div > h4
David Tieba span.styles-module--linkBlock--4d82c > div.styles-module--quoteContainer--e6aa4 > div > h6

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
span.styles-module--linkBlock--4d82c > div.styles-module--quoteContainer--e6aa4 > div.styles-module--imgContainer--aac1b > img.vestiaire-collective span.styles-module--linkBlock--4d82c > div.styles-module--quoteContainer--e6aa4 > div.styles-module--imgContainer--aac1b > img.vestiaire-collective

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
launchdarkly.com/ line 25, col 12
AttributionReporting

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Uncaught ReferenceError: revealCallback is not defined
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
77

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
span.styles-module--linkBlock--4d82c > div.styles-module--quoteContainer--e6aa4 > div.styles-module--imgContainer--aac1b > img.vestiaire-collective span.styles-module--linkBlock--4d82c > div.styles-module--quoteContainer--e6aa4 > div.styles-module--imgContainer--aac1b > img.vestiaire-collective

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Accept cookies div#cookiebanner > div#cookiebanner_consent > div#c-right > a.c-button
Decline cookies div#cookiebanner > div#cookiebanner_consent > div#c-right > a.c-button
Allow selected div#cookiebanner_preferece > div.cookiebot-preference-footer-group > div.cookiebot-preference-button-group > a#CybotCookiebotDialogBodyLevelButtonAccept
Allow all div#cookiebanner_preferece > div.cookiebot-preference-footer-group > div.cookiebot-preference-button-group > a.cookiebot-preference-button-group-selected-button

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback