Skip to content
Audit Complete

Results for https://www.theverge.com

Visit site
Spain Spain · Madrid Completed: Apr 7, 2026 20:17 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C75

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

Cookie '_vm_consent_type' is missing the Secure flag

Security › Cookie Security
2

Page weighs 13.5 MB (5.2 MB transferred)

Performance › Page Weight Budget
3

1 control(s) without accessible label

Accessibility › Form Accessibility
4

10 button(s) with no accessible text

Accessibility › Link & Button Quality
5

No H1 heading found

Accessibility › Heading Hierarchy
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.theverge.com)](https://beavercheck.com/results/3f773972-7428-8d4b-13a3-09f1812177c1)
<a href="https://beavercheck.com/results/3f773972-7428-8d4b-13a3-09f1812177c1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.theverge.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.theverge.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

26
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
87
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

6.65 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

22.40 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

4.36 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.002

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

10.99 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

36.54 s

Detailed Report

Audit breakdown by category with detailed findings.

26

Performance

Insights

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

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

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

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.

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.

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:0.204 source:map[column:75308 line:193 type:source-location url:https://www.theverge.com/_next/static/chunks/pages/_app-e6a244fd60f98f13.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:212.588 source:map[type:text value:[unattributed]]] map[reflowTime:2.436 source:map[column:57524 line:7 type:source-location url:https://btloader.com/tag?o=6315858775244800&upapi=true urlProvider:network]] map[reflowTime:1.82 source:map[column:143784 line:1 type:source-location url:https://cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js urlProvider:network]] map[reflowTime:3.47 source:map[column:322676 line:1 type:source-location url:https://cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js urlProvider:network]] map[reflowTime:0.204 source:map[column:97 line:286 type:source-location url:https://d15kdpgjg3unno.cloudfront.net/oPS.js?cid=113 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

URLResource SizeEst Savings
Can AI responses be influenced? The SEO industry is trying div._1qlu5k4 > div._1ufh7nr8 > div > img.x271pn0
/wp-content/uploads/sites/2/2026/03/268407_Can_AI_respons...995.8 KiB994.9 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.

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.

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.

Estimated savings: 150 ms 17.7 KiB
URLTransfer SizeEst Savings
www.theverge.com/_next/static/css/641dbe35b05a14b5.css31.6 KiB17.7 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.

URLTotal CPU TimeScript EvaluationScript Parse
d15kdpgjg3unno.cloudfront.net/oPS.js?cid=11316.1 s16.0 s17 ms
www.theverge.com/_next/static/chunks/pages/_app-e6a244fd60f98f13.js4.0 s3.2 s273 ms
www.theverge.com/_next/static/chunks/framework-8e0f3cf51af7b1e2.js2.8 s2.5 s19 ms
Unattributable2.4 s183 ms0.0 ms
www.theverge.com/2.1 s25 ms1.3 ms
/pagead/managed/js/gpt/m202604060101/pubads_impl.js?cb=31...1.8 s1.7 s49 ms
cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.js1.4 s1.0 s48 ms
www.theverge.com/metrics/gtm.js?id=GTM-WQ5FM5W421 ms344 ms72 ms
/assets/smart-tag/versioned/main-v2_e645891259bb60090bde4...314 ms217 ms85 ms
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js253 ms148 ms94 ms
www.theverge.com/metrics/gtd?id=AW-926030959&cx=c&gtm=4e6460234 ms197 ms34 ms
btloader.com/tag?o=6315858775244800&upapi=true223 ms190 ms8.8 ms
client.aps.amazon-adsystem.com/publisher.js221 ms181 ms36 ms
/state/js?website_id=6384&device_id=6211442399393596874&v...209 ms195 ms0.2 ms
cdn.bullwhip.cloud/sonar/vox-verge.umd.js209 ms146 ms62 ms
pub.doubleverify.com/dvtag/21236410/DV464041/pub.js177 ms99 ms8.9 ms
/assets/smart-tag/versioned/ads-v2_c07e09f77264cce5ba5038...171 ms146 ms21 ms
www.theverge.com/_next/static/chunks/main-2d72d2950d961b0b.js161 ms143 ms16 ms
worldrealize.com/chunks/l2aod777_3ir2.v2.js127 ms82 ms12 ms
www.theverge.com/_next/static/chunks/pages/resource/homepage-be5d3bb96465e846.js101 ms94 ms6.3 ms
www.googletagservices.com/tag/js/gpt.js94 ms81 ms13 ms
/assets/smart-tag/versioned/cjs_min_92abedfd1b9757a428bfc...84 ms65 ms9.0 ms
assets.bounceexchange.com/assets/bounce/jquery-3.7.1.min.js58 ms40 ms16 ms
config.aps.amazon-adsystem.com/configs/317658 ms47 ms9.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

CategoryTime Spent
Script Evaluation27.8 s
Other3.2 s
Style & Layout1.5 s
Script Parsing & Compilation993 ms
Garbage Collection520 ms
Rendering462 ms
Parse HTML & CSS167 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

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
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

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Sponsor Logo div._8tvx5mc > div._8tvx5m6 > div._8tvx5mh > img._8tvx5mg

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
LCP request discovery
Modern HTTP
Network dependency tree
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 15 user timings
Avoid long main-thread tasks 20 long tasks found
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 110 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 1 layout shift found
INP breakdown
Avoid non-composited animations
87

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
The case for banning cookie banners div > div > div._1xwtict9 > a._1lkmsmo0
DAVID PIERCE span > span._1lldluw3 > span > span
Cisco CEO Chuck Robbins wants data centers in space div > div > div._1xwtict9 > a._1lkmsmo0
NILAY PATEL span > span._1lldluw3 > span > span
How the Amazon Echo learned to talk — and listen div > div > div._1xwtict9 > a._1lkmsmo0
DAVID PIERCE span > span._1lldluw3 > span > span
Apple’s best product ever div > div > div._1xwtict9 > a._1lkmsmo0
DAVID PIERCE span > span._1lldluw3 > span > span
Verge subscribers: Join us for a movie night in New York City, hosted by The Ve… div > div > div._1xwtict9 > a._1lkmsmo0
DAVID PIERCE span > span._1lldluw3 > span > span

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Failing Elements
now $899.99 console div._1t4tcr91 > div.wn1wvof > p.duet--article--dangerously-set-cms-markup > a
began blocking AI crawlers div._1t4tcr91 > div.wn1wvof > p.duet--article--dangerously-set-cms-markup > a

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
Art from Wit Studio’s <em>The One Piece.</em> section.duet--article--gallery > div#:R5af75ikqr96: > div._1etxtj13 > a._1etxtj12
<em>Instead of adding a screen, the Polaroid Hi-Print 3x3 has an integrated fra… section.duet--article--gallery > div#:R5aen5mkqr96: > div._1etxtj13 > a._1etxtj12
Render showing Isai Blue Google Pixel 10A from the front section.duet--article--gallery > div#:R5afn5mkqr96: > div._1etxtj13 > a._1etxtj12
Render showing Isai Blue Google Pixel 10A from the back section.duet--article--gallery > div#:R5afn5mkqr96: > div._1etxtj13 > a._1etxtj12
Bento box graphic showing Isai Blue Google Pixel 10A with exclusive software de… section.duet--article--gallery > div#:R5afn5mkqr96: > div._1etxtj13 > a._1etxtj12

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.

Failing Elements
Cookie Settings div._1twvhsd0 > ul._1twvhsd1 > li._1twvhsd2 > button#ot-sdk-btn
Cookie Policy div._1twvhsd0 > ul._1twvhsd1 > li._1twvhsd2 > a._1twvhsd3
Platform Status div._1twvhsd0 > ul._1twvhsd1 > li._1twvhsd2 > a._1twvhsd3

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
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
ARIA IDs are unique
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
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
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.
77

Best Practices

General

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

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

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

SourceDescription
Access to XMLHttpRequest at 'https://c.amazon-adsystem.com/cdn/prod/config?src=3176&u=https%3A%2F%2Fwww.theverge.com' from origin 'https://www.theverge.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 401 ()
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
100

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.

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
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

60
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
83
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

775 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.16 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

592 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.001

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.37 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

7.87 s

Detailed Report

Audit breakdown by category with detailed findings.

60

Performance

Insights

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

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

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

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.

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.

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:10.083 source:map[column:75308 line:193 type:source-location url:https://www.theverge.com/_next/static/chunks/pages/_app-e6a244fd60f98f13.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:278.072 source:map[type:text value:[unattributed]]] map[reflowTime:1.236 source:map[column:63211 line:1 type:source-location url:https://assets.bounceexchange.com/assets/smart-tag/versioned/main-v2_e645891259bb60090bde423588e192e6.br.js urlProvider:network]] map[reflowTime:1.658 source:map[column:376 line:864 type:source-location url:https://www.theverge.com/metrics/gtm.js?id=GTM-WQ5FM5W urlProvider:network]] map[reflowTime:0.691 source:map[column:57524 line:7 type:source-location url:https://btloader.com/tag?o=6315858775244800&upapi=true urlProvider:network]] map[reflowTime:7.043 source:map[column:134 line:286 type:source-location url:https://d15kdpgjg3unno.cloudfront.net/oPS.js?cid=113 urlProvider:network]] map[reflowTime:0.146 source:map[column:235686 line:1 type:source-location url:https://cdn.concert.io/lib/concert-ads/v2-latest/concert_ads.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

URLResource SizeEst Savings
Can AI responses be influenced? The SEO industry is trying div._1qlu5k3 > div._1ufh7nr7 > div > img.x271pn0
/wp-content/uploads/sites/2/2026/03/268407_Can_AI_respons...333.9 KiB333.1 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.

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.

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.

Estimated savings: 40 ms 17.0 KiB
URLTransfer SizeEst Savings
www.theverge.com/_next/static/css/641dbe35b05a14b5.css31.6 KiB17.0 KiB

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

CategoryTime Spent
Script Evaluation9.4 s
Other796 ms
Style & Layout437 ms
Script Parsing & Compilation286 ms
Garbage Collection156 ms
Rendering154 ms
Parse HTML & CSS40 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

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
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

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Sponsor Logo div._8tvx5mc > div._8tvx5m6 > div._8tvx5mh > img._8tvx5mg

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
LCP request discovery
Modern HTTP
Network dependency tree
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 16 user timings
Avoid long main-thread tasks 17 long tasks found
Network Requests
Network Round Trip Times 110 ms
Server Backend Latencies 130 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 2 layout shifts found
INP breakdown
Avoid non-composited animations
83

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
DAVID PIERCE span > span._1lldluw3 > span > span
NILAY PATEL span > span._1lldluw3 > span > span
DAVID PIERCE span > span._1lldluw3 > span > span
DAVID PIERCE span > span._1lldluw3 > span > span
DAVID PIERCE span > span._1lldluw3 > span > span

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Failing Elements
now $899.99 console div._1t4tcr91 > div.wn1wvof > p.duet--article--dangerously-set-cms-markup > a
began blocking AI crawlers div._1t4tcr91 > div.wn1wvof > p.duet--article--dangerously-set-cms-markup > a

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
Art from Wit Studio’s <em>The One Piece.</em> section.duet--article--gallery > div#:R5af75ikqr96: > div._1etxtj13 > a._1etxtj12
<em>Instead of adding a screen, the Polaroid Hi-Print 3x3 has an integrated fra… section.duet--article--gallery > div#:R5aen5mkqr96: > div._1etxtj13 > a._1etxtj12
Render showing Isai Blue Google Pixel 10A from the front section.duet--article--gallery > div#:R5afn5mkqr96: > div._1etxtj13 > a._1etxtj12
Render showing Isai Blue Google Pixel 10A from the back section.duet--article--gallery > div#:R5afn5mkqr96: > div._1etxtj13 > a._1etxtj12
Bento box graphic showing Isai Blue Google Pixel 10A with exclusive software de… section.duet--article--gallery > div#:R5afn5mkqr96: > div._1etxtj13 > a._1etxtj12

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.

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.

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.

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
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
ARIA IDs are unique
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
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
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.
77

Best Practices

General

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

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

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

SourceDescription
Access to XMLHttpRequest at 'https://c.amazon-adsystem.com/cdn/prod/config?src=3176&u=https%3A%2F%2Fwww.theverge.com' from origin 'https://www.theverge.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 401 ()
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
100

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.

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