Skip to content
https://www.theverge.com

Lighthouse Desktop

· 0 checks — Desktop 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.

80

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.

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.

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:1.889 source:map[column:272889 line:2 type:source-location url:https://cdn.doubleverify.com/dv-measurements9836.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:105.28 source:map[type:text value:[unattributed]]] map[reflowTime:13.659 source:map[column:58370 line:7 type:source-location url:https://btloader.com/tag?o=6315858775244800&upapi=true urlProvider:network]] map[reflowTime:1.004 source:map[column:259775 line:1 type:source-location url:https://cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js urlProvider:network]] map[reflowTime:0.338 source:map[column:235686 line:1 type:source-location url:https://cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js urlProvider:network]] map[reflowTime:1.081 source:map[column:237636 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604300101/pubads_impl.js urlProvider:network]] map[reflowTime:0.964 source:map[column:242243 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604300101/pubads_impl.js urlProvider:network]] map[reflowTime:0.702 source:map[column:143811 line:1 type:source-location url:https://cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js urlProvider:network]] map[reflowTime:0.344 source:map[column:103257 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604300101/pubads_impl.js urlProvider:network]] map[reflowTime:0.793 source:map[column:63213 line:1 type:source-location url:https://assets.bounceexchange.com/assets/smart-tag/versioned/main-v2_63e84cd7813c827315a199d35d5845ce.br.js urlProvider:network]] map[reflowTime:0.66 source:map[column:444 line:348 type:source-location url:https://www.gstatic.com/recaptcha/releases/U5VsmTDhJM1iOJUyw4DEUTYv/recaptcha__en.js urlProvider:network]] map[reflowTime:0.38 source:map[column:122666 line:1 type:source-location url:https://cdn.ampproject.org/rtv/012603032146000/amp4ads-v0.mjs urlProvider:network]] map[reflowTime:0.642 source:map[column:126177 line:1 type:source-location url:https://cdn.ampproject.org/rtv/012603032146000/amp4ads-v0.mjs urlProvider:network]] map[reflowTime:1.524 source:map[column:325083 line:1 type:source-location url:https://cdn.doubleverify.com/dv-measurements9836.js urlProvider:network]] map[reflowTime:0.262 source:map[column:6503 line:1 type:source-location url:https://cdn.ampproject.org/rtv/012603032146000/v0/amp-ad-exit-0.1.mjs urlProvider:network]] map[reflowTime:0.812 source:map[column:128662 line:1 type:source-location url:https://cdn.ampproject.org/rtv/012603032146000/amp4ads-v0.mjs urlProvider:network]] map[reflowTime:1.536 source:map[column:325226 line:1 type:source-location url:https://cdn.doubleverify.com/dv-measurements9836.js urlProvider:network]] map[reflowTime:1.24 source:map[column:267789 line:1 type:source-location url:https://cdn.doubleverify.com/dv-measurements9836.js urlProvider:network]]]

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.

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
div#banner > div.ns-r4baa-e-1 > a.ns-r4baa-e-2 > svg.ns-r4baa-e-3 div#banner > div.ns-r4baa-e-1 > a.ns-r4baa-e-2 > svg.ns-r4baa-e-3
/simgad/7569173843847414255/14763004658117789537?w=600&h=...55.0 KiB24.3 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

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: 40 ms 23.5 KiB
URLTransfer SizeEst Savings
www.theverge.com/_next/static/css/67c4bd3a29d2225c.css31.8 KiB23.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.

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 Evaluation2.6 s
Other638 ms
Style & Layout272 ms
Script Parsing & Compilation195 ms
Garbage Collection139 ms
Rendering114 ms
Parse HTML & CSS65 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
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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

●Max Potential First Input Delay 120 ms
●Layout shift culprits
●Document request latency
●Optimize DOM size
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Network dependency tree
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 32 user timings
●Avoid long main-thread tasks 8 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 60 ms
●Server Backend Latencies 180 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 0 ms
●Avoid large layout shifts 3 layout shifts found
○INP breakdown
○Avoid non-composited animations
93

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Tech Reviews Science Entertainment AI Policy div._1ckl8uw3 > div._1ckl8uw4 > nav._1ckl8uwc > ul._18l06ho1

These are opportunities to improve the experience of reading tabular or list data using 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
SIGN IN div._1ckl8uw4 > div._1wnt6o310 > div._6cuzo20 > a._6cuzo22

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[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
●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
●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 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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[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
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

General

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
Failed to load resource: the server responded with a status of 401 ()
●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No 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
○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.

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