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
cdn.ziffstatic.com/pg/cnet.prebid.js	2844.0 s	232.1 KiB
openads-cdn.adsrvr.org/openadsjs/build/v1.0/ziffdavis/openads.js	0.0 ms	98.3 KiB
client.aps.amazon-adsystem.com/publisher.js	3600.0 s	90.9 KiB
cdn.ziffstatic.com/pg/cnet.js	2757.0 s	86.3 KiB
cdn.static.zdbb.net/eu/js/z0WVjCBSEeGLoxIxOQVEwQ.min.js	86400.0 s	175.1 KiB
/J3UXFee1xclY-bfFlWh1mIZ_phU/gpt_and_prebid/config.js	1100.0 s	57.9 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	250.0 s	27.8 KiB
cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.js	599954.0 s	126.2 KiB
static.chartbeat.com/js/chartbeat.js	86400.0 s	15.9 KiB
static.trueanthem.com/scripts/ta.c34341.js	86400.0 s	10.7 KiB
config.aps.amazon-adsystem.com/configs/3158	3600.0 s	2.8 KiB
/vendor/474a4045-633c-42d5-8a01-35be527d3b9a/lightbox_inl...	0.0 ms	1.8 KiB
cdn.ziffstatic.com/jst/otTCF.202512.1.0.js	599954.0 s	17.7 KiB
/a4flkt7l2b/z9gd/45898/www.cnet.com/jsonp/z?cb=1776295399...	0.0 ms	1.2 KiB
www.cnet.com/images/logos/cnet_load.png	604800.0 s	8.5 KiB
cdn.ziffstatic.com/pg/cnet.css	2671.0 s	1001 B
static.trueanthem.com/scripts/ta.js	86400.0 s	1.3 KiB
/w37htfhcq2/z9g/digibox.gif?c=1776295399044&h=www.cnet.co...	0.0 ms	301 B
cdn.ziffstatic.com/ajs?zoneid=a	3600.0 s	298 B

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:26.174 source:map[column:23360 line:1 type:source-location url:https://www.cnet.com/a/neutron/708c8bde17c4.modern.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:11.21 source:map[column:85 line:160 type:source-location url:https://cdn.ziffstatic.com/pg/cnet.js urlProvider:network]] map[reflowTime:5.405 source:map[column:70745 line:0 type:source-location url:https://www.cnet.com/a/neutron/3d1897abd40d.modern.js urlProvider:network]] map[reflowTime:0.807 source:map[column:253703 line:0 type:source-location url:https://www.cnet.com/a/neutron/3d1897abd40d.modern.js urlProvider:network]] map[reflowTime:4.149 source:map[column:63225 line:0 type:source-location url:https://www.cnet.com/a/neutron/d52d1ea3a562.modern.js urlProvider:network]] map[reflowTime:7.731 source:map[column:6978 line:0 type:source-location url:https://www.cnet.com/a/neutron/a5012ebf0873.modern.js urlProvider:network]] map[reflowTime:0.076 source:map[column:1862 line:0 type:source-location url:https://www.cnet.com/a/neutron/708c8bde17c4.modern.js urlProvider:network]] map[reflowTime:1.112 source:map[column:156831 line:1 type:source-location url:https://www.cnet.com/a/neutron/47d696a75771.modern.js urlProvider:network]] map[reflowTime:26.174 source:map[column:61837 line:0 type:source-location url:https://www.cnet.com/a/neutron/d52d1ea3a562.modern.js 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-VIDEO

nodeLabel: div.c-storiesNeonHighlightsLead_media > div.c-cmsImage > div.c-cmsImage_video > video

path: 1,HTML,1,BODY,1,DIV,1,DIV,0,DIV,10,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,1,DIV,0,DIV,0,A,0,DIV,0,DIV,0,DIV,0,DIV,0,VIDEO

selector: div.c-storiesNeonHighlightsLead_media > div.c-cmsImage > div.c-cmsImage_video > video

snippet: <video src="https://www.cnet.com/a/img/resize/102c5db689c0443be53c7d05547f1392c3165004…" poster="https://www.cnet.com/a/img/resize/45dc3ed12ffab202ee43fee530a3c7516d9b6e72…" width="1280" height="720" autoplay="autoplay" loop="loop" muted="muted" playsinline="" disableremoteplayback="">

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

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.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
div.c-storiesNeonHighlightsLead_media > div.c-cmsImage > div.c-cmsImage_video > video `div.c-storiesNeonHighlightsLead_media > div.c-cmsImage > div.c-cmsImage_video > video`	/a/img/resize/45dc3ed12ffab202ee43fee530a3c7516d9b6e72/hu...	544.3 KiB	499.1 KiB
a.c-storiesNeonLatest_story > div.c-cmsImage > picture.c-cmsImage_image > img `a.c-storiesNeonLatest_story > div.c-cmsImage > picture.c-cmsImage_image > img`	/a/img/resize/54cbb5612b5d7145acf6bf22bd56c9648132f5e9/hu...	34.4 KiB	28.4 KiB

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
cdn.ziffstatic.com/pg/cnet.css	1001 B	206 ms

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

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: 201 ms

URL	Time Spent
cnet.com/	201 ms
www.cnet.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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused 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: 570 ms 1.2 MiB

URL	Transfer Size	Est Savings
cdn.ziffstatic.com/pg/cnet.prebid.js	231.9 KiB	188.2 KiB
www.cnet.com/a/neutron/47d696a75771.modern.js	376.7 KiB	178.7 KiB
/pagead/managed/js/gpt/m202604100101/pubads_impl.js	186.4 KiB	125.3 KiB
cdn.confiant-integrations.net/gptprebidnative/202603241056/wrap.js	141.5 KiB	85.5 KiB
cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.js	126.2 KiB	71.6 KiB
www.cnet.com/a/neutron/a922d2a89ddd.modern.js	223.5 KiB	71.4 KiB
cdn.ziffstatic.com/pg/cnet.js	86.1 KiB	68.4 KiB
/w37htfhcq2/vendor/474a4045-633c-42d5-8a01-35be527d3b9a/m...	116.3 KiB	67.8 KiB
openads-cdn.adsrvr.org/openadsjs/build/v1.0/ziffdavis/openads.js	98.0 KiB	67.4 KiB
www.cnet.com/a/neutron/3d1897abd40d.modern.js	83.4 KiB	62.8 KiB
www.googletagmanager.com/gtag/destination?id=G-R820W8QX02&cx=c&gtm=4e64e1	161.0 KiB	62.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-NHBTHTVT	115.5 KiB	61.8 KiB
client.aps.amazon-adsystem.com/publisher.js	90.5 KiB	50.0 KiB
cdn.static.zdbb.net/js/z0WVjCBSEeGLoxIxOQVEwQ.min.js	174.7 KiB	41.3 KiB
www.cnet.com/a/neutron/eb626a70ccf6.modern.js	90.1 KiB	40.3 KiB
fundingchoicesmessages.google.com/i/pub-8038936283815017?ers=1	68.5 KiB	34.1 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
www.cnet.com/a/neutron/eb626a70ccf6.modern.js	844 ms	770 ms	0.4 ms
Unattributable	480 ms	168 ms	0.0 ms
www.cnet.com/	451 ms	30 ms	94 ms
www.cnet.com/a/neutron/6518b13b9504.modern.js	136 ms	119 ms	1.2 ms
/pagead/managed/js/gpt/m202604100101/pubads_impl.js	125 ms	110 ms	13 ms
www.cnet.com/a/neutron/47d696a75771.modern.js	119 ms	85 ms	1.3 ms
www.googletagmanager.com/gtag/destination?id=G-R820W8QX02&cx=c&gtm=4e64e1	118 ms	106 ms	12 ms
www.cnet.com/a/neutron/da62f8586255.modern.js	117 ms	106 ms	0.9 ms
client.aps.amazon-adsystem.com/publisher.js	92 ms	83 ms	7.6 ms
cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.js	91 ms	69 ms	12 ms
cdn.confiant-integrations.net/gptprebidnative/202603241056/wrap.js	89 ms	79 ms	9.2 ms
cdn.ziffstatic.com/pg/cnet.js	76 ms	44 ms	13 ms
fundingchoicesmessages.google.com/i/pub-8038936283815017?ers=1	57 ms	52 ms	4.5 ms
cdn.ziffstatic.com/pg/cnet.prebid.js	57 ms	40 ms	17 ms
www.cnet.com/a/neutron/d77860478607.modern.js	56 ms	55 ms	0.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.

Category	Time Spent
Script Evaluation	2.2 s
Other	423 ms
Style & Layout	254 ms
Script Parsing & Compilation	238 ms
Garbage Collection	101 ms
Parse HTML & CSS	89 ms
Rendering	37 ms

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
/a/img/resize/102c5db689c0443be53c7d05547f1392c3165004/hu...	1.9 MiB
/a/img/resize/45dc3ed12ffab202ee43fee530a3c7516d9b6e72/hu...	544.9 KiB
www.cnet.com/	428.9 KiB
www.cnet.com/a/neutron/47d696a75771.modern.js	381.0 KiB
www.cnet.com/a/neutron/fonts/Stardust/Variable.woff2	377.3 KiB
/a/img/resize/16bfc489dc0310fe6f83850831773fcb861e8dad/hu...	373.0 KiB
cdn.ziffstatic.com/pg/cnet.prebid.js	232.1 KiB
www.cnet.com/a/neutron/a922d2a89ddd.modern.js	223.7 KiB
/pagead/managed/js/gpt/m202604100101/pubads_impl.js	186.4 KiB
cdn.static.zdbb.net/eu/js/z0WVjCBSEeGLoxIxOQVEwQ.min.js	175.1 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 25 user timings

●Avoid long main-thread tasks 11 long tasks found

●Avoid non-composited animations 6 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

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

100

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.

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
Manage Preferences `div.md:flex > div.md:max-w-80 > div.mb-6 > a.primary-link`
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

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●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

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

Best Practices

User Experience

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img `a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img`	/a/img/resize/17ee1d5d5a927ae58e249f8a3006b8432c522898/hu...	320 x 180 (1.78)	416 x 228 (1.82)
a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img `a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img`	/a/img/resize/d603adf83b70668622b260f84fdf39c3f8d01ad5/hu...	320 x 180 (1.78)	416 x 228 (1.82)
a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img `a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img`	/a/img/resize/e51db0653de2aa299724761236a77272e1cb31cb/hu...	320 x 180 (1.78)	416 x 228 (1.82)
a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img `a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img`	/a/img/resize/a69066034dedfd36987106969409fcfd355d4e53/hu...	320 x 180 (1.78)	416 x 228 (1.82)
a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img `a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img`	/a/img/resize/3d4ab56d8b55cfaa236550e0edff334b8876fe37/hu...	320 x 180 (1.78)	416 x 228 (1.82)
a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img `a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img`	/a/img/resize/71e03f703ab3adcb58b666d833c16d83b0d838d4/hu...	320 x 180 (1.78)	416 x 228 (1.82)
a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img `a.c-storiesNeonHighlightsCard_link > div.c-cmsImage > picture.c-cmsImage_image > img`	/a/img/resize/a69066034dedfd36987106969409fcfd355d4e53/hu...	320 x 180 (1.78)	416 x 228 (1.82)

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.cnet.com/a/neutron/a922d2a89ddd.modern.js
www.cnet.com/a/neutron/47d696a75771.modern.js
www.cnet.com/

●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

●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

○Use a strong HSTS policy

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Learn more `div.c-storiesExpertise > div.c-storiesExpertise_headContainer > div.c-storiesExpertise_ctaContainer > a.c-storiesExpertise_cta`

To appear in search results, crawlers need access to your app.

○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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`