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.

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.Homepage_container__m8Vvy > div.Desktop_container__GSOOB > picture.ImagePanel_picture__FQ_Pd > img.ImagePanel_center__dgOma

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

selector: div.Homepage_container__m8Vvy > div.Desktop_container__GSOOB > picture.ImagePanel_picture__FQ_Pd > img.ImagePanel_center__dgOma

snippet: <img class="ImagePanel_center__dgOma" loading="lazy" alt="" role="presentation" src="https://web-assets.strava.com/assets/landing-pages/_next/static/media/Desk…" width="" height="" data-testid="desktop/DesktopWide-Col-1-column">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
/assets/fonts/Boathouse/Static/Boathouse-Medium.woff2	0.0 ms	42.1 KiB
/assets/fonts/Boathouse/Static/Boathouse-Regular.woff2	0.0 ms	41.8 KiB
consent.cookiebot.com/uc.js	184.0 s	35.7 KiB
appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js	86400.0 s	17.4 KiB

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
div.Homepage_container__m8Vvy > div.Desktop_container__GSOOB > picture.ImagePanel_picture__FQ_Pd > img.ImagePanel_center__dgOma `div.Homepage_container__m8Vvy > div.Desktop_container__GSOOB > picture.ImagePanel_picture__FQ_Pd > img.ImagePanel_center__dgOma`	/assets/landing-pages/_next/static/media/DesktopWide-Col-...	627.0 KiB	574.4 KiB
div.Desktop_container__GSOOB > div.Desktop_columnWrapper__0v2TN > picture.ImagePanel_picture__FQ_Pd > img.ImagePanel_center__dgOma `div.Desktop_container__GSOOB > div.Desktop_columnWrapper__0v2TN > picture.ImagePanel_picture__FQ_Pd > img.ImagePanel_center__dgOma`	/assets/landing-pages/_next/static/media/DesktopWide-Col-...	455.8 KiB	403.2 KiB
device `div.Desktop_container__GSOOB > div.Desktop_columnWrapper__0v2TN > picture.Desktop_device__jz4Ne > img`	/assets/landing-pages/_next/static/media/Device-en-US@1x....	29.2 KiB	19.7 KiB

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

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.

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

Diagnostics

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 29.1 KiB

URL	Transfer Size	Est Savings
web-assets.strava.com/assets/landing-pages/_next/static/css/53350daed7761b4b.css	30.1 KiB	29.1 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: 140 ms 593.1 KiB

URL	Transfer Size	Est Savings
/assets/landing-pages/_next/static/chunks/pages/_app-090d...	439.8 KiB	255.8 KiB
/assets/landing-pages/_next/static/chunks/59947-2e0be482d...	89.7 KiB	72.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-TP845S&l=googleTagManagerDataLayer	165.0 KiB	71.1 KiB
/gtag/js?id=DC-15023759&l=googleTagManagerDataLayer&cx=c&...	128.8 KiB	62.3 KiB
/gtag/js?id=G-ESZ0QKJW56&l=googleTagManagerDataLayer&cx=c...	174.2 KiB	62.0 KiB
/e47bebbc-d5c7-470a-a8f6-6d858aa50ff4/cc.js?renew=false&r...	112.2 KiB	26.1 KiB
consent.cookiebot.com/uc.js	35.4 KiB	22.4 KiB
/assets/landing-pages/_next/static/chunks/main-6f5274bcc7...	39.0 KiB	20.9 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
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
/assets/landing-pages/_next/static/media/DesktopWide-Col-...	628.5 KiB
/assets/landing-pages/_next/static/media/DesktopWide-Col-...	456.8 KiB
/assets/landing-pages/_next/static/chunks/pages/_app-090d...	440.2 KiB
/assets/landing-pages/_next/static/media/static-layer.a3a...	295.4 KiB
/gtag/js?id=G-ESZ0QKJW56&l=googleTagManagerDataLayer&cx=c...	174.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-TP845S&l=googleTagManagerDataLayer	165.3 KiB
/gtag/js?id=DC-15023759&l=googleTagManagerDataLayer&cx=c&...	128.8 KiB
www.strava.com/	127.3 KiB
/e47bebbc-d5c7-470a-a8f6-6d858aa50ff4/cc.js?renew=false&r...	112.4 KiB
/assets/landing-pages/_next/static/chunks/59947-2e0be482d...	90.6 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
div.Homepage_container__m8Vvy > div.Desktop_container__GSOOB > picture.ImagePanel_picture__FQ_Pd > img.ImagePanel_center__dgOma `div.Homepage_container__m8Vvy > div.Desktop_container__GSOOB > picture.ImagePanel_picture__FQ_Pd > img.ImagePanel_center__dgOma`	/assets/landing-pages/_next/static/media/DesktopWide-Col-...
div.Desktop_container__GSOOB > div.Desktop_columnWrapper__0v2TN > picture.ImagePanel_picture__FQ_Pd > img.ImagePanel_center__dgOma `div.Desktop_container__GSOOB > div.Desktop_columnWrapper__0v2TN > picture.ImagePanel_picture__FQ_Pd > img.ImagePanel_center__dgOma`	/assets/landing-pages/_next/static/media/DesktopWide-Col-...

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

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 12 user timings

●JavaScript execution time 0.5 s

●Minimizes main-thread work 0.9 s

●Avoid long main-thread tasks 3 long tasks found

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 230 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 250 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

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
Log In `div.Desktop_container__GSOOB > div.Desktop_middleColumn__pAOKb > p.Desktop_alreadyAMember__y5voZ > a`
Sign Up With Email `div.Desktop_container__GSOOB > div.Desktop_middleColumn__pAOKb > div.RegistrationPanel_container__zgeYj > button.Button_btn__EdK33`
Log In `li > ul > li > a.Footer_highlight__3ACCZ`

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

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

○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

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
device `div.Desktop_container__GSOOB > div.Desktop_columnWrapper__0v2TN > picture.Desktop_device__jz4Ne > img`	/assets/landing-pages/_next/static/media/Device-en-US@1x....	295 x 270 (1.09)	516 x 476 (1.08)
Get it on Google Play `li > a > picture > img`	/assets/landing-pages/_next/static/media/play-store-en-US...	105 x 35 (3.00)	105 x 32 (3.28)

General

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
/assets/landing-pages/_next/static/chunks/pages/_app-090d...

●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

●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

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`