Skip to content
https://lifewire.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.

29

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.

RequestCache TTLTransfer Size
openads-cdn.adsrvr.org/openadsjs/build/v1.0/dotdash/openads-20260304T232958Z.js0.0 ms97.3 KiB
c.amazon-adsystem.com/aax2/apstag.js3600.0 s91.0 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s73.1 KiB
ak.sail-horizon.com/spm/spm.v1.min.js600.0 s48.1 KiB
btloader.com/tag?o=5657833865478144&upapi=true300.0 s32.0 KiB
cdn.id5-sync.com/api/1.0/id5-api.js3600.0 s34.2 KiB
s0.2mdn.net/879366/html_inpage_rendering_lib_200_287.js86400.0 s59.8 KiB
cdn.id5-sync.com/api/1.0/id5PrebidModule.js3600.0 s29.5 KiB
g.3gl.net/jp/552/latest/InitialLoadScript.js1579.0 s23.1 KiB
secure.cdn.fastclick.net/js/pubcid/latest/pubcid.min.js900.0 s21.7 KiB
b-code.liadm.com/a-07sm.min.js86400.0 s45.3 KiB
s0.2mdn.net/879366/Enabler_01_262.js86400.0 s41.2 KiB
/scripts/bundle/65568.js?sid=c207879e-a95a-4330-93ec-4f19...3600.0 s20.6 KiB
g.3gl.net/jp/552/v4.0.13/LastMileScript.js1880.0 s18.0 KiB
ep2.adtrafficquality.google/sodar/VFc2VJAc.js3000.0 s14.0 KiB
connectid.analytics.yahoo.com/connectId.js3600.0 s8.9 KiB
static.hotjar.com/c/hotjar-2777028.js?sv=660.0 s6.2 KiB
dotdash-meredith.solutions.cdn.optable.co/public-assets/ddm-sdk.js86400.0 s15.4 KiB
static.criteo.net/js/ld/publishertag.ids.js86400.0 s14.8 KiB
tags.crwdcntrl.net/lt/c/16576/sync.min.js86400.0 s13.1 KiB
sb.scorecardresearch.com/internal-cs/default/beacon-and.js86400.0 s7.9 KiB
config.aps.amazon-adsystem.com/configs/34463600.0 s3.7 KiB
cdn.brandmetrics.com/tag/c106e229-c4c9-4c07-8306-2ef6b9d6d9ea/Lifewire.js3600.0 s3.6 KiB
/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c124171768917...86400.0 s6.9 KiB
/08378bf6-c29a-482b-88a2-bf3e3bcf4974/launchpad-liveramp.js0.0 ms2.2 KiB
/w37htfhcq2/vendor/72fdd3bc-a7cd-401d-88aa-0e87a8d6083f/l...60.0 s2.1 KiB
/a4flkt7l2b/z9gd/72fdd3bc-a7cd-401d-88aa-0e87a8d6083f/www...0.0 ms1.3 KiB
tru.am/scripts/ta-pagesocial-sdk.js2419200.0 s10.9 KiB
pagead2.googlesyndication.com/pagead/js/r20260420/r20110914/abg_lite.js1209600.0 s10.5 KiB
id5-sync.com/c/957/0/8/1.gif?gdpr=0&gdpr_consent=&us_privacy=0.0 ms1.0 KiB
/pagead/js/r20260420/r20110914/client/qs_click_protection...1209600.0 s8.9 KiB
/w37htfhcq2/z9g/digibox.gif?c=1776807432621&h=www.lifewir...0.0 ms688 B
px.ads.linkedin.com/setuid?partner=appNexus0.0 ms542 B
sli.lifewire.com/baker?dtstmp=17768074293270.0 ms540 B
/pagead/js/r20260420/r20110914/elements/html/omrhp.js1209600.0 s4.7 KiB
/usersync/liveintent/?cb=%2F%2Fi.liadm.com%2Fs%2F35004%3F...0.0 ms405 B
/c.js?siteid=c207879e-a95a-4330-93ec-4f19afa5645a&toploc=...0.0 ms293 B
/track/cmb/generic?ttd_pid=ber823s&ttd_tpi=1&gdpr=&gdpr_c...0.0 ms254 B
match.adsrvr.org/track/cmb/generic?ttd_pid=liveintent&ttd_tpi=1&gdpr=00.0 ms253 B
/pagead/js/r20260420/r20110914/client/window_focus_fy2021.js1209600.0 s1.3 KiB

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.

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: Samsung Galaxy S26 Ultra smartphone with camera array and stylus exposed
path: 1,HTML,2,BODY,5,MAIN,2,SECTION,0,A,0,DIV,0,DIV,0,IMG
selector: a#hero-spotlights__content_1-0 > div.loc > div.img-placeholder > img.block-image
snippet: <img src="https://www.lifewire.com/thmb/uGFeem8OONkT9MDmoPLP83T7WMU=/420x280/filters…" width="420" height="280" alt="Samsung Galaxy S26 Ultra smartphone with camera array and stylus exposed" class=" block-image mntl-image block-img js-justified universal-image__image" data-expand="300">

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

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.

URLEst Savings
/sadbundle/4352893413389935958/fonts/googlesanstext-mediu...5.0 ms
/sadbundle/4352893413389935958/fonts/GoogleSans-latin-sub...5.0 ms

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
head.loc > link head.loc > link
/dynamic/2/11256269/s3-bridge-prd-doubleclick.hogarth.ai/...18.1 KiB17.7 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.

Estimated savings: 839 ms
URLTime Spent
lifewire.com/839 ms
www.lifewire.com/0.0 ms

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

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 18.9 KiB
URLTransfer SizeEst Savings
launchpad.privacymanager.io/latest/launchpad.bundle.js40.2 KiB12.7 KiB
/static/6.175.0/static/modules/js/AssertiveYield/scripts/...36.4 KiB6.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.2 s 718.6 KiB
URLTransfer SizeEst Savings
/pagead/managed/js/gpt/m202604160201/pubads_impl.js187.7 KiB87.5 KiB
www.googletagmanager.com/gtag/js?id=G-ZS4VE91JW9&cx=c&gtm=4e64h1165.2 KiB66.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-WT6XGWDH&gtm=4e64h1123.1 KiB62.4 KiB
www.googletagmanager.com/gtag/js?id=G-DK3GDWHWJH&cx=c&gtm=4e64h1150.8 KiB62.4 KiB
/w37htfhcq2/vendor/72fdd3bc-a7cd-401d-88aa-0e87a8d6083f/m...96.4 KiB61.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-5P3SZGS139.0 KiB58.0 KiB
openads-cdn.adsrvr.org/openadsjs/build/v1.0/dotdash/openads-20260304T232958Z.js96.9 KiB45.3 KiB
/static/6.175.0/static/cache/eNqllttu2zAMhl9ogdEAfYCszYYA...144.0 KiB43.5 KiB
/ats-modules/6b702f9f-3fb0-44ab-80ee-f731b15c78bc/ats.js74.7 KiB38.8 KiB
script.hotjar.com/modules.6a0f3932cb1341a35c18.js56.1 KiB37.6 KiB
c.amazon-adsystem.com/aax2/apstag.js90.5 KiB37.1 KiB
ak.sail-horizon.com/spm/spm.v1.min.js47.7 KiB33.3 KiB
b-code.liadm.com/a-07sm.min.js45.0 KiB32.2 KiB
cdn.id5-sync.com/api/1.0/id5-api.js34.1 KiB31.1 KiB
b-code.liadm.com/a-07sm.min.js45.0 KiB21.3 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.

URLTotal CPU TimeScript EvaluationScript Parse
Unattributable2.0 s474 ms0.0 ms
www.lifewire.com/1.7 s258 ms21 ms
/static/6.175.0/cache/eNp9UltuwyAQvFCRz9BWVb8iRa0vgGFtE2P...1.4 s1.1 s21 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js661 ms528 ms77 ms
/static/6.175.0/static/cache/eNqllttu2zAMhl9ogdEAfYCszYYA...642 ms540 ms65 ms
/static/6.175.0/static/modules/js/AssertiveYield/scripts/...509 ms462 ms17 ms
www.googletagmanager.com/gtm.js?id=GTM-5P3SZGS412 ms334 ms68 ms
www.googletagmanager.com/gtag/js?id=G-DK3GDWHWJH&cx=c&gtm=4e64h1367 ms272 ms56 ms
www.googletagmanager.com/gtag/js?id=G-ZS4VE91JW9&cx=c&gtm=4e64h1352 ms288 ms60 ms
g.3gl.net/jp/552/latest/InitialLoadScript.js274 ms216 ms12 ms
btloader.com/tag?o=5657833865478144&upapi=true267 ms242 ms12 ms
www.googletagmanager.com/gtm.js?id=GTM-WT6XGWDH&gtm=4e64h1238 ms180 ms53 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js236 ms197 ms31 ms
b-code.liadm.com/a-07sm.min.js234 ms130 ms97 ms
openads-cdn.adsrvr.org/openadsjs/build/v1.0/dotdash/openads-20260304T232958Z.js227 ms188 ms38 ms
c.amazon-adsystem.com/aax2/apstag.js220 ms160 ms44 ms
cdn.id5-sync.com/api/1.0/id5-api.js212 ms139 ms60 ms
cdn.id5-sync.com/api/1.0/id5PrebidModule.js196 ms155 ms36 ms
g.3gl.net/jp/552/v4.0.13/LastMileScript.js175 ms130 ms11 ms
/a4flkt7l2b/z9gd/72fdd3bc-a7cd-401d-88aa-0e87a8d6083f/www...135 ms125 ms2.8 ms
/scripts/bundle/65568.js?sid=c207879e-a95a-4330-93ec-4f19...131 ms116 ms9.6 ms
config.aps.amazon-adsystem.com/configs/3446125 ms113 ms10 ms
/ats-modules/6b702f9f-3fb0-44ab-80ee-f731b15c78bc/ats.js120 ms90 ms29 ms
/w37htfhcq2/vendor/72fdd3bc-a7cd-401d-88aa-0e87a8d6083f/m...117 ms57 ms43 ms
ak.sail-horizon.com/spm/spm.v1.min.js104 ms84 ms19 ms
launchpad.privacymanager.io/latest/launchpad.bundle.js97 ms56 ms32 ms
securepubads.g.doubleclick.net/tag/js/gpt.js96 ms80 ms15 ms
aim-tag.hcn.health/js/client.js?dl=aimDataLayer95 ms85 ms9.1 ms
secure.cdn.fastclick.net/js/pubcid/latest/pubcid.min.js83 ms57 ms26 ms
tags.crwdcntrl.net/lt/c/16576/sync.min.js82 ms66 ms5.9 ms
ep2.adtrafficquality.google/sodar/sodar2.js66 ms60 ms2.9 ms
static.criteo.net/js/ld/publishertag.ids.js63 ms57 ms5.0 ms
dotdash-meredith.solutions.cdn.optable.co/public-assets/ddm-sdk.js56 ms48 ms6.5 ms
/08378bf6-c29a-482b-88a2-bf3e3bcf4974/launchpad-liveramp.js55 ms52 ms1.2 ms
oa.openxcdn.net/esp.js54 ms49 ms3.1 ms
tru.am/scripts/ta-pagesocial-sdk.js51 ms32 ms19 ms
/static/6.175.0/cache/eNqlU-1ugzAMfKFFUZ9hf_cSLjHBm3EqO5S...51 ms29 ms4.7 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 Evaluation7.4 s
Other2.1 s
Style & Layout1.1 s
Script Parsing & Compilation1.0 s
Rendering160 ms
Garbage Collection155 ms
Parse HTML & CSS146 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 reasonFailure type
The page has an unload handler in the main frame.Actionable
The page has an unload handler in a sub frame.Actionable

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 11.1 KiB
URLTransfer SizeEst Savings
.is-hidden{display:none!important} …21.0 KiB11.1 KiB

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.

URLTransfer Size
/pagead/managed/js/gpt/m202604160201/pubads_impl.js187.7 KiB
www.googletagmanager.com/gtag/js?id=G-ZS4VE91JW9&cx=c&gtm=4e64h1165.3 KiB
www.googletagmanager.com/gtag/js?id=G-ZS4VE91JW9&l=dataLayer&cx=c165.3 KiB
www.googletagmanager.com/gtag/js?id=G-DK3GDWHWJH&cx=c&gtm=4e64h1150.8 KiB
/static/6.175.0/static/cache/eNqllttu2zAMhl9ogdEAfYCszYYA...144.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-5P3SZGS139.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-WT6XGWDH&gtm=4e64h1123.1 KiB
bpulse.perflib.com/ipulse/ad/cp.com/creative/100.jpg?rand=102771902101.0 KiB
www.lifewire.com/static/6.175.0/fonts/jost.woff2101.0 KiB
cpulse.perflib.com/ipulse/ad/cp.com/creative/100.jpg?rand=399547536101.0 KiB

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●User Timing marks and measures 18 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 230 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 110 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○Avoid non-composited animations
92

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_1-0 div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_1-0
div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_2-0 div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_2-0
div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_3-0 div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_3-0
div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_4-0 div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_4-0

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_1-0 div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_1-0
div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_2-0 div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_2-0
div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_3-0 div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_3-0
div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_4-0 div#eat-snackbar__slideshow_1-0 > div.loc > div#eat-snackbar__pagination-dots_1-0 > button#slide__pagination-button_4-0
Should You Upgrade Your Android? div#eat-section_1-0 > ul#experts-spotlight_1-0 > li#experts-spotlight__block_1-0 > a#experts-spotlight__latest_1-0

These items highlight common accessibility best practices.

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
Lifewire Tech for Humans div.mntl-footer__inner > div.mntl-footer__primary > div.mntl-footer__logo > a#mntl-logo_1-0
○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
●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.
●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
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[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
○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.
○Uses ARIA roles only on compatible elements
○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.
73

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
Samsung Galaxy S26 Ultra smartphone with camera array and stylus exposed a#hero-spotlights__content_1-0 > div.loc > div.img-placeholder > img.block-image
/thmb/uGFeem8OONkT9MDmoPLP83T7WMU=/420x280/filters:no_ups...412 x 275420 x 280618 x 413
Sharper Image S-600 Active Lumbar Heated Ergonomic Bonded Leather Swivel Execut… a#block_9-0 > div.loc > div.img-placeholder > img.block-image
/thmb/9v6ilLZ48NmZGKa5RCEIsXl4LZ4=/120x80/filters:no_upsc...116 x 77120 x 80174 x 116
expert icon div.eat-snackbar__slide-icon > div.loc > div.img-placeholder > img.eat-image
/thmb/NIvryaDLQKz_37ncl8Fvjo_v1LY=/40x40/filters:no_upsca...40 x 4040 x 4060 x 60
meter icon div.eat-snackbar__slide-icon > div.loc > div.img-placeholder > img.eat-image
/thmb/z9dDuZuTlgslYbjpfLZRqSD6t3s=/40x40/filters:no_upsca...40 x 4040 x 4060 x 60

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
Topics
/static/6.175.0/static/modules/js/AssertiveYield/scripts/... line 53, col 130538
Unload event listeners are deprecated and will be removed.
g.3gl.net/jp/552/latest/InitialLoadScript.js line 4, col 17376

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.

SourceDescription
api.sail-personalize.com/v1/personalize/simple?pageviews=1&isMobile=1
Failed to load resource: the server responded with a status of 401 ()
/static/6.175.0/static/modules/js/AssertiveYield/scripts/... line 53, col 108411
Personalize call failed. SyntaxError: Unexpected token 'C', "Credential"... is not valid JSON
●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
●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 DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
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.

Link destinationLink Text
www.lifewire.com/home-networking-4781492SEE MORE

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