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
/0N3XMOl0/captcha/PX0N3XMOl0/captcha.js?a=c&u=ac2576c0-3e...	600.0 s	266.8 KiB
crcldu.com/bd/auditor.js?v=1776898200000	120.0 s	134.3 KiB
client.px-cloud.net/PX0N3XMOl0/main.min.js	600.0 s	111.8 KiB
cdn.attn.tv/tag/4-latest/unified-tag.js?v=4-latest_5472150738	300.0 s	49.3 KiB
www.urbanoutfitters.com/static/uologo.png	3600.0 s	2.5 KiB
cdn.attn.tv/growth-tag-assets/client-configs/3EO.js	120.0 s	2.0 KiB
cdn.attn.tv/urbanoutfitters/dtag.js	120.0 s	1.9 KiB
static.urbanoutfitters.com/static/v3/assets/us-DMB68NKF.js	3600.0 s	533 B
static.urbanoutfitters.com/static/v3/assets/fr-Bs0PlRkf.js	3600.0 s	529 B
static.urbanoutfitters.com/static/v3/assets/us-K8hZK4rW.png	3600.0 s	281 B

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:267.972 source:map[column:133700 line:2 type:source-location url:https://client.px-cloud.net/PX0N3XMOl0/main.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:0.156 source:map[column:272950 line:1 type:source-location url:https://www.urbanoutfitters.com/0N3XMOl0/captcha/PX0N3XMOl0/captcha.js?a=c&u=ac2576c0-3e9d-11f1-8ce2-3b56869164bc&v=ab440521-3e9d-11f1-ade2-cfaf2d1d7045&m=0&b=aHR0cHM6Ly93d3cudXJiYW5vdXRmaXR0ZXJzLmNvbS9mci1mci8/YXI9dW8tdXMsdW8tZnI= urlProvider:network]] map[reflowTime:0.813 source:map[column:217192 line:1 type:source-location url:https://www.urbanoutfitters.com/0N3XMOl0/captcha/PX0N3XMOl0/captcha.js?a=c&u=ac2576c0-3e9d-11f1-8ce2-3b56869164bc&v=ab440521-3e9d-11f1-ade2-cfaf2d1d7045&m=0&b=aHR0cHM6Ly93d3cudXJiYW5vdXRmaXR0ZXJzLmNvbS9mci1mci8/YXI9dW8tdXMsdW8tZnI= urlProvider:network]] map[reflowTime:0.374 source:map[column:275034 line:1 type:source-location url:https://www.urbanoutfitters.com/0N3XMOl0/captcha/PX0N3XMOl0/captcha.js?a=c&u=ac2576c0-3e9d-11f1-8ce2-3b56869164bc&v=ab440521-3e9d-11f1-ade2-cfaf2d1d7045&m=0&b=aHR0cHM6Ly93d3cudXJiYW5vdXRmaXR0ZXJzLmNvbS9mci1mci8/YXI9dW8tdXMsdW8tZnI= urlProvider:network]] map[reflowTime:0.224 source:map[column:285440 line:1 type:source-location url:https://www.urbanoutfitters.com/0N3XMOl0/captcha/PX0N3XMOl0/captcha.js?a=c&u=ac2576c0-3e9d-11f1-8ce2-3b56869164bc&v=ab440521-3e9d-11f1-ade2-cfaf2d1d7045&m=0&b=aHR0cHM6Ly93d3cudXJiYW5vdXRmaXR0ZXJzLmNvbS9mci1mci8/YXI9dW8tdXMsdW8tZnI= urlProvider:network]] map[reflowTime:0.281 source:map[type:text value:[unattributed]]] map[reflowTime:0.07 source:map[column:158221 line:1 type:source-location url:https://client.px-cloud.net/PX0N3XMOl0/main.min.js urlProvider:network]] map[reflowTime:267.972 source:map[column:133827 line:1 type:source-location url:https://client.px-cloud.net/PX0N3XMOl0/main.min.js urlProvider:network]]]

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

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.

Lists the toplevel main thread tasks that executed during page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Collection of useful page vitals.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 3.3 s

URL	Time Spent
urbanoutfitters.com/	251 ms
www.urbanoutfitters.com/	425 ms
www.urbanoutfitters.com/fr-fr?ar=uo-us,uo-fr	345 ms
www.urbanoutfitters.com/fr-fr/?ar=uo-us,uo-fr	2.3 s
www.urbanoutfitters.com/fr-fr/?ar=uo-us,uo-fr	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

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.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 230 ms 113.4 KiB

URL	Transfer Size	Est Savings
static.urbanoutfitters.com/static/v3/assets/app-libraries-zP-Xul63.js	226.6 KiB	72.8 KiB
static.urbanoutfitters.com/static/v3/assets/app-wuhGshlm.js	149.5 KiB	40.5 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: 70 ms 62.3 KiB

URL	Transfer Size	Est Savings
static.urbanoutfitters.com/static/v3/assets/BaseLayout-blt_rsjG.js	95.1 KiB	42.0 KiB
www.urbanoutfitters.com/fr-fr/?ar=uo-us,uo-fr	114.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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
The page has an unload handler in the main frame.	Actionable
Only pages with a status code of 2XX can be cached.	Not actionable

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.

URL	Transfer Size
/q602vtcuu3w3/6vXT96sCct191ix6B0yhNt/cbc4cda2b67b613bb0bc...	448.8 KiB
/q602vtcuu3w3/1T5GbuQDeNetZplig3eQ4g/416e458a0590b9a67ce6...	396.4 KiB
/0N3XMOl0/captcha/PX0N3XMOl0/captcha.js?a=c&u=ac2576c0-3e...	266.8 KiB
static.urbanoutfitters.com/static/v3/assets/app-libraries-zP-Xul63.js	226.9 KiB
/q602vtcuu3w3/5v7ZHpRjaARr3JvfPQuky3/8799aef4d064869905f5...	209.5 KiB
www.googletagmanager.com/gtag/js?id=G-BBMWPLK0E5&cx=c&gtm=4e64m0h2	167.5 KiB
/q602vtcuu3w3/5WMXQ3zvthXtwkAvBPFFWB/4efdf15ea02506d804c8...	166.9 KiB
static.urbanoutfitters.com/static/v3/assets/app-wuhGshlm.js	149.7 KiB
/q602vtcuu3w3/74n2WJpPQGLcjU8nbX8Xfd/2a384dd4b29504bccbbf...	142.6 KiB
crcldu.com/bd/auditor.js?v=1776898200000	134.3 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
Logo `body > div#px-captcha-wrapper > div.px-captcha-container > img.px-captcha-logo`	www.urbanoutfitters.com/static/uologo.png

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

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

●User Timing marks and measures 6 user timings

●Avoid non-composited animations 1 animated element found

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 150 ms

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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.

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
Reference ID ac2576c0-3e9d-11f1-8ce2-3b56869164bc `body > div#px-captcha-wrapper > div.px-captcha-container > div.px-captcha-refid`

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

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

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

●Document has a `<title>` element

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

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

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

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

○Deprecated ARIA roles were not used

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

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○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

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

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

○Buttons have an accessible name

○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

○Heading elements appear in a sequentially-descending order

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

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Touch targets have sufficient size and spacing.

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

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

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 / Warning	Source
Unload event listeners are deprecated and will be removed.	/0N3XMOl0/captcha/PX0N3XMOl0/captcha.js?a=c&u=ac2576c0-3e... line 1, col 206600

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
static.urbanoutfitters.com/static/v3/assets/app-libraries-zP-Xul63.js line 44, col 13994	`(Blocked by PX) Could not load cart count [object Object]`
static.urbanoutfitters.com/static/v3/assets/app-wuhGshlm.js line 1, col 75656	`(Blocked by PX) Failed to fetch translations (SiteSwitchBanner) [object Object]`
static.urbanoutfitters.com/static/v3/assets/app-wuhGshlm.js line 1, col 75656	`(Blocked by PX) Failed to load contentful Category config [object Object]`
api.urbanoutfitters.com/api/checkout/v0/uo-fr/minicart?cacheBuster=1776898234262	`Failed to load resource: the server responded with a status of 403 ()`
/api/content/v1/uo-fr/entries?include=2&contentfulEnviron...	`Failed to load resource: the server responded with a status of 403 ()`
/api/content/v1/uo-fr/entries?include=1&contentfulEnviron...	`Failed to load resource: the server responded with a status of 403 ()`
/api/content/v1/uo-fr/entries?include=1&contentfulEnviron...	`Failed to load resource: the server responded with a status of 403 ()`
www.urbanoutfitters.com/fr-fr/?ar=uo-us,uo-fr	`Failed to load resource: the server responded with a status of 403 (Forbidden)`

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

Crawling and Indexing

Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.

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

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