Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
lifehacker.com/fonts/InterVariable-Italic.ttf	1800.0 s	874.1 KiB
lifehacker.com/images/newsletter-background.png	1800.0 s	860.0 KiB
lifehacker.com/fonts/InterVariable.ttf	1800.0 s	843.3 KiB
lifehacker.com/images/icons/spritemap.svg?id=7f67b9a9e21a44fd068b4682ff70f449	1800.0 s	309.2 KiB
cdn.ziffstatic.com/pg/lifehacker.prebid.js	2107.0 s	232.4 KiB
lifehacker.com/fonts/Akshar-VariableFont_wght.ttf	1800.0 s	199.9 KiB
openads-cdn.adsrvr.org/openadsjs/build/v1.0/ziffdavis/openads.js	0.0 ms	98.4 KiB
client.aps.amazon-adsystem.com/publisher.js	3600.0 s	91.0 KiB
cdn.ziffstatic.com/pg/lifehacker.js	2556.0 s	84.2 KiB
cdn.static.zdbb.net/eu/js/z0WVjCBSEeGLoxIxOQVEwQ.min.js	86400.0 s	175.8 KiB
lifehacker.com/js/app.js?id=5b3509872efe334ff7a4884a752c7332	1800.0 s	71.7 KiB
lifehacker.com/fonts/LeagueGothic-Regular-VariableFont_wdth.ttf	1800.0 s	62.8 KiB
client.openweb.bid/federated/index.bundle.js	0.0 ms	48.8 KiB
client.openweb.bid/federated/v2.62.0/77e7874d0c04f7940d1a.bundle.js	0.0 ms	28.4 KiB
cdn.id5-sync.com/api/1.0/id5-api.js	3600.0 s	34.5 KiB
pub.doubleverify.com/dvtag/33936767/DV1379166/pub.js	900.0 s	30.8 KiB
cdn.ziffstatic.com/jst/zdconsent_eu.js	416.0 s	27.8 KiB
launcher.spot.im/spot/sp_Z3zhn8qO	300.0 s	19.5 KiB
client.openweb.bid/federated/libs/dfd79f527ba6d5147e19.bundle.js	0.0 ms	17.0 KiB
client.openweb.bid/federated/v2.62.0/e4d98b2864095e91c18b.bundle.js	0.0 ms	12.0 KiB
cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.js	2557460.0 s	126.2 KiB
ml314.com/tag.aspx?213	3600.0 s	12.7 KiB
static.chartbeat.com/js/chartbeat_video.js	86400.0 s	24.8 KiB
assets.bounceexchange.com/cache/6171/website-0929e538179b789b01f09b030c31f569.js	120.0 s	9.0 KiB
/federated/libs/prebid/modules/userId/userId.ca4a55ca9628...	0.0 ms	5.9 KiB
lifehacker.com/iterable/push-consent.js	1800.0 s	5.5 KiB
tag.wknd.ai/6171/i.js	60.0 s	3.8 KiB
sb.scorecardresearch.com/internal-cs/default/beacon.js	86400.0 s	6.7 KiB
lifehacker.com/iterable/push-notify.js	1800.0 s	2.8 KiB
config.aps.amazon-adsystem.com/configs/3158	3600.0 s	2.9 KiB
/vendor/d0e1d3d8-b896-4fe6-911a-2d9fc7c5cc2a/lightbox_spe...	60.0 s	2.1 KiB
/federated/libs/prebid/modules/pubProvidedId.05e7d23f396e...	0.0 ms	1.8 KiB
/federated/libs/prebid/modules/unifiedId.beee421287ae8389...	0.0 ms	1.7 KiB
cdn.ziffstatic.com/jst/otTCF.202512.1.0.js	2557460.0 s	17.7 KiB
lifehacker.com/images/lifehacker-logo.svg	1800.0 s	1.9 KiB
cdn.ziffstatic.com/pg/lifehacker.css	3340.0 s	1.9 KiB
lifehacker.com/js/app/table-of-contents.js	1800.0 s	1.5 KiB
lifehacker.com/js/app/live-blog-updates.js	1800.0 s	1.4 KiB
/a4flkt7l2b/z9gd/d0e1d3d8-b896-4fe6-911a-2d9fc7c5cc2a/lif...	0.0 ms	1.2 KiB
tru.am/scripts/ta-pagesocial-sdk.js	2419200.0 s	10.9 KiB
/w37htfhcq2/z9g/digibox.gif?c=1776800292147&h=lifehacker....	0.0 ms	850 B
client.openweb.bid/federated/v2.62.0/e2518f6682edc2ab14a6.bundle.js	0.0 ms	569 B
g.lifehacker.com/lifehacker.js?url=https%3A%2F%2Flifehacker.com	680.0 s	353 B
lifehacker.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js	172800.0 s	836 B
cdn.ziffstatic.com/ajs?zoneid=a	3600.0 s	298 B
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 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.

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:55.511 source:map[column:215 line:143 type:source-location url:https://cdn.ziffstatic.com/pg/lifehacker.js urlProvider:network]]]

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

items: [map[reflowTime:17.557 source:map[column:18 line:2 type:source-location url:https://lifehacker.com/js/app/table-of-contents.js urlProvider:network]] map[reflowTime:66.943 source:map[type:text value:[unattributed]]] map[reflowTime:55.511 source:map[column:438 line:137 type:source-location url:https://cdn.ziffstatic.com/pg/lifehacker.js urlProvider:network]] map[reflowTime:0.251 source:map[column:17157 line:0 type:source-location url:https://static-cdn.spot.im/production/social/tags/v5.26.0/launcher/entry-bundle.js urlProvider:network]] map[reflowTime:13.45 source:map[column:295860 line:6 type:source-location url:https://cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.js urlProvider:network]] map[reflowTime:0.902 source:map[column:296204 line:6 type:source-location url:https://cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.js urlProvider:network]] map[reflowTime:0.607 source:map[column:349463 line:6 type:source-location url:https://cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.js urlProvider:network]] map[reflowTime:0.473 source:map[column:119 line:90 type:source-location url:https://cdn.ziffstatic.com/jst/zdconsent.js urlProvider:network]] map[reflowTime:0.869 source:map[column:332 line:412 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]] map[reflowTime:0.359 source:map[column:168540 line:6 type:source-location url:https://cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
1:26 `div.mt-12 > div.md:grid-cols-2 > div > a.relative`	lifehacker.com/imagery/videos/01HF2HPAGFGY6Y6FT2C3PA10GS/hero-image.png	1.5 MiB	1.2 MiB
Examples of my strength, cardio, and active recovery days. `div.mt-8 > div.w-full > a.peer > img.w-full`	/imagery/articles/01KPBN8CFXZA7TN8Y4KRP0Y6PW/hero-image.f...	458.7 KiB	392.8 KiB
Ready to do everything better? Get daily tips, tricks, and tech guides delivere… `section.flex > section.w-full > section.relative > div.custom-background-image`	lifehacker.com/images/newsletter-background.png	859.4 KiB	296.9 KiB
A hand holding the X3 e-reader (displaying the cover of the book Lonesome Dove)… `div.mt-8 > div.col-span-2 > a.peer > img.w-full`	/imagery/articles/01KPBHCN78NW4WXQK73T0P35YX/hero-image.f...	124.2 KiB	103.3 KiB
Google Pixel phone lying screen down `div.mt-8 > div.col-span-2 > a.peer > img.w-full`	/imagery/articles/01KPE24WGR7W2T8989VPE3RPZH/hero-image.f...	122.6 KiB	101.7 KiB
div.md:grid-cols-2 > div > a.relative > img.aspect-video `div.md:grid-cols-2 > div > a.relative > img.aspect-video`	/transformations/production/ee650fbb-f5f1-48dd-95a2-bb88f...	25.3 KiB	18.9 KiB
7X7=49, Olaf, Sea Lion `div.mt-8 > div.col-span-2 > a.peer > img.w-full`	/imagery/articles/01KNMN5KWA0SDRXCF79G72YTQV/hero-image.f...	30.9 KiB	15.0 KiB
div.md:grid-cols-2 > div > a.relative > img.aspect-video `div.md:grid-cols-2 > div > a.relative > img.aspect-video`	/transformations/production/fce21d65-d01f-41da-a950-d7920...	16.6 KiB	12.4 KiB
Samsung HW-Q800F Soundbar `div.mt-4 > div.group > a.group-hover:custom-underline > img.w-full`	/imagery/articles/01KPR24HCN9WFDFXXMEE6NB43Q/hero-image.f...	8.2 KiB	7.3 KiB
Google Pixel 10 Pro XL `div.mt-4 > div.group > a.group-hover:custom-underline > img.w-full`	/imagery/articles/01KPR6KNYT7T02FEH7T3H4PSX1/hero-image.f...	6.8 KiB	6.0 KiB
Animal or AI, You the Birthday, AI trampoline `div.mt-8 > div.w-full > a.peer > img.w-full`	/imagery/articles/01KNWW11JSSASPPKYVX0VFY03H/hero-image.f...	64.4 KiB	4.8 KiB

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-1-IMG

nodeLabel: Examples of my strength, cardio, and active recovery days.

path: 1,HTML,1,BODY,6,DIV,1,MAIN,0,SECTION,0,SECTION,0,SECTION,0,DIV,0,DIV,1,DIV,0,DIV,0,A,0,IMG

selector: div.mt-8 > div.w-full > a.peer > img.w-full

snippet: <img class="w-full rounded-md border border-gray-100" src="https://lifehacker.com/imagery/articles/01KPBN8CFXZA7TN8Y4KRP0Y6PW/hero-im…" alt="Examples of my strength, cardio, and active recovery days." width="900" height="450">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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.

URL	Transfer Size	Duration
lifehacker.com/js/app/live-blog-updates.js	1.4 KiB	178 ms
lifehacker.com/js/app/table-of-contents.js	1.5 KiB	178 ms
www.googletagmanager.com/gtag/js?id=G-7E851STSQZ	161.1 KiB	660 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	10 ms

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

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 140 ms 1.3 MiB

URL	Transfer Size	Est Savings
cdn.ziffstatic.com/pg/lifehacker.prebid.js	232.2 KiB	188.3 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	176.8 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB	126.3 KiB
/assets/smart-tag/versioned/main-v2_567848e754a175dbe6219...	116.2 KiB	88.2 KiB
cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.js	126.2 KiB	71.7 KiB
/w37htfhcq2/vendor/d0e1d3d8-b896-4fe6-911a-2d9fc7c5cc2a/m...	116.3 KiB	71.3 KiB
openads-cdn.adsrvr.org/openadsjs/build/v1.0/ziffdavis/openads.js	98.0 KiB	67.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-WRN84GTL	122.1 KiB	62.2 KiB
www.googletagmanager.com/gtag/js?id=G-7E851STSQZ	160.8 KiB	60.5 KiB
static-cdn.spot.im/production/social/tags/v5.26.0/launcher/691-bundle.js	100.9 KiB	54.2 KiB
lifehacker.com/js/app.js?id=5b3509872efe334ff7a4884a752c7332	71.4 KiB	52.2 KiB
static-cdn.spot.im/production/ads/tags/v22.32.1/ads/ads.js	71.7 KiB	42.7 KiB
cdn.static.zdbb.net/js/z0WVjCBSEeGLoxIxOQVEwQ.min.js	175.4 KiB	42.7 KiB
cdn.ziffstatic.com/pg/lifehacker.js	52.0 KiB	42.0 KiB
static-cdn.spot.im/production/social/tags/v5.26.0/launcher/296-bundle.js	54.2 KiB	37.2 KiB
/assets/smart-tag/versioned/ads-v2_b6cef0b913934dd3669178...	41.7 KiB	33.6 KiB
client.openweb.bid/federated/v2.62.0/77e7874d0c04f7940d1a.bundle.js	28.4 KiB	23.0 KiB
assets.bounceexchange.com/assets/bounce/jquery-3.7.1.min.js	30.3 KiB	23.0 KiB
client.openweb.bid/federated/index.bundle.js	48.5 KiB	22.0 KiB
static-cdn.spot.im/production/social/tags/v5.26.0/launcher/467-bundle.js	30.0 KiB	21.8 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	784 ms	131 ms	0.0 ms
lifehacker.com/	466 ms	47 ms	3.9 ms
static-cdn.spot.im/production/social/tags/v5.26.0/launcher/691-bundle.js	422 ms	376 ms	21 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	365 ms	319 ms	38 ms
cdn.ziffstatic.com/jst/otTCF.202512.1.0.js	351 ms	315 ms	5.4 ms
static-cdn.spot.im/production/social/tags/v5.26.0/launcher/entry-bundle.js	199 ms	191 ms	2.6 ms
cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.js	183 ms	140 ms	22 ms
www.googletagmanager.com/gtag/js?id=G-7E851STSQZ	180 ms	143 ms	28 ms
static-cdn.spot.im/production/social/tags/v5.26.0/launcher/696-bundle.js	179 ms	47 ms	0.8 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	163 ms	133 ms	26 ms
client.aps.amazon-adsystem.com/publisher.js	148 ms	126 ms	16 ms
cdn.ziffstatic.com/pg/lifehacker.js	135 ms	45 ms	11 ms
/assets/smart-tag/versioned/ads-v2_b6cef0b913934dd3669178...	122 ms	61 ms	12 ms
lifehacker.com/js/app.js?id=5b3509872efe334ff7a4884a752c7332	119 ms	95 ms	8.8 ms
cdn.ziffstatic.com/pg/lifehacker.prebid.js	105 ms	60 ms	45 ms
/w37htfhcq2/vendor/d0e1d3d8-b896-4fe6-911a-2d9fc7c5cc2a/m...	81 ms	33 ms	19 ms
/assets/smart-tag/versioned/main-v2_567848e754a175dbe6219...	78 ms	54 ms	23 ms
cdn.ziffstatic.com/jst/zdconsent.js	72 ms	60 ms	6.7 ms
openads-cdn.adsrvr.org/openadsjs/build/v1.0/ziffdavis/openads.js	65 ms	51 ms	14 ms
www.googletagmanager.com/gtm.js?id=GTM-WRN84GTL	61 ms	46 ms	15 ms
/a4flkt7l2b/z9gd/d0e1d3d8-b896-4fe6-911a-2d9fc7c5cc2a/lif...	59 ms	58 ms	0.2 ms
pub.doubleverify.com/dvtag/33936767/DV1379166/pub.js	55 ms	47 ms	4.3 ms
static-cdn.spot.im/production/social/tags/v5.26.0/launcher/223-bundle.js	54 ms	50 ms	3.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.

Category	Time Spent
Script Evaluation	3.0 s
Other	838 ms
Style & Layout	438 ms
Script Parsing & Compilation	419 ms
Garbage Collection	123 ms
Rendering	92 ms
Parse HTML & CSS	62 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
The page has an unload handler in the main frame.	Actionable

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: 0.0 ms 16.2 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/firebasejs/12.7.0/firebase-app.js	22.7 KiB	13.5 KiB
lifehacker.com/iterable/push-consent.js	5.2 KiB	2.7 KiB

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

URL	Transfer Size	Est Savings
.spotim-light {--launcher--module-font-size-offset: calc(3 * var(--launcher--global-font-size-level…	52.8 KiB	52.8 KiB
:host {--launcher--module-font-size-offset: calc(3 * var(--launcher--global-font-size-level, 0));--…	50.8 KiB	48.3 KiB
@font-face{font-display:swap;font-family:inter;font-style:normal;font-weight:100 800; … } …	14.5 KiB	11.5 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.

URL	Transfer Size
lifehacker.com/imagery/videos/01HF2HPAGFGY6Y6FT2C3PA10GS/hero-image.png	1.5 MiB
lifehacker.com/fonts/InterVariable-Italic.ttf	874.1 KiB
lifehacker.com/images/newsletter-background.png	860.0 KiB
lifehacker.com/fonts/InterVariable.ttf	843.3 KiB
/imagery/articles/01KPBN8CFXZA7TN8Y4KRP0Y6PW/hero-image.f...	459.2 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.1 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.9 KiB
lifehacker.com/images/icons/spritemap.svg	309.5 KiB
lifehacker.com/images/icons/spritemap.svg?id=7f67b9a9e21a44fd068b4682ff70f449	309.2 KiB
cdn.ziffstatic.com/pg/lifehacker.prebid.js	232.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

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●User Timing marks and measures 25 user timings

●Avoid long main-thread tasks 18 long tasks found

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

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 160 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 20 ms

○INP breakdown

○Avoid non-composited animations

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

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.md:grid-cols-2 > div > a.relative > img.aspect-video `div.md:grid-cols-2 > div > a.relative > img.aspect-video`
div.md:grid-cols-2 > div > a.relative > img.aspect-video `div.md:grid-cols-2 > div > a.relative > img.aspect-video`

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-full > div.w-full > form#homepage_newsletter_form > input `div.w-full > div.w-full > form#homepage_newsletter_form > input`

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.

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
SEE MORE `div.mt-6 > div.mx-auto > div.flex > a.custom-gradient-text`
SEE MORE `section.relative > div.mt-12 > div.flex > a.custom-gradient-text`
SEE MORE `div.flex > div.flex-1 > div.flex > a.custom-gradient-text`
SEE MORE `div.flex > div.flex-1 > div.flex > a.custom-gradient-text`
SEE MORE `section.relative > div.mt-12 > div.flex > a.custom-gradient-text`
SEE MORE `section.relative > div.mt-12 > div.flex > a.custom-gradient-text`
SEE MORE `section.relative > div.mt-12 > div.flex > a.custom-gradient-text`
SEE MORE `section.relative > div.mt-12 > div.flex > a.custom-gradient-text`
About Ziff Davis (Opens in a new tab) `div.w-full > ul.grid > li.md:mr-4 > a.text-sm`
Our Privacy Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●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

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

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

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

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 / Warning	Source
Unload event listeners are deprecated and will be removed.	static-cdn.spot.im/production/social/tags/v5.26.0/launcher/296-bundle.js line 1, col 182835

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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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 destination	Link Text
lifehacker.com/latest	SEE MORE
lifehacker.com/series/out-of-touch-adults-guide-to-kid-culture	SEE MORE
lifehacker.com/our-mission	SEE MORE
lifehacker.com/our-team	SEE MORE
lifehacker.com/deals	SEE MORE
lifehacker.com/news	SEE MORE
lifehacker.com/hacks	SEE MORE
lifehacker.com/how-to	SEE MORE

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.md:grid-cols-2 > div > a.relative > img.aspect-video `div.md:grid-cols-2 > div > a.relative > img.aspect-video`
div.md:grid-cols-2 > div > a.relative > img.aspect-video `div.md:grid-cols-2 > div > a.relative > img.aspect-video`

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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`