C — https://www.adobe.com | BeaverCheck Audit

Site Health

Score: 73 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

Page weighs 15.3 MB (3.9 MB transferred)

Performance › Page Weight Budget

2 image(s) missing alt attribute

Accessibility › Alt Text Quality

No <main> landmark found

Accessibility › Landmark Structure

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.adobe.com)](https://beavercheck.com/results/e6ca5c06-6a08-806a-c20c-df0f41b7a798)

HTML

<a href="https://beavercheck.com/results/e6ca5c06-6a08-806a-c20c-df0f41b7a798"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.adobe.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.adobe.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

100

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.34 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.67 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

206 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.32 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

9.31 s

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.

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

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

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

Request	Cache TTL	Transfer Size
www.adobe.com/marketingtech/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js	0.0 ms	136.5 KiB
client.messaging.adobe.com/latest/AdobeMessagingClient.js	0.0 ms	37.4 KiB
www.adobe.com/etc.clientlibs/globalnav/clientlibs/base/privacy-standalone.js	21600.0 s	12.5 KiB
client.messaging.adobe.com/latest/AdobeMessagingClient.css	0.0 ms	7.0 KiB
www.adobe.com/akam/13/5f70ebe0	21600.0 s	9.4 KiB
/unav/1.5/vendors-node_modules_intl_adobe-locales_dist_ad...	43200.0 s	11.7 KiB
s2.go-mpulse.net/boomerang/MXSSB-A58LJ-RJPHN-5VBV8-JQ3FW	604800.0 s	56.3 KiB
prod.adobeccstatic.com/unav/1.5/UniversalNav.css	43200.0 s	11.1 KiB
prod.adobeccstatic.com/unav/1.5/UniversalNav.js	43200.0 s	10.8 KiB
/unav/1.5/vendors-node_modules_cchome_ingest-react_index_...	43200.0 s	6.8 KiB
prod.adobeccstatic.com/unav/1.5/AnalyticsProvider.9de9869f8d722dc25993.bundle.js	43200.0 s	4.3 KiB
/unav/1.5/UniversalNavComponentLayout.8bf2b383a7f98e7ec8c...	43200.0 s	3.8 KiB
www.adobe.com/marketingtech/main.standard.min.js	0.0 ms	1.8 KiB
/unav/1.5/createCartComponent.2737a247d41ad89d70d1.bundle.js	43200.0 s	3.4 KiB
/marketingtech/d4d114c60e50/a0e989131fd5/f842cfa591cb/RC0...	0.0 ms	1.1 KiB
prod.adobeccstatic.com/unav/1.5/icons-default.a791d3f6a1d83b2f8b28.bundle.js	43200.0 s	2.2 KiB
www.adobe.com/content/dam/cc/optimization/pzn/fixPodHeightUSOnlyPostMax.js?v1	21600.0 s	1.4 KiB
prod.adobeccstatic.com/unav/1.5/AEPProvider.97ecedf81c3cd8b00458.bundle.js	43200.0 s	1.8 KiB
prod.adobeccstatic.com/unav/1.5/layout.bundle.css	43200.0 s	1.8 KiB
prod.adobeccstatic.com/unav/1.5/localization.9e06d3f4d731aa249008.bundle.js	43200.0 s	1.7 KiB
prod.adobeccstatic.com/unav/1.5/TrayLayout.3c62a247e6dfbea3cf6f.bundle.js	43200.0 s	1.6 KiB
prod.adobeccstatic.com/unav/1.5/profile.caf56ff75a83df4ef4ea.bundle.js	43200.0 s	1.4 KiB
prod.adobeccstatic.com/unav/1.5/validator.154d4012a397a5d81fe7.bundle.js	43200.0 s	1.1 KiB
prod.adobeccstatic.com/unav/1.5/tray.bundle.css	43200.0 s	897 B
prod.adobeccstatic.com/unav/1.5/profile.bundle.css	43200.0 s	846 B
/p.css?s=1&k=hah7vzn&ht=tk&f=7180.7181.7182.7183.7185.224...	604800.0 s	172 B

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

lhId: page-0-IMG

nodeLabel: div.background > div > picture > img

path: 1,HTML,1,BODY,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,3,IMG

selector: div.background > div > picture > img

snippet: <img loading="eager" alt="" src="https://www.adobe.com/upp-shared/media_15172f98a61142921581530c6eb1763bae8…" width="720" height="540" fetchpriority="high" style="object-position: 50% 50%;">

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

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.

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.

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 0.0 ms 17.8 KiB

URL	Transfer Size	Est Savings
www.adobe.com/libs/utils/utils.js	23.2 KiB	4.6 KiB
www.adobe.com/libs/blocks/global-navigation/global-navigation.js	16.5 KiB	4.1 KiB
www.adobe.com/libs/blocks/merch/merch.js	14.8 KiB	3.7 KiB
www.adobe.com/libs/features/personalization/personalization.js	14.8 KiB	2.9 KiB
www.adobe.com/libs/blocks/global-navigation/utilities/utilities.js	11.6 KiB	2.6 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.adobe.com/	1.4 s	32 ms	0.5 ms
Unattributable	1.1 s	301 ms	0.0 ms
www.adobe.com/marketingtech/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js	329 ms	260 ms	56 ms
www.adobe.com/libs/blocks/global-navigation/utilities/utilities.js	326 ms	231 ms	0.2 ms
client.messaging.adobe.com/latest/AdobeMessagingClient.js	172 ms	125 ms	17 ms
commerce.adobe.com/store/iframe/preload-optimized.html	153 ms	55 ms	29 ms
www.adobe.com/akam/13/5f70ebe0	151 ms	142 ms	3.3 ms
www.adobe.com/libs/utils/utils.js	94 ms	51 ms	6.2 ms
www.adobe.com/libs/utils/decorate.js	93 ms	0.0 ms	2.0 ms
www.adobe.com/upp/blocks/homepage-brick/homepage-brick.js	70 ms	15 ms	1.1 ms
www.adobe.com/libs/blocks/fragment/fragment.js	65 ms	54 ms	0.1 ms
www.adobe.com/mas/libs/commerce.js	56 ms	42 ms	0.4 ms
s2.go-mpulse.net/boomerang/MXSSB-A58LJ-RJPHN-5VBV8-JQ3FW	51 ms	32 ms	15 ms

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

Category	Time Spent
Script Evaluation	1.6 s
Other	1.3 s
Style & Layout	1.2 s
Script Parsing & Compilation	169 ms
Parse HTML & CSS	138 ms
Garbage Collection	97 ms
Rendering	61 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reason	Failure type
The page has an unload handler in a sub frame.	Actionable

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

Estimated savings: 0.0 ms 136.1 KiB

URL	Transfer Size	Est Savings
www.adobe.com/marketingtech/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js	136.5 KiB	79.3 KiB
s2.go-mpulse.net/boomerang/MXSSB-A58LJ-RJPHN-5VBV8-JQ3FW	56.1 KiB	36.5 KiB
client.messaging.adobe.com/latest/AdobeMessagingClient.js	37.0 KiB	20.3 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
commerce.adobe.com/store/_next/static/chunks/pages/_app-0c40935afa5f1689.js	2.3 MiB
/store/_next/static/chunks/pages/segmentation-57ecfe7f491...	269.1 KiB
commerce.adobe.com/store/_next/static/chunks/pages/_app.83dfcef9.css	197.9 KiB
www.adobe.com/marketingtech/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js	136.5 KiB
commerce.adobe.com/store/_next/static/chunks/styles.df7ecca0.css	69.2 KiB
commerce.adobe.com/store/_next/static/chunks/framework-880e7eeca526ad46.js	65.4 KiB
/af/59b220/00000000000000007735dac8/31/l?primer=7cdcb44be...	61.9 KiB
/af/55f17d/00000000000000007735dad8/31/l?primer=7cdcb44be...	61.8 KiB
s2.go-mpulse.net/boomerang/MXSSB-A58LJ-RJPHN-5VBV8-JQ3FW	56.3 KiB
/upp-shared/media_15172f98a61142921581530c6eb1763bae8959a...	55.3 KiB

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

	URL
Adobe, Inc. `div.feds-brand-container > a.feds-brand > span.feds-brand-image > img`	www.adobe.com/federal/assets/svgs/adobe-logo.svg

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

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Network dependency tree

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

●User Timing marks and measures 44 user timings

●Avoid long main-thread tasks 7 long tasks found

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 190 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 20 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

100

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.

○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

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Uses ARIA roles only on compatible elements

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

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

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

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

○All heading elements contain content.

○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

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

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	s2.go-mpulse.net/boomerang/MXSSB-A58LJ-RJPHN-5VBV8-JQ3FW line 9, col 11504

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

Source	Description
www.adobe.com/	`Access to fetch at 'https://cdn.cookielaw.org/consent/7a5eb705-95ed-4cc4-a11d-0cc5760e93db/7a5eb705-95ed-4cc4-a11d-0cc5760e93db.json' from origin 'https://www.adobe.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
www.adobe.com/	`Access to script at 'https://cdn.cookielaw.org/scripttemplates/otSDKStub.js' from origin 'https://www.adobe.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
www.adobe.com/etc.clientlibs/globalnav/clientlibs/base/privacy-standalone.js line 3, col 7941	`Event`
/consent/7a5eb705-95ed-4cc4-a11d-0cc5760e93db/7a5eb705-95...	`Failed to load resource: net::ERR_FAILED`
cdn.cookielaw.org/scripttemplates/otSDKStub.js	`Failed to load resource: net::ERR_FAILED`

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.

URL
www.adobe.com/marketingtech/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js

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

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

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.

Link destination	Link Text
business.adobe.com/	Learn more
www.adobe.com/products/firefly.html	Learn more

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

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

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

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

100

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

436 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.12 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.30 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.12 s

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.

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

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

Request	Cache TTL	Transfer Size
www.adobe.com/marketingtech/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js	0.0 ms	136.4 KiB
client.messaging.adobe.com/latest/AdobeMessagingClient.js	0.0 ms	37.4 KiB
www.adobe.com/etc.clientlibs/globalnav/clientlibs/base/privacy-standalone.js	21600.0 s	12.5 KiB
client.messaging.adobe.com/latest/AdobeMessagingClient.css	0.0 ms	7.0 KiB
www.adobe.com/akam/13/5f70ebe0	21600.0 s	9.4 KiB
/unav/1.5/vendors-node_modules_intl_adobe-locales_dist_ad...	43200.0 s	11.7 KiB
s2.go-mpulse.net/boomerang/MXSSB-A58LJ-RJPHN-5VBV8-JQ3FW	604800.0 s	56.3 KiB
prod.adobeccstatic.com/unav/1.5/UniversalNav.css	43200.0 s	11.1 KiB
prod.adobeccstatic.com/unav/1.5/UniversalNav.js	43200.0 s	10.8 KiB
/unav/1.5/vendors-node_modules_cchome_ingest-react_index_...	43200.0 s	6.8 KiB
prod.adobeccstatic.com/unav/1.5/AnalyticsProvider.9de9869f8d722dc25993.bundle.js	43200.0 s	4.3 KiB
/unav/1.5/UniversalNavComponentLayout.8bf2b383a7f98e7ec8c...	43200.0 s	3.8 KiB
www.adobe.com/marketingtech/main.standard.min.js	0.0 ms	1.8 KiB
/unav/1.5/createCartComponent.2737a247d41ad89d70d1.bundle.js	43200.0 s	3.4 KiB
/marketingtech/d4d114c60e50/a0e989131fd5/f842cfa591cb/RC0...	0.0 ms	1.1 KiB
prod.adobeccstatic.com/unav/1.5/icons-default.a791d3f6a1d83b2f8b28.bundle.js	43200.0 s	2.1 KiB
www.adobe.com/content/dam/cc/optimization/pzn/fixPodHeightUSOnlyPostMax.js?v1	21600.0 s	1.4 KiB
prod.adobeccstatic.com/unav/1.5/AEPProvider.97ecedf81c3cd8b00458.bundle.js	43200.0 s	1.8 KiB
prod.adobeccstatic.com/unav/1.5/layout.bundle.css	43200.0 s	1.8 KiB
prod.adobeccstatic.com/unav/1.5/localization.9e06d3f4d731aa249008.bundle.js	43200.0 s	1.7 KiB
prod.adobeccstatic.com/unav/1.5/profile.caf56ff75a83df4ef4ea.bundle.js	43200.0 s	1.4 KiB
prod.adobeccstatic.com/unav/1.5/validator.154d4012a397a5d81fe7.bundle.js	43200.0 s	1.1 KiB
prod.adobeccstatic.com/unav/1.5/PopoverLayout.0cc7505f14981bb71a65.bundle.js	43200.0 s	1.1 KiB
prod.adobeccstatic.com/unav/1.5/popover.bundle.css	43200.0 s	991 B
prod.adobeccstatic.com/unav/1.5/profile.bundle.css	43200.0 s	845 B
/p.css?s=1&k=hah7vzn&ht=tk&f=7180.7181.7182.7183.7185.224...	604800.0 s	172 B

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

	URL	Resource Size	Est Savings
div.background > div.desktopOnly > picture > img `div.background > div.desktopOnly > picture > img`	/upp-shared/media_191004308a9ddf7e72e93b1db66a55954b6b6fe...	183.5 KiB	175.0 KiB
div.background > div.desktopOnly > picture > img `div.background > div.desktopOnly > picture > img`	/upp-shared/media_109103253402c26b30b717042bb3210471341d9...	145.3 KiB	69.6 KiB

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

lhId: page-2-IMG

nodeLabel: Inserting image...

path: 1,HTML,1,BODY,1,MAIN,0,DIV,0,PICTURE,3,IMG

selector: main > div.section > picture.section-background > img

snippet: <img loading="eager" alt="Inserting image..." src="https://www.adobe.com/upp-shared/media_1babc08c0941b67a737c17c8205a784f2c9…" width="1600" height="742" fetchpriority="high">

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

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.

Estimated savings: 70 ms 122.3 KiB

URL	Transfer Size	Est Savings
www.adobe.com/marketingtech/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js	136.4 KiB	79.3 KiB
s2.go-mpulse.net/boomerang/MXSSB-A58LJ-RJPHN-5VBV8-JQ3FW	56.1 KiB	22.8 KiB
client.messaging.adobe.com/latest/AdobeMessagingClient.js	37.0 KiB	20.3 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reason	Failure type
The page has an unload handler in a sub frame.	Actionable

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 0.0 ms 17.8 KiB

URL	Transfer Size	Est Savings
www.adobe.com/libs/utils/utils.js	23.2 KiB	4.6 KiB
www.adobe.com/libs/blocks/global-navigation/global-navigation.js	16.5 KiB	4.1 KiB
www.adobe.com/libs/blocks/merch/merch.js	14.8 KiB	3.7 KiB
www.adobe.com/libs/features/personalization/personalization.js	14.8 KiB	2.9 KiB
www.adobe.com/libs/blocks/global-navigation/utilities/utilities.js	11.6 KiB	2.6 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
commerce.adobe.com/store/_next/static/chunks/pages/_app-0c40935afa5f1689.js	2.3 MiB
/store/_next/static/chunks/pages/segmentation-57ecfe7f491...	269.1 KiB
commerce.adobe.com/store/_next/static/chunks/pages/_app.83dfcef9.css	197.9 KiB
/upp-shared/media_191004308a9ddf7e72e93b1db66a55954b6b6fe...	183.6 KiB
/upp-shared/media_109103253402c26b30b717042bb3210471341d9...	145.4 KiB
www.adobe.com/marketingtech/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js	136.4 KiB
/homepage/fragments/loggedout/pods/2026/media_16fa4eac7da...	115.3 KiB
/homepage/fragments/loggedout/pods/max-2025/media_1869b11...	84.3 KiB
commerce.adobe.com/store/_next/static/chunks/styles.df7ecca0.css	69.2 KiB
commerce.adobe.com/store/_next/static/chunks/framework-880e7eeca526ad46.js	65.4 KiB

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

	URL
Adobe, Inc. `div.feds-brand-container > a.feds-brand > span.feds-brand-image > img`	www.adobe.com/federal/assets/svgs/adobe-logo.svg

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Network dependency tree

●Render blocking requests

●Optimize viewport for mobile

●Time to Interactive 1.1 s

●Max Potential First Input Delay 40 ms

●Minify CSS

●Reduce unused CSS

●User Timing marks and measures 44 user timings

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.9 s

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 280 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 20 ms

○INP breakdown

○Avoid long main-thread tasks

○Avoid non-composited animations

○Avoid large layout shifts

100

Accessibility

○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

●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

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

●Identical links have the same purpose.

●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 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

○ARIA IDs are unique

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

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

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

○All heading elements contain content.

○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

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

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	s2.go-mpulse.net/boomerang/MXSSB-A58LJ-RJPHN-5VBV8-JQ3FW line 9, col 11504

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

Source	Description
www.adobe.com/	`Access to fetch at 'https://cdn.cookielaw.org/consent/7a5eb705-95ed-4cc4-a11d-0cc5760e93db/7a5eb705-95ed-4cc4-a11d-0cc5760e93db.json' from origin 'https://www.adobe.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
www.adobe.com/	`Access to script at 'https://cdn.cookielaw.org/scripttemplates/otSDKStub.js' from origin 'https://www.adobe.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
s2.go-mpulse.net/boomerang/MXSSB-A58LJ-RJPHN-5VBV8-JQ3FW line 9, col 28393	`Connecting to 'https://684dd326.akstat.io/' violates the following Content Security Policy directive: "connect-src 'self' p.typekit.net performance.typekit.net .forter.com d1wix2gc2cgqis.cloudfront.net .go-mpulse.net .fptls.com api.fpjs.io .api.fpjs.io". The action has been blocked.`
www.adobe.com/etc.clientlibs/globalnav/clientlibs/base/privacy-standalone.js line 3, col 7941	`Event`
/consent/7a5eb705-95ed-4cc4-a11d-0cc5760e93db/7a5eb705-95...	`Failed to load resource: net::ERR_FAILED`
cdn.cookielaw.org/scripttemplates/otSDKStub.js	`Failed to load resource: net::ERR_FAILED`

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.

Issue type
Content security policy

URL
www.adobe.com/marketingtech/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js

●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

●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

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

SEO

Content Best Practices

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

Link destination	Link Text
business.adobe.com/	Learn more

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

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

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

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.adobe.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Content Best Practices

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Content Best Practices

Crawling and Indexing

Keyboard Shortcuts