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
/wetransfer/2504/static-ultimateanimated/3_xrmZaA/_r3.gif	0.0 ms	568.3 KiB
js.stripe.com/v3	120.0 s	225.0 KiB
/genie/wetransfer/2504/static-ultimateanimated/3_xrmZaA/b...	0.0 ms	107.5 KiB
/wetransfer/2504/static-ultimateanimated/3_xrmZaA/Copy3.svg	0.0 ms	86.0 KiB
nolan.wetransfer.net/apps/desktop-web-renderer/0.9.4/main.f2f5d90813aacde5.js	0.0 ms	55.8 KiB
www.datadoghq-browser-agent.com/eu1/v5/datadog-rum-slim.js	14400.0 s	36.2 KiB
m.stripe.network/out-4.5.45.js	300.0 s	16.5 KiB
scripts.clarity.ms/0.8.59/clarity.js	86400.0 s	26.2 KiB
/wetransfer/2504/static-ultimateanimated/1_hUYzQC/Button.svg	0.0 ms	8.4 KiB
apps.rokt.com/icons/rokt-icons.woff	1200.0 s	7.7 KiB
public.profitwell.com/js/profitwell.js?auth=1a33eb12b20b92f6b89c398e023e2ca1	14400.0 s	9.7 KiB
/genie/wetransfer/2504/static-ultimateanimated/3_xrmZaA/4...	0.0 ms	2.0 KiB
/i.gif?e=eyJ2IjoiMS4xNCIsImF2Ijo0Mjg5MjEsImF0Ijo5NTksImJ0...	0.0 ms	136 B
scripts.clarity.ms/0.8.59/clarity.js	86400.0 s	0 B

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
cdn.wetransfer.com/_next/static/media/GT-Super-WT-Super.3397811e.woff	30 ms

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:1.195 source:map[column:73398 line:2 type:source-location url:https://scripts.clarity.ms/0.8.59/clarity.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:35.77 source:map[type:text value:[unattributed]]] map[reflowTime:0.327 source:map[column:40094 line:0 type:source-location url:https://cdn.wetransfer.com/_next/static/chunks/4664.87840722f23b911d.js urlProvider:network]] map[reflowTime:1.195 source:map[column:31518 line:1 type:source-location url:https://scripts.clarity.ms/0.8.59/clarity.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:106.703 label:Time to first byte subpart:timeToFirstByte] map[duration:3154.407 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-P

nodeLabel: To continue, please agree to our Terms of Service, and acknowledge our Privacy …

path: 1,HTML,1,BODY,0,DIV,0,DIV,1,DIV,1,DIV,1,DIV,0,DIV,0,DIV,2,P

selector: div.transfer-visibleWrapper > div.transfer__window > div.transfer__contents > p.terms_info

snippet: <p class="terms_info">

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

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
/wetransfer/2504/static-ultimateanimated/3_xrmZaA/_r3.gif	567.9 KiB	532.8 KiB

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.

URL	Transfer Size	Duration
/css2?family=Dancing+Script&family=Kalam&family=Unna&disp...	1.1 KiB	266 ms

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.

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: 1.0 s 1.3 MiB

URL	Transfer Size	Est Savings
cdn.wetransfer.com/_next/static/chunks/7354.30a5a0411a6507e5.js	805.4 KiB	273.1 KiB
js.stripe.com/v3	224.6 KiB	163.4 KiB
blob:https://wetransfer.com/ad72f200-adfe-4a50-934e-d5cc1ef70c0c	358.0 KiB	152.8 KiB
accounts.google.com/gsi/client	95.6 KiB	80.4 KiB
tagging.wetransfer.com/gtm.js?id=GTM-NS54WBW	172.6 KiB	72.4 KiB
tagging.wetransfer.com/gtm.js?id=GTM-NS54WBW	172.6 KiB	71.1 KiB
accounts.google.com/gsi/client	95.6 KiB	68.6 KiB
cdn.wetransfer.com/_next/static/chunks/9338.993d9483534aa86f.js	122.4 KiB	67.9 KiB
/gtag/js?id=G-0M019DTWVR&cx=c&gtm=4e64h1&sign=68f7c7b92e6...	159.7 KiB	63.5 KiB
cdn.wetransfer.com/_next/static/chunks/b7bfefd8.9b1f2da38a41583d.js	70.7 KiB	61.7 KiB
cdn.wetransfer.com/_next/static/chunks/7242.f78322a12cd2966a.js	132.5 KiB	51.1 KiB
cdn.wetransfer.com/_next/static/chunks/1639.4df9c4041275b2cc.js	85.0 KiB	48.2 KiB
cdn.wetransfer.com/_next/static/chunks/3317-ab04cad15aa1b4da.js	52.1 KiB	36.4 KiB
cdn.wetransfer.com/_next/static/chunks/4771.eab54f30f88ab428.js	130.4 KiB	31.0 KiB
cdn.wetransfer.com/_next/static/chunks/5366.0187f510a715a100.js	52.7 KiB	26.7 KiB
cdn.wetransfer.com/_next/static/chunks/8633.3602a101028b8f21.js	32.4 KiB	25.1 KiB
cdn.wetransfer.com/_next/static/chunks/a7be5a01.5020bc92ad1f42c8.js	29.4 KiB	23.0 KiB
cdn.wetransfer.com/_next/static/chunks/main-076b1c0380ea4934.js	38.6 KiB	22.7 KiB
cdn.wetransfer.com/_next/static/chunks/pages/_app-f6f58138673d109c.js	27.4 KiB	21.1 KiB
cdn.wetransfer.com/_next/static/chunks/main-076b1c0380ea4934.js	38.6 KiB	20.7 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.

URL	Total CPU Time	Script Evaluation	Script Parse
cdn.wetransfer.com/_next/static/chunks/framework-ca2f8fe4a887959b.js	797 ms	691 ms	19 ms
tagging.wetransfer.com/gtm.js?id=GTM-NS54WBW	264 ms	224 ms	32 ms
cdn.wetransfer.com/_next/static/chunks/7354.30a5a0411a6507e5.js	255 ms	156 ms	60 ms
Unattributable	215 ms	21 ms	0.0 ms
cdn.wetransfer.com/_next/static/chunks/1639.4df9c4041275b2cc.js	171 ms	151 ms	9.5 ms
wetransfer.com/	148 ms	5.7 ms	0.4 ms
blob:https://wetransfer.com/ad72f200-adfe-4a50-934e-d5cc1ef70c0c	99 ms	88 ms	5.9 ms
/gtag/js?id=G-0M019DTWVR&cx=c&gtm=4e64h1&sign=68f7c7b92e6...	86 ms	74 ms	11 ms
scripts.clarity.ms/0.8.59/clarity.js	78 ms	69 ms	4.4 ms
js.stripe.com/v3	69 ms	48 ms	20 ms
cdn.wetransfer.com/_next/static/chunks/9338.993d9483534aa86f.js	64 ms	54 ms	9.4 ms
cdn.wetransfer.com/_next/static/chunks/pages/_app-f6f58138673d109c.js	59 ms	39 ms	13 ms
apps.rokt.com/wsdk/integrations/launcher.js	52 ms	48 ms	3.0 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.

Category	Time Spent
Script Evaluation	1.8 s
Other	422 ms
Script Parsing & Compilation	300 ms
Style & Layout	112 ms
Parse HTML & CSS	72 ms
Garbage Collection	70 ms
Rendering	12 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 reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	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
cdn.wetransfer.com/_next/static/chunks/7354.30a5a0411a6507e5.js	805.7 KiB
/wetransfer/2504/static-ultimateanimated/3_xrmZaA/_r3.gif	568.3 KiB
apps.rokt.com/wsdk/plugins/widget/modern/index.bc13226619f0851fb148.js	253.4 KiB
js.stripe.com/v3	225.0 KiB
tagging.wetransfer.com/gtm.js?id=GTM-NS54WBW	173.0 KiB
/gtag/js?id=G-0M019DTWVR&cx=c&gtm=4e64h1&sign=68f7c7b92e6...	160.0 KiB
apps.rokt.com/wsdk/plugins/dcui/index.f1d191594906abde4e6a.js	146.0 KiB
cdn.wetransfer.com/_next/static/chunks/7242.f78322a12cd2966a.js	134.7 KiB
cdn.wetransfer.com/_next/static/chunks/4771.eab54f30f88ab428.js	130.8 KiB
cdn.wetransfer.com/_next/static/chunks/9338.993d9483534aa86f.js	122.8 KiB

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

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 13 user timings

●Avoid long main-thread tasks 11 long tasks found

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

●Network Requests

●Network Round Trip Times 170 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 70 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

○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
Features `div.styles_module_menuGroup__8c684e1f > div.styles_module_menuBar__8c684e1f > div.styles_module_fullMenu__8c684e1f > span#wt-popover-target-uCdfv0YkO0xv-V0rsJY6d`
Use cases `div.styles_module_menuGroup__8c684e1f > div.styles_module_menuBar__8c684e1f > div.styles_module_fullMenu__8c684e1f > span#wt-popover-target-OfVTbGMv0puFx-ldPn2im`
Resources `div.styles_module_menuGroup__8c684e1f > div.styles_module_menuBar__8c684e1f > div.styles_module_fullMenu__8c684e1f > span#wt-popover-target-604hU2w55kClvh9Qtv0pR`
4 `div.styles_module_menuGroup__8c684e1f > div.styles_module_menuBar__8c684e1f > div.styles_module_productUpdatesSection__5b9cea60 > span#wt-popover-target-D0qjhJ1KZI4kAQku7JoQK`

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.

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

●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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

●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

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

○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

○ARIA IDs are unique

○No form fields have multiple labels

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

○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

○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

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
auth.wetransfer.com/oauth/token	`Failed to load resource: the server responded with a status of 403 ()`
auth.wetransfer.com/oauth/token	`Failed to load resource: the server responded with a status of 403 ()`
wetransfer.com/	`Not signed in with the identity provider.`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

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	Map URL
tagging.wetransfer.com/gtm.js?id=GTM-NS54WBW
tagging.wetransfer.com/gtm.js?id=GTM-NS54WBW
cdn.wetransfer.com/_next/static/chunks/7354.30a5a0411a6507e5.js
cdn.wetransfer.com/_next/static/chunks/4771.eab54f30f88ab428.js
apps.rokt.com/wsdk/integrations/launcher.js	sourcemaps-wsdk.roktinternal.com/integrations/launcher.2.9701.0.js.map

●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

●Ensure CSP is effective against XSS attacks

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

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`