Skip to content
https://speedtest.net

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.

41

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.

RequestCache TTLTransfer Size
b.cdnst.net/javascript/speedtest-main.js?v=740e4726565b535af6c9481d7ff91b6a86400.0 s1.5 MiB
cdn.ziffstatic.com/pg/speedtest.prebid.js2050.0 s232.1 KiB
www.speedtest.net/s/fonts/Montserrat-Italic-VariableFont_wght-hint-all.woff260.0 s120.0 KiB
www.speedtest.net/s/fonts/Montserrat-VariableFont_wght-hint-all.woff260.0 s116.1 KiB
openads-cdn.adsrvr.org/openadsjs/build/v1.0/ziffdavis/openads.js0.0 ms89.9 KiB
cdn.static.zdbb.net/eu/js/z0WVjCBSEeGLoxIxOQVEwQ.min.js86400.0 s175.1 KiB
client.aps.amazon-adsystem.com/publisher.js3600.0 s82.5 KiB
b.cdnst.net/images/gauge-gradient-dl-multi-web.png86400.0 s76.8 KiB
b.cdnst.net/images/gauge-gradient-ul-multi-web.png86400.0 s72.7 KiB
www.speedtest.net/s/fonts/Montserrat-VariableFont_wght-kern-latin.woff260.0 s28.5 KiB
cdn.ziffstatic.com/pg/speedtest.js2581.0 s33.5 KiB
b.cdnst.net/images/gauge-gradient-ul-single-web.png86400.0 s63.9 KiB
cdn.ziffstatic.com/jst/zdconsent_eu.js605.0 s27.8 KiB
b.cdnst.net/images/gauge-gradient-dl-single-web.png86400.0 s61.0 KiB
cdn.ziffstatic.com/jst/otBannerSdk.202512.1.0.js534454.0 s126.2 KiB
b.cdnst.net/styles/main.c94cd88435f3e907a9963e080e58198b.css86400.0 s29.1 KiB
www.speedtest.net/images/android-app-promo-1x.png86400.0 s29.0 KiB
appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js86400.0 s17.4 KiB
www.speedtest.net/s/fonts/gaugemono-regular-webfont.woff260.0 s4.3 KiB
b.cdnst.net/images/icg_how_much_speed.png86400.0 s10.7 KiB
b.cdnst.net/images/ad-free-125x101-fade-anim-1x.gif86400.0 s9.7 KiB
sb.scorecardresearch.com/beacon.js86400.0 s6.7 KiB
cdn.ziffstatic.com/jst/otTCF.202512.1.0.js534455.0 s17.7 KiB
www.speedtest.net/images/Download_on_the_Mac_App_Store_Badge_US-UK_165x40.svg86400.0 s5.1 KiB
config.aps.amazon-adsystem.com/configs/33363600.0 s2.1 KiB
b.cdnst.net/images/icg_desktop_apps.svg86400.0 s3.3 KiB
b.cdnst.net/images/dd-logo.svg86400.0 s2.5 KiB
cdn.ziffstatic.com/pg/speedtest.css2576.0 s1.2 KiB
b.cdnst.net/images/mobile_apps.svg86400.0 s2.2 KiB
b.cdnst.net/images/icg_talk_to_isp.svg86400.0 s1.9 KiB
b.cdnst.net/images/icg_check_outages.svg86400.0 s1.8 KiB
b.cdnst.net/images/icg_troubleshoot_wifi.svg86400.0 s1.3 KiB
b.cdnst.net/images/icg_get_help.svg86400.0 s1.1 KiB
b.cdnst.net/images/icg_qr_code.svg86400.0 s1.0 KiB
cdn.ziffstatic.com/ajs?zoneid=a3600.0 s298 B
b.cdnst.net/javascript/ads/ad.js86400.0 s237 B

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:13.015 source:map[column:224 line:158 type:source-location url:https://cdn.ziffstatic.com/pg/speedtest.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:13.015 source:map[column:85 line:152 type:source-location url:https://cdn.ziffstatic.com/pg/speedtest.js urlProvider:network]] map[reflowTime:19.835 source:map[type:text value:[unattributed]]] map[reflowTime:1.211 source:map[column:132 line:76 type:source-location url:https://cdn.ziffstatic.com/pg/speedtest.js urlProvider:network]] map[reflowTime:0.519 source:map[column:447 line:107 type:source-location url:https://cdn.ziffstatic.com/jst/zdconsent.js urlProvider:network]]]

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

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.

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
Speed requirement div.pure-u-1-3 > a > div.homepage-lower-btn > img.homepage-lower-icon
b.cdnst.net/images/icg_how_much_speed.png10.6 KiB9.0 KiB

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

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.

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: 203 ms
URLTime Spent
speedtest.net/203 ms
www.speedtest.net/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

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.2 s
Script Parsing & Compilation496 ms
Other385 ms
Style & Layout89 ms
Garbage Collection81 ms
Parse HTML & CSS63 ms
Rendering24 ms

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.

URL
Speed requirement div.pure-u-1-3 > a > div.homepage-lower-btn > img.homepage-lower-icon
b.cdnst.net/images/icg_how_much_speed.png
Desktop apps div.pure-u-1-3 > a > div.homepage-lower-btn > img.homepage-lower-icon
b.cdnst.net/images/icg_desktop_apps.svg
QR code for downloading mobile app div.pure-u-1-3 > div.qr-and-text > div.homepage-lower-btn > img.homepage-lower-icon
b.cdnst.net/images/icg_qr_code.svg
Wi-Fi troubleshooting div.pure-u-1-3 > a > div.homepage-lower-btn > img.homepage-lower-icon
b.cdnst.net/images/icg_troubleshoot_wifi.svg
Check outages div.pure-u-1-3 > a > div.homepage-lower-btn > img.homepage-lower-icon
b.cdnst.net/images/icg_check_outages.svg
Talk to ISP div.pure-u-1-3 > a > div.homepage-lower-btn > img.homepage-lower-icon
b.cdnst.net/images/icg_talk_to_isp.svg

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
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
User Timing marks and measures 13 user timings
Avoid long main-thread tasks 12 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 250 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 30 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
LCP request discovery
Avoid non-composited animations
96

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Speedtest div.nav > div.pure-g > div.pure-u-1 > a.masthead-logo
GO div.speedtest-view > div.speedtest-container > div.start-button > a.js-start-test
Multi div > div.test-modes-wrapper > div.toggle > a.test-mode
Single div > div.test-modes-wrapper > div.toggle > a.test-mode

These are opportunities to improve keyboard navigation in your application.

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
GO div.speedtest-view > div.speedtest-container > div.start-button > a.js-start-test
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
`[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
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
Image elements do not have `[alt]` attributes that are redundant text.
`[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 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
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.
100

Best Practices

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 browser errors logged to the console
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
Page has valid source maps
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