Skip to content
https://vox.com

Lighthouse Mobile

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

31

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:80.948 source:map[type:text value:[unattributed]]]]

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
Why Trump is tearing up a beloved national park div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/gettyimages-228973334...75.6 KiB70.4 KiB
Why scientists are using cheap picnic coolers to protect some of the world’s mo… div.tsnmpo1 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/JLA8341-1.jpg?quality...68.2 KiB49.2 KiB
Should you spend your money on retirement or give it to your kids? div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/Nest-Egg.jpg?quality=...47.7 KiB44.4 KiB
How religion can help you have better sex (seriously!) div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/LorenaSpurio_AugustSo...42.4 KiB39.5 KiB
People are betting on wildfires on Polymarket. What could go wrong? div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/gettyimages-228717581...43.4 KiB38.2 KiB
A new housing politics is taking shape on the left div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/GettyImages-227605439...36.8 KiB34.3 KiB
Ozempic is not just a weight-loss story anymore div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/GettyImages-227948488...36.6 KiB34.1 KiB
Hasan Piker isn’t retreating div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/gettyimages-228805868...33.7 KiB28.9 KiB
How to bring more playfulness to your everyday life div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/GettyImages-132820699...30.9 KiB28.8 KiB
Ozempic is not just a weight-loss story anymore div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/GettyImages-227948488...32.4 KiB27.9 KiB
How to bring more playfulness to your everyday life div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/GettyImages-132820699...30.7 KiB26.3 KiB
This hamster has a Strava and runs more than you. It’s not as cute as it sounds. div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/Mollie-the-Hamster.pn...22.7 KiB21.2 KiB
Everybody needs a personal AI policy. Just ask Hank Green. div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/AP26028019695368.jpg?...17.7 KiB16.5 KiB
The definitive guide to canceling plans div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/07/GettyImages-228510211...14.4 KiB13.5 KiB
How to rebuild your broken attention span div.a5kjze2 > div.duet--content-cards--content-card > div._11rr6on7 > img._1ssnpw50
/wp-content/uploads/sites/2/2026/08/GettyImages-227463114...14.3 KiB13.4 KiB

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.

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

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

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: 150 ms 37.8 KiB
URLTransfer SizeEst Savings
23.5 KiB20.5 KiB
www.vox.com/_next/static/css/6e1a147951515e1a.css28.1 KiB17.3 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.

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 Evaluation7.7 s
Other2.5 s
Script Parsing & Compilation686 ms
Style & Layout630 ms
Garbage Collection436 ms
Rendering382 ms
Parse HTML & CSS160 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

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._12y2yrnc > div._12y2yrn6 > div._12y2yrnh > img._12y2yrng

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
●Modern HTTP
●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
●Avoid non-composited animations 1 animated element found
●Network Requests
●Network Round Trip Times 100 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
●Avoid large layout shifts 10 layout shifts found
○INP breakdown
○LCP request discovery
97

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.

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
Privacy Notice div.gezj8c0 > ul.gezj8c1 > li.gezj8c2 > a.gezj8c3
Terms of Use div.gezj8c0 > ul.gezj8c1 > li.gezj8c2 > a.gezj8c3
Platform Status div.gezj8c0 > ul.gezj8c1 > li.gezj8c2 > a.gezj8c3
Careers div.gezj8c0 > ul.gezj8c1 > li.gezj8c2 > a.gezj8c3

These items highlight common accessibility best practices.

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
Cookie 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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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
○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.
○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: (114ms) 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 ()

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.

●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