Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

Request	Cache TTL	Transfer Size
assets.adobedtm.com/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js	3600.0 s	162.5 KiB
cdn.cookielaw.org/scripttemplates/202501.1.0/otBannerSdk.js	86400.0 s	112.8 KiB
auth.services.adobe.com/imslib/imslib.min.js	14400.0 s	20.8 KiB
www.adobe.com/etc.clientlibs/globalnav/clientlibs/base/privacy-standalone.js	21600.0 s	13.0 KiB
cdn.cookielaw.org/logos/static/ot_company_logo.png	86400.0 s	19.5 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	8.8 KiB
www.adobe.com/marketingtech/main.standard.min.js	0.0 ms	2.3 KiB
/d4d114c60e50/a0e989131fd5/a51f38842101/RC43b630b936cb493...	3600.0 s	2.5 KiB
/d4d114c60e50/a0e989131fd5/a51f38842101/RC04a927fa157f40a...	3600.0 s	1.5 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.5 KiB
geo2.adobe.com/json/?callback=privacy_177635938725560745	0.0 ms	357 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:56.899 source:map[type:text value:[unattributed]]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: Dev Hero banner 2

path: 1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,0,DIV,3,DIV,2,MAIN,0,SECTION,0,P,0,SPAN,1,PICTURE,2,IMG

selector: p.spectrum-Body > span.gatsby-resp-image-wrapper > picture > img.gatsby-resp-image-image

snippet: <img src="https://developer.adobe.com/static/1bde5b5c22354eeb704997730716596c/94b1e/…" alt="Dev Hero banner 2" loading="eager" style="width: 100%; height: 100%; margin: 0px; vertical-align: middle;" class="gatsby-resp-image-image">

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.

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

value: no origins were preconnected

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

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.

	URL	Resource Size	Est Savings
App Builder `p.spectrum-Body > span.gatsby-resp-image-wrapper > picture > img.gatsby-resp-image-image`	developer.adobe.com/static/2a82d928995f14664a1ca7b4094948ff/45954/ADL-2025.webp	114.7 KiB	104.4 KiB
Adobe MAX `p.spectrum-Body > span.gatsby-resp-image-wrapper > picture > img.gatsby-resp-image-image`	/static/654ae1b27313dda5eefad8f5030d5b09/cf465/DevLive_Ju...	100.9 KiB	90.6 KiB
Express Add-Ons `p.spectrum-Body > span.gatsby-resp-image-wrapper > picture > img.gatsby-resp-image-image`	/static/626d53429622009c145b3491706f12d5/94b1e/Express_Ad...	44.8 KiB	40.5 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 697 ms

URL	Time Spent
adobe.io/	495 ms
www.adobe.io/	202 ms
developer.adobe.com/	0.0 ms

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

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.

Diagnostics

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.

Estimated savings: 730 ms 1016.8 KiB

URL	Transfer Size	Est Savings
developer.adobe.com/dev-site-assets/579e4e6714746dfa0bf9.js	422.9 KiB	303.0 KiB
developer.adobe.com/search-frame/dev-site-assets/0b8287da19fccf674b73.js	357.8 KiB	285.5 KiB
cdn.cookielaw.org/scripttemplates/202501.1.0/otBannerSdk.js	112.6 KiB	98.3 KiB
assets.adobedtm.com/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js	162.2 KiB	97.6 KiB
developer.adobe.com/search-frame/dev-site-assets/b6b591956631b360f54f.js	74.9 KiB	65.4 KiB
developer.adobe.com/dev-site-assets/a3902d0e94a17a9b8e94.js	74.9 KiB	65.4 KiB
cdn.cookielaw.org/scripttemplates/202501.1.0/otBannerSdk.js	112.6 KiB	62.0 KiB
developer.adobe.com/search-frame/dev-site-assets/591cf2c8e047b5715a7f.js	74.7 KiB	39.6 KiB

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 8.9 KiB

URL	Transfer Size	Est Savings
	59.6 KiB	8.9 KiB

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: 0.0 ms 181.4 KiB

URL	Transfer Size	Est Savings
.spectrum{--spectrum-global-animation-linear:cubic-bezier(0,0,1,1);--spectrum-global-animation-dura…	78.1 KiB	78.1 KiB
.spectrum{--spectrum-global-animation-linear:cubic-bezier(0,0,1,1);--spectrum-global-animation-dura…	84.2 KiB	52.4 KiB
	59.6 KiB	50.9 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,306 KiB

●User Timing marks and measures 2 user timings

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.3 s

●Avoid long main-thread tasks 3 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 120 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 0 ms

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○Avoid non-composited animations

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home `div.css-17rxrrc > div.css-2mytqp > div.css-13d1d42 > a#tabindex0`
Products `div.css-17rxrrc > div.css-2mytqp > div.css-13d1d42 > a#tabindex1`
Community `div.css-17rxrrc > div.css-2mytqp > div.css-13d1d42 > div#tabindex2`

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
Adobe Developer `div.css-wm3npa > a#adobeIcon > div.css-s5xdrg > strong.spectrum-Heading`
Adobe `a#adobeIcon > div.css-s5xdrg > strong.spectrum-Heading > span.css-ppngqo`

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
Launch the Adobe Developer Console: `section.text-style > div.css-8yifvb > p.spectrum-Body > a.spectrum-Link`
Adobe Exchange Marketplace `section.text-style > div.css-sux842 > p.spectrum-Body > a.spectrum-Link`
Adobe Developers Blog `section.text-style > div.css-imrbmy > p.spectrum-Body > a.spectrum-Link`

These are opportunities to improve the legibility of your content.

○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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[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.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[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

○Form elements have associated labels

○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.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○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.

Best Practices

General

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.

Source	Description
cdn.cookielaw.org/scripttemplates/202501.1.0/otBannerSdk.js line 6, col 467341	`TypeError: Cannot read properties of undefined (reading 'TenantFeatures') at https://cdn.cookielaw.org/scripttemplates/202501.1.0/otBannerSdk.js:7:467342 at https://cdn.cookielaw.org/scripttemplates/202501.1.0/otBannerSdk.js:7:475472`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS

●Avoids deprecated APIs

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

100

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.

○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

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`