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

Site Health

Score: 75 / 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

HSTS header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

5 control(s) without accessible label

Accessibility › Form Accessibility

Cookie '_strava4_session' has no SameSite attribute

Security › Cookie Security

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.strava.com)](https://beavercheck.com/results/f466f70e-9ec7-4116-adb8-82444226116c)

HTML

<a href="https://beavercheck.com/results/f466f70e-9ec7-4116-adb8-82444226116c"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.strava.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.strava.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

Accessibility

100

Best Practices

100

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.

4.57 s

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

17.12 s

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

1.29 s

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.

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

17.23 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
/assets/fonts/Boathouse/Static/Boathouse-Regular-Oblique....	0.0 ms	43.7 KiB
/assets/fonts/Boathouse/Static/Boathouse-Medium.woff2	0.0 ms	42.0 KiB
/assets/fonts/Boathouse/Static/Boathouse-Regular.woff2	0.0 ms	41.8 KiB
consent.cookiebot.com/uc.js	202.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

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.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:42.752 source:map[column:32047 line:25 type:source-location url:https://appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js urlProvider:network]]]

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
ul#splide01-list > li#splide01-slide01 > div.ImageSequence_container__XzI3K > img.ImageSequence_staticLayer___rx6N `ul#splide01-list > li#splide01-slide01 > div.ImageSequence_container__XzI3K > img.ImageSequence_staticLayer___rx6N`	/assets/landing-pages/_next/static/media/static-layer.a3a...	294.6 KiB	265.4 KiB
div.Mobile_container__dzJVJ > section.Hero_container__dwBFb > picture.HeroBackgroundImage_picture__JiFsQ > img `div.Mobile_container__dzJVJ > section.Hero_container__dwBFb > picture.HeroBackgroundImage_picture__JiFsQ > img`	/assets/landing-pages/_next/static/media/background.1c5a9...	85.9 KiB	55.1 KiB
div.Mobile_container__dzJVJ > section.Section_container__4WNJ1 > div.ImageSequence_container__XzI3K > img.ImageSequence_fadeInLayer__yCtSt `div.Mobile_container__dzJVJ > section.Section_container__4WNJ1 > div.ImageSequence_container__XzI3K > img.ImageSequence_fadeInLayer__yCtSt`	web-assets.strava.com/assets/landing-pages/_next/static/media/frame.20c32256.png	34.1 KiB	24.5 KiB
Activity Summary `ul#splide01-list > li#splide01-slide01 > div.ImageSequence_container__XzI3K > img.ImageSequence_fadeInLayer__yCtSt`	web-assets.strava.com/assets/landing-pages/_next/static/media/frame.842c929b.png	24.3 KiB	21.3 KiB
Beacon `div.Mobile_container__dzJVJ > section.Section_container__4WNJ1 > div.ImageSequence_container__XzI3K > img.ImageSequence_staticLayer___rx6N`	/assets/landing-pages/_next/static/media/static-layer-fro...	9.6 KiB	8.4 KiB
div.Mobile_container__dzJVJ > section.Section_container__4WNJ1 > div.ImageSequence_container__XzI3K > img.ImageSequence_staticLayer___rx6N `div.Mobile_container__dzJVJ > section.Section_container__4WNJ1 > div.ImageSequence_container__XzI3K > img.ImageSequence_staticLayer___rx6N`	/assets/landing-pages/_next/static/media/static-layer.04c...	8.4 KiB	7.4 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:325.461 label:Time to first byte subpart:timeToFirstByte] map[duration:1168.859 label:Resource load delay subpart:resourceLoadDelay] map[duration:329.689 label:Resource load duration subpart:resourceLoadDuration] map[duration:724.352 label:Element render delay subpart:elementRenderDelay]]

lhId: page-1-IMG

nodeLabel: div.Mobile_container__dzJVJ > section.Hero_container__dwBFb > picture.HeroBackgroundImage_picture__JiFsQ > img

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

selector: div.Mobile_container__dzJVJ > section.Hero_container__dwBFb > picture.HeroBackgroundImage_picture__JiFsQ > img

snippet: <img alt="" src="https://web-assets.strava.com/assets/landing-pages/_next/static/media/back…" loading="lazy">

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

lhId: page-1-IMG

nodeLabel: div.Mobile_container__dzJVJ > section.Hero_container__dwBFb > picture.HeroBackgroundImage_picture__JiFsQ > img

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

selector: div.Mobile_container__dzJVJ > section.Hero_container__dwBFb > picture.HeroBackgroundImage_picture__JiFsQ > img

snippet: <img alt="" src="https://web-assets.strava.com/assets/landing-pages/_next/static/media/back…" loading="lazy">

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

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.

Estimated savings: 180 ms 40.3 KiB

URL	Transfer Size	Est Savings
web-assets.strava.com/assets/landing-pages/_next/static/css/53350daed7761b4b.css	30.1 KiB	29.0 KiB
	13.5 KiB	11.3 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.

Estimated savings: 3.4 s 570.2 KiB

URL	Transfer Size	Est Savings
/assets/landing-pages/_next/static/chunks/pages/_app-090d...	439.8 KiB	255.9 KiB
/assets/landing-pages/_next/static/chunks/59947-2e0be482d...	89.7 KiB	72.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-TP845S&l=googleTagManagerDataLayer	165.0 KiB	72.0 KiB
/gtag/js?id=G-ESZ0QKJW56&l=googleTagManagerDataLayer&cx=c...	174.2 KiB	63.4 KiB
/gtag/js?id=DC-15023759&l=googleTagManagerDataLayer&cx=c&...	128.8 KiB	63.3 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

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.strava.com/	962 ms	5.4 ms	1.2 ms
/assets/landing-pages/_next/static/chunks/pages/_app-090d...	814 ms	571 ms	152 ms
/assets/landing-pages/_next/static/chunks/framework-7f9d5...	570 ms	485 ms	15 ms
Unattributable	521 ms	36 ms	0.0 ms
consent.cookiebot.com/uc.js	384 ms	213 ms	11 ms
/gtag/js?id=G-ESZ0QKJW56&l=googleTagManagerDataLayer&cx=c...	343 ms	293 ms	46 ms
www.googletagmanager.com/gtm.js?id=GTM-TP845S&l=googleTagManagerDataLayer	189 ms	142 ms	45 ms
appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js	183 ms	7.1 ms	3.9 ms
/assets/landing-pages/_next/static/chunks/main-6f5274bcc7...	171 ms	156 ms	14 ms
/assets/landing-pages/_next/static/chunks/pages/index-c53...	166 ms	161 ms	5.0 ms
/gtag/js?id=DC-15023759&l=googleTagManagerDataLayer&cx=c&...	119 ms	88 ms	30 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	2.2 s
Other	926 ms
Style & Layout	461 ms
Script Parsing & Compilation	427 ms
Rendering	355 ms
Parse HTML & CSS	179 ms
Garbage Collection	71 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
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.

URL	Transfer Size
/assets/landing-pages/_next/static/media/background-layer...	461.9 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
/assets/landing-pages/_next/static/media/summary.206cbbe0...	156.6 KiB
/gtag/js?id=DC-15023759&l=googleTagManagerDataLayer&cx=c&...	128.8 KiB
www.strava.com/	127.4 KiB
/assets/landing-pages/_next/static/chunks/59947-2e0be482d...	90.6 KiB
/assets/landing-pages/_next/static/media/background.1c5a9...	86.4 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

●Font display

●Modern HTTP

●Network dependency tree

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 13 long tasks found

●Avoid non-composited animations 5 animated elements found

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

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 220 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

○INP breakdown

○Avoid large layout shifts

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.

Failing Elements
GET APP `div.Header_items__xlCyf > div.SmartBanner_wrapper__5eRa3 > div.SmartBanner_smartBanner__8x4sY > a.Button_btn__EdK33`
Sign Up `div.Header_items__xlCyf > div.MobileNav_container__ki3E9 > div.MobileNav_right__xVNWr > a.Button_btn__EdK33`
Join Us Now `div.Mobile_container__dzJVJ > section.Hero_container__dwBFb > div.Hero_overlay__pFJ6Z > a.PillButton_pillButton__lT2Fo`
Join Us Now `div.Mobile_container__dzJVJ > section.Section_container__4WNJ1 > a.JoinTryCta_container__ZJPGJ > h4`
EXPLORE `div.Community_container__WfglZ > section.Section_container__4WNJ1 > a.PillButton_pillButton__lT2Fo > span`
Join Us Now `div.Community_container__WfglZ > section.Section_container__4WNJ1 > a.JoinTryCta_container__ZJPGJ > h4`
STRAVA SUBSCRIPTION `div.Homepage_container__m8Vvy > div.Mobile_container__dzJVJ > section.Section_container__4WNJ1 > span.Subscription_header__7D445`
Strava Features `div.Mobile_container__dzJVJ > div.Summary_container__vWu0R > div.Summary_features__ixBz6 > h3`
EXPLORE `div.Summary_container__vWu0R > div.Summary_features__ixBz6 > a.PillButton_pillButton__lT2Fo > span`
Log In `li > ul > li > a.Footer_highlight__3ACCZ`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Failing Elements
If you're active, Strava was made for you. Our mobile app and website enhance t… `div.Homepage_container__m8Vvy > div.Mobile_container__dzJVJ > section.Section_container__4WNJ1 > h3`
Open, tap, go. `div.JoinAndStay_content__acYij > div.JoinAndStay_paragraphs__dTdy9 > div.JoinAndStay_paragraph__guLbH > h4`
Track & Analyze `div.ItemGrid_container__lWVNA > div.ItemGrid_items__NEEM5 > div.ItemGrid_item__Z0wTV > h4`
Track & Analyze `div.ItemGrid_container__lWVNA > div.ItemGrid_items__NEEM5 > div.ItemGrid_item__Z0wTV > h4`

These are opportunities to improve keyboard navigation in your application.

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

●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

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

100

Best Practices

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.

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

●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

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

100

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.

1.31 s

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

2.43 s

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

60 ms

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

0.021

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

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

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

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

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.

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

	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.

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

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.

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.

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

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.

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

	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

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

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.

	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

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

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

Browse & Analyze

Learn

Results for https://www.strava.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Navigation

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Best Practices

User Experience

General

SEO

Keyboard Shortcuts