Skip to content
https://get.adobe.com

Lighthouse Mobile

· 0 checks — Mobile 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.

80

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.

RequestCache TTLTransfer Size
www.adobe.com/marketingtech/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js0.0 ms137.6 KiB
cdn.cookielaw.org/scripttemplates/202501.1.0/otBannerSdk.js86400.0 s112.8 KiB
client.messaging.adobe.com/latest/AdobeMessagingClient.js0.0 ms37.5 KiB
www.adobe.com/etc.clientlibs/globalnav/clientlibs/base/privacy-standalone.js21600.0 s12.5 KiB
cdn.cookielaw.org/logos/static/ot_company_logo.png86400.0 s19.5 KiB
client.messaging.adobe.com/latest/AdobeMessagingClient.css0.0 ms7.0 KiB
www.adobe.com/akam/13/5f70eb3c21600.0 s9.4 KiB
/unav/1.5/vendors-node_modules_intl_adobe-locales_dist_ad...43200.0 s11.7 KiB
s2.go-mpulse.net/boomerang/MXSSB-A58LJ-RJPHN-5VBV8-JQ3FW604800.0 s56.5 KiB
prod.adobeccstatic.com/unav/1.5/UniversalNav.js43200.0 s10.8 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s8.8 KiB
/unav/1.5/vendors-node_modules_cchome_ingest-react_index_...43200.0 s6.8 KiB
prod.adobeccstatic.com/unav/1.5/AnalyticsProvider.9de9869f8d722dc25993.bundle.js43200.0 s4.3 KiB
/unav/1.5/UniversalNavComponentLayout.8bf2b383a7f98e7ec8c...43200.0 s3.7 KiB
www.adobe.com/marketingtech/main.standard.min.js0.0 ms1.8 KiB
/unav/1.5/createCartComponent.2737a247d41ad89d70d1.bundle.js43200.0 s3.4 KiB
prod.adobeccstatic.com/unav/1.5/UniversalNav.css43200.0 s2.3 KiB
/marketingtech/d4d114c60e50/a0e989131fd5/6a0ce35364bd/RC0...0.0 ms1.1 KiB
prod.adobeccstatic.com/unav/1.5/icons-default.a791d3f6a1d83b2f8b28.bundle.js43200.0 s2.1 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.5 KiB
prod.adobeccstatic.com/unav/1.5/AEPProvider.97ecedf81c3cd8b00458.bundle.js43200.0 s1.9 KiB
www.adobe.com/content/dam/cc/optimization/pzn/fixPodHeightUSOnlyPostMax.js?v121600.0 s1.4 KiB
prod.adobeccstatic.com/unav/1.5/layout.bundle.css43200.0 s1.8 KiB
prod.adobeccstatic.com/unav/1.5/TrayLayout.3c62a247e6dfbea3cf6f.bundle.js43200.0 s1.6 KiB
prod.adobeccstatic.com/unav/1.5/localization.9e06d3f4d731aa249008.bundle.js43200.0 s1.6 KiB
prod.adobeccstatic.com/unav/1.5/profile.caf56ff75a83df4ef4ea.bundle.js43200.0 s1.4 KiB
prod.adobeccstatic.com/unav/1.5/validator.154d4012a397a5d81fe7.bundle.js43200.0 s1.1 KiB
prod.adobeccstatic.com/unav/1.5/tray.bundle.css43200.0 s993 B
prod.adobeccstatic.com/unav/1.5/profile.bundle.css43200.0 s845 B
/p.css?s=1&k=hah7vzn&ht=tk&f=7180.7181.7182.7183.7185.224...604800.0 s172 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.

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: 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">

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
value: No additional origins are good candidates for preconnecting

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: 753 ms
URLTime Spent
get.adobe.com/753 ms
www.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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 18.1 KiB
URLTransfer SizeEst Savings
www.adobe.com/libs/utils/utils.js24.4 KiB4.8 KiB
www.adobe.com/libs/blocks/global-navigation/global-navigation.js16.6 KiB4.1 KiB
www.adobe.com/libs/blocks/merch/merch.js14.8 KiB3.7 KiB
www.adobe.com/libs/features/personalization/personalization.js14.8 KiB2.9 KiB
www.adobe.com/libs/blocks/global-navigation/utilities/utilities.js11.6 KiB2.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
www.adobe.com/1.9 s46 ms1.6 ms
Unattributable1.7 s519 ms0.0 ms
www.adobe.com/marketingtech/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js499 ms418 ms59 ms
www.adobe.com/libs/blocks/global-navigation/utilities/utilities.js471 ms341 ms0.2 ms
cdn.cookielaw.org/scripttemplates/202501.1.0/otBannerSdk.js428 ms291 ms53 ms
client.messaging.adobe.com/latest/AdobeMessagingClient.js264 ms185 ms17 ms
www.adobe.com/libs/utils/decorate.js217 ms0.0 ms1.7 ms
www.adobe.com/libs/utils/utils.js161 ms75 ms9.3 ms
www.adobe.com/upp/blocks/homepage-brick/homepage-brick.js155 ms38 ms1.1 ms
www.adobe.com/akam/13/5f70eb3c147 ms134 ms4.4 ms
commerce.adobe.com/store/iframe/preload-optimized.html120 ms33 ms4.2 ms
www.adobe.com/mas/libs/commerce.js96 ms77 ms0.5 ms
s2.go-mpulse.net/boomerang/MXSSB-A58LJ-RJPHN-5VBV8-JQ3FW91 ms72 ms16 ms
www.adobe.com/libs/blocks/fragment/fragment.js84 ms67 ms0.2 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation2.7 s
Style & Layout1.8 s
Other1.7 s
Parse HTML & CSS228 ms
Script Parsing & Compilation217 ms
Garbage Collection146 ms
Rendering91 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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
URLTransfer SizeEst Savings
59.6 KiB8.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 59.6 KiB
URLTransfer SizeEst Savings
59.6 KiB59.6 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.

Estimated savings: 0.0 ms 198.3 KiB
URLTransfer SizeEst Savings
www.adobe.com/marketingtech/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js137.5 KiB79.3 KiB
cdn.cookielaw.org/scripttemplates/202501.1.0/otBannerSdk.js112.6 KiB62.0 KiB
s2.go-mpulse.net/boomerang/MXSSB-A58LJ-RJPHN-5VBV8-JQ3FW56.3 KiB36.7 KiB
client.messaging.adobe.com/latest/AdobeMessagingClient.js37.0 KiB20.3 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
commerce.adobe.com/store/_next/static/chunks/pages/_app-45508f141bcf3f3a.js2.3 MiB
/store/_next/static/chunks/pages/segmentation-c66873d2f58...270.5 KiB
commerce.adobe.com/store/_next/static/chunks/pages/_app.2bebcd9d.css185.0 KiB
www.adobe.com/marketingtech/d4d114c60e50/a0e989131fd5/launch-5dd5dd2177e6.min.js137.6 KiB
cdn.cookielaw.org/scripttemplates/202501.1.0/otBannerSdk.js112.8 KiB
/consent/7a5eb705-95ed-4cc4-a11d-0cc5760e93db/019caf6e-47...83.1 KiB
commerce.adobe.com/store/_next/static/chunks/framework-880e7eeca526ad46.js65.4 KiB
commerce.adobe.com/store/_next/static/chunks/styles.4b0be7e7.css64.6 KiB
/af/59b220/00000000000000007735dac8/31/l?primer=7cdcb44be...61.9 KiB
/af/55f17d/00000000000000007735dad8/31/l?primer=7cdcb44be...61.8 KiB

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
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
●Optimize DOM size
●Font display
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●User Timing marks and measures 44 user timings
●Avoid long main-thread tasks 14 long tasks found
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 220 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 10 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.
81

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
Unload event listeners are deprecated and will be removed.
s2.go-mpulse.net/boomerang/MXSSB-A58LJ-RJPHN-5VBV8-JQ3FW line 9, col 11504

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.

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 browser errors logged to the console
●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
85

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.

Link destinationLink Text
www.adobe.com/products/firefly.htmlLearn 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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`

Send Feedback