Skip to content
https://livestrong.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

21

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.511326] map[node:map[boundingRect:map[bottom:7363 height:6814 left:0 right:412 top:549 width:412] lhId:page-1-MAIN nodeLabel:WE ENSURE EVERYONE AFFECTED BY CANCER HAS THE RESOURCES THEY NEED TO THRIVE In… path:6,HTML,6,BODY,4,MAIN selector:body.home > main#livestrong-main snippet:<main class="livestrong-main" id="livestrong-main"> type:node] score:0.349929] map[node:map[boundingRect:map[bottom:7363 height:6814 left:0 right:412 top:549 width:412] lhId:page-1-MAIN nodeLabel:WE ENSURE EVERYONE AFFECTED BY CANCER HAS THE RESOURCES THEY NEED TO THRIVE In… path:6,HTML,6,BODY,4,MAIN selector:body.home > main#livestrong-main snippet:<main class="livestrong-main" id="livestrong-main"> type:node] score:0.158194] map[node:map[boundingRect:map[bottom:1534 height:541 left:1 right:411 top:993 width:410] lhId:page-2-DIV nodeLabel:Chat Apply Community Resources path:6,HTML,6,BODY,4,MAIN,0,DIV,0,DIV,2,DIV,0,WL-MODAL,a,#document-fragment,2,DIV,1,DIV,1,DIV,2,DIV selector:div.wl-embedded-container > div.modal-content > div.chat-section > div.chat-tabs snippet:<div class="chat-tabs"> type:node] score:0.003203]]

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:42.568 source:map[column:29819 line:2 type:source-location url:https://livestrong.org/wp-content/themes/livestrong/webpack/dist/scripts/theme-scripts.min.js?ver=1776424976 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:43.163 source:map[column:149513 line:2 type:source-location url:https://cdn.fundraiseup.com/widget/AXPBBAQJ urlProvider:network]] map[reflowTime:0.449 source:map[column:120656 line:1 type:source-location url:https://static.fundraiseup.com/elementsApi.c0fc24ed4d35f527.js urlProvider:network]] map[reflowTime:13.19 source:map[type:text value:[unattributed]]] map[reflowTime:1.106 source:map[column:17535 line:85 type:source-location url:https://static.fundraiseup.com/elements-vendors.c590dd34e4f5ac29.js urlProvider:network]] map[reflowTime:13.575 source:map[column:29930 line:1 type:source-location url:https://livestrong.org/wp-content/themes/livestrong/webpack/dist/scripts/theme-scripts.min.js?ver=1776424976 urlProvider:network]] map[reflowTime:0.473 source:map[column:7318 line:5518 type:source-location url:https://cdn.whitelabel.ai/widget/latest/widget.iife.js urlProvider:network]] map[reflowTime:28.993 source:map[column:29882 line:1 type:source-location url:https://livestrong.org/wp-content/themes/livestrong/webpack/dist/scripts/theme-scripts.min.js?ver=1776424976 urlProvider:network]]]

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: Two men cycling
path: 6,HTML,6,BODY,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,IMG
selector: div.livestrong-max-width > div.livestrong-grid > div.livestrong-col-md-4 > img
snippet: <img loading="lazy" alt="Two men cycling" src=" https://livestrong.org/wp-content/uploads/2026/04/Ride-for-Resili…">

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

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.

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.

URLResource SizeEst Savings
Father in cyclist gear embracing daughter with rose div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/FatherDaughter.jpg197.1 KiB182.9 KiB
Portrait of a woman looking into the distance div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/Fayruz_Benyousef-8701-Edit.jpg65.4 KiB55.1 KiB
Smiling child holding up art project div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/LICENSED_shutterstock_1467879026.jpg60.4 KiB50.9 KiB
Two men cycling div.livestrong-max-width > div.livestrong-grid > div.livestrong-col-md-4 > img
/wp-content/uploads/2026/04/Ride-for-Resilience-Loop-head...42.8 KiB20.4 KiB

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

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.

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
WE ENSURE EVERYONE AFFECTED BY CANCER HAS THE RESOURCES THEY NEED TO THRIVE In… body.home > main#livestrong-main
0.350
WE ENSURE EVERYONE AFFECTED BY CANCER HAS THE RESOURCES THEY NEED TO THRIVE In… body.home > main#livestrong-main
0.158
Chat Apply Community Resources div.wl-embedded-container > div.modal-content > div.chat-section > div.chat-tabs
0.003

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 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: 150 ms 24.5 KiB
URLTransfer SizeEst Savings
/wp-content/themes/livestrong/webpack/dist/styles/theme-s...27.7 KiB24.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.

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
/wp-content/themes/livestrong/webpack/dist/scripts/theme-...1.8 s914 ms61 ms
Unattributable922 ms77 ms0.0 ms
cdn.whitelabel.ai/widget/latest/widget.iife.js886 ms455 ms331 ms
livestrong.org/?utm_source=dotcom&utm_medium=referral858 ms602 ms30 ms
static.fundraiseup.com/checkout.9e2624d0be733d7f.js456 ms268 ms187 ms
cdn.fundraiseup.com/widget/AXPBBAQJ410 ms183 ms48 ms
www.googletagmanager.com/gtm.js?id=GTM-TSR34SPC372 ms306 ms57 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js337 ms246 ms75 ms
js-agent.newrelic.com/nr-spa-1.313.0.min.js306 ms234 ms16 ms
www.googletagmanager.com/gtag/js?id=G-ZH92XFBC92&cx=c&gtm=4e64h1h1284 ms212 ms38 ms
cdn.gtranslate.net/widgets/latest/dwf.js?ver=6.9.4235 ms208 ms1.6 ms
www.googletagmanager.com/gtag/js?id=DC-14265039&cx=c&gtm=4e64h1h1231 ms198 ms30 ms
www.googletagmanager.com/gtag/js?id=AW-17178805589&cx=c&gtm=4e64h1h1207 ms177 ms29 ms
www.googletagmanager.com/gtag/js?id=AW-853766454&cx=c&gtm=4e64h1h1198 ms165 ms32 ms
www.googletagmanager.com/gtag/js?id=AW-1056869159&cx=c&gtm=4e64h1h1192 ms162 ms29 ms
static.fundraiseup.com/9483.5049a274cd651063.js174 ms133 ms0.8 ms
t.contentsquare.net/uxa/smb/tag.js161 ms100 ms56 ms
connect.facebook.net/en_US/fbevents.js107 ms81 ms25 ms
/onsite/js/build-preview/commit-019948276f5166670cb8f0c64...101 ms90 ms6.3 ms
/signals/config/1139778359401597?v=2.9.303&r=stable&domai...98 ms87 ms11 ms
static.fundraiseup.com/elementsApi.c0fc24ed4d35f527.js70 ms57 ms10 ms
static.fundraiseup.com/elements-langs-vendors.86315bee0669542d.js70 ms1.1 ms68 ms
livestrong.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.161 ms49 ms6.6 ms
/onsite/js/build-preview/commit-019948276f5166670cb8f0c64...58 ms50 ms2.3 ms
/onsite/js/build-preview/commit-019948276f5166670cb8f0c64...55 ms40 ms6.9 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation5.5 s
Script Parsing & Compilation1.3 s
Other1.3 s
Style & Layout771 ms
Garbage Collection135 ms
Rendering126 ms
Parse HTML & CSS111 ms

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
Father in cyclist gear embracing daughter with rose div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/FatherDaughter.jpg
Smiling child holding up art project div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/LICENSED_shutterstock_1467879026.jpg
Portrait of a woman looking into the distance div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/Fayruz_Benyousef-8701-Edit.jpg
Portrait of a woman cancer survivor div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/Nicole-DeBusk.jpg
A smiling man wearing a black hat, glasses, and a yellow shirt div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/Ryan-Becerra-1.jpg
Portrait of a smiling man div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/Kristoffer_Lands-8778-Edit.jpg
A teen girl sitting in a field div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/Valery-Livestrong-8523-Edit.jpg
Father in cyclist gear embracing daughter with rose div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/FatherDaughter.jpg
Smiling child holding up art project div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/LICENSED_shutterstock_1467879026.jpg
Portrait of a woman looking into the distance div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/Fayruz_Benyousef-8701-Edit.jpg
Portrait of a woman cancer survivor div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/Nicole-DeBusk.jpg
A smiling man wearing a black hat, glasses, and a yellow shirt div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/Ryan-Becerra-1.jpg
Portrait of a smiling man div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/Kristoffer_Lands-8778-Edit.jpg
A teen girl sitting in a field div.livestrong-survivor-first-section > div.livestrong-survivor-first-section__portraits > div.livestrong-survivor-first-section__portrait > img
livestrong.org/wp-content/uploads/2024/04/Valery-Livestrong-8523-Edit.jpg
Two men cycling div.livestrong-max-width > div.livestrong-grid > div.livestrong-col-md-4 > img
/wp-content/uploads/2026/04/Ride-for-Resilience-Loop-head...

More information about the performance of your application. These numbers don't directly affect the Performance score.

Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 5 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 5 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 320 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 10 ms
INP breakdown
89

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
WHAT CAN WE HELP YOU WITH TODAY? Close search Search in https://livestrong.org/… body.home > header.livestrong-header > div.livestrong-max-width--large > div.livestrong-header__search

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
HOW WE HELP How We Help Livestrong Fertility Livestrong at the YMCA CancerFit f… header.livestrong-header > div.livestrong-max-width--large > div.livestrong-header__wrapper > div.livestrong-header__menu
div.tab-group > div.tab-group__nav-container > sl-icon-button.tab-group__scroll-button div.tab-group > div.tab-group__nav-container > sl-icon-button.tab-group__scroll-button

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Close search div#livestrong-push-down__modal_18079 > div.livestrong-padding > div.livestrong-max-width--large > button.livestrong-close-button

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ask div.floating-bar
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
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
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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
Uses ARIA roles only on compatible elements
`[accesskey]` values are unique
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 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
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.
`[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.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting

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.

Description
ReferenceError: amzn is not defined at <anonymous>:1:1 at https://www.googletagmanager.com/gtm.js?id=GTM-TSR34SPC:948:429 at uR (https://www.googletagmanager.com/gtm.js?id=GTM-TSR34SPC:950:31) at Md.tR (https://www.googletagmanager.com/gtm.js?id=GTM-TSR34SPC:947:92) at Md.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-TSR34SPC:337:187) at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-TSR34SPC:263:466) at fb (https://www.googletagmanager.com/gtm.js?id=GTM-TSR34SPC:226:719) at eb (https://www.googletagmanager.com/gtm.js?id=GTM-TSR34SPC:226:470) at Md.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-TSR34SPC:287:473) at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-TSR34SPC:263:466)

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
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
92

SEO

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

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback