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

63

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:85.955 source:map[type:text value:[unattributed]]]]

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
value: No additional origins are good candidates for preconnecting

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.

URLResource SizeEst Savings
America, Actually div.fp8pvk1 > div._1agz5xb8 > div > img.mvmjsc0
www.vox.com/static-assets/podcasts/america-actually.png1.0 MiB1.0 MiB
Explain It to Me div.fp8pvk1 > div._1agz5xb8 > div > img.mvmjsc0
www.vox.com/static-assets/podcasts/explain-it-to-me.png103.3 KiB102.4 KiB
Unexplainable div.fp8pvk1 > div._1agz5xb8 > div > img.mvmjsc0
www.vox.com/static-assets/podcasts/unexplainable2.jpeg89.6 KiB88.7 KiB
div#google_image_div > a#aw0 > amp-img.img_ad > img.i-amphtml-fill-content div#google_image_div > a#aw0 > amp-img.img_ad > img.i-amphtml-fill-content
tpc.googlesyndication.com/daca_images/simgad/1782369703661411386110.3 KiB82.7 KiB
What to do about burnout at work div.ox2lvn1 > div.duet--content-cards--content-card > div.hd0te97 > img.mvmjsc0
/wp-content/uploads/sites/2/2026/04/Burnout.png?quality=9...75.4 KiB70.4 KiB
My partner and I don’t share many interests. Should we break up? div.ox2lvn1 > div.duet--content-cards--content-card > div.hd0te97 > img.mvmjsc0
/wp-content/uploads/sites/2/2026/04/GettyImages-221927762...66.1 KiB62.2 KiB
The Gray Area div.fp8pvk1 > div._1agz5xb8 > div > img.mvmjsc0
www.vox.com/static-assets/podcasts/the-gray-area.png46.7 KiB45.8 KiB
8 ways to zone out and relax that don’t involve being on your phone div.ox2lvn1 > div.duet--content-cards--content-card > div.hd0te97 > img.mvmjsc0
/wp-content/uploads/sites/2/2026/04/GettyImages-223820685...39.2 KiB35.7 KiB
Is it wrong to send your kid to private school? div.ox2lvn1 > div.duet--content-cards--content-card > div.hd0te97 > img.mvmjsc0
/wp-content/uploads/sites/2/2026/03/Public-Schools.jpg?qu...38.3 KiB34.9 KiB
What trainers actually think about the 12-3-30 workout div.ox2lvn1 > div.duet--content-cards--content-card > div.hd0te97 > img.mvmjsc0
/wp-content/uploads/sites/2/2026/04/gettyimages-226092996...34.6 KiB31.6 KiB
How to make unemployment suck a little less div.ox2lvn1 > div.duet--content-cards--content-card > div.hd0te97 > img.mvmjsc0
/wp-content/uploads/sites/2/2026/04/GettyImages-142099938...22.3 KiB20.4 KiB
The case for AI realism div.ox2lvn1 > div.duet--content-cards--content-card > div.hd0te97 > img.mvmjsc0
/wp-content/uploads/sites/2/2026/04/gettyimages-226807157...19.8 KiB18.0 KiB
How Americans really feel about immigration div.ox2lvn1 > div.duet--content-cards--content-card > div.hd0te97 > img.mvmjsc0
/wp-content/uploads/sites/2/2026/04/gettyimages-218635846...20.9 KiB17.0 KiB
How to ask for help when you’re really going through it div.ox2lvn1 > div.duet--content-cards--content-card > div.hd0te97 > img.mvmjsc0
/wp-content/uploads/sites/2/2026/04/GettyImages-75489153....18.6 KiB16.9 KiB
The simple question that could change your career div.ox2lvn1 > div.duet--content-cards--content-card > div.hd0te97 > img.mvmjsc0
/wp-content/uploads/sites/2/2026/04/GettyImages-225125095...16.5 KiB15.0 KiB
Rubén Gallego on why he defended Eric Swalwell — and why he regrets it now div.ox2lvn1 > div.duet--content-cards--content-card > div.hd0te97 > img.mvmjsc0
/wp-content/uploads/sites/2/2026/04/gettyimages-224249349...17.4 KiB14.2 KiB
How Georgia manufactured the Peach State myth div.lqawqb6 > div.duet--content-cards--content-card > div._1agz5xb7 > img.mvmjsc0
/wp-content/uploads/sites/2/2026/03/Peaches_Thumbnail_05....11.2 KiB4.1 KiB

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: 242 ms
URLTime Spent
vox.com/242 ms
www.vox.com/0.0 ms

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.

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.3 s
Other445 ms
Script Parsing & Compilation185 ms
Style & Layout184 ms
Rendering85 ms
Garbage Collection83 ms
Parse HTML & CSS45 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

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 15.0 KiB
URLTransfer SizeEst Savings
www.vox.com/_next/static/css/05d88cec0dec7d53.css27.4 KiB15.0 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Sponsor Logo div._1yq350vc > div._1yq350v6 > div._1yq350vh > img._1yq350vg

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

●Layout shift culprits
●Optimize DOM size
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 27 user timings
●Avoid long main-thread tasks 8 long tasks found
●Network Requests
●Network Round Trip Times 90 ms
●Server Backend Latencies 100 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 0 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
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.

○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
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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
ConcertAds: (73ms) loadMotifTargeting failed to fetch targeting from https://cdn.concert.io/lookup/
Failed to load resource: the server responded with a status of 401 ()
Failed to load resource: the server responded with a status of 404 ()
●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