Skip to content
https://speedtest.net

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.

21

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.js2074.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
www.speedtest.net/images/app-promo-image@2x.png86400.0 s148.4 KiB
b.cdnst.net/images/app-promo-image@2x.png86400.0 s148.3 KiB
www.speedtest.net/images/android-app-promo-2x.png86400.0 s92.0 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.6 KiB
cdn.ziffstatic.com/pg/speedtest.js2605.0 s33.5 KiB
b.cdnst.net/images/gauge-gradient-ul-single-web.png86400.0 s63.9 KiB
cdn.ziffstatic.com/jst/zdconsent_eu.js629.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.js534479.0 s126.2 KiB
b.cdnst.net/styles/main.c94cd88435f3e907a9963e080e58198b.css86400.0 s29.1 KiB
appleid.cdn-apple.com/appleauth/static/jsapi/appleid/1/en_US/appleid.auth.js86400.0 s17.4 KiB
b.cdnst.net/images/icg_how_much_speed.png86400.0 s10.7 KiB
www.speedtest.net/s/fonts/gaugemono-regular-webfont.woff260.0 s4.3 KiB
sb.scorecardresearch.com/beacon.js86400.0 s6.7 KiB
cdn.ziffstatic.com/jst/otTCF.202512.1.0.js534480.0 s17.7 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/mobile-badges/google-play-EN.svg86400.0 s2.6 KiB
cdn.ziffstatic.com/pg/speedtest.css2600.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
www.speedtest.net/images/scroll_for_more.svg86400.0 s671 B
cdn.ziffstatic.com/ajs?zoneid=a3600.0 s298 B
b.cdnst.net/javascript/ads/ad.js86400.0 s237 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.126284] map[node:map[boundingRect:map[bottom:2329 height:782 left:0 right:412 top:1547 width:412] lhId:page-1-FOOTER nodeLabel:SPEEDTEST® Advertise Speedtest Awards™ Speedtest Servers™ Speedtest Performance… path:1,HTML,1,BODY,5,DIV,5,FOOTER selector:body.layout-mobile > div > footer.footer snippet:<footer class="footer" role="contentinfo"> type:node] score:0.121507] map[node:map[boundingRect:map[bottom:870 height:126 left:224 right:380 top:744 width:157] lhId:page-2-IMG nodeLabel:Wi-Fi troubleshooting path:1,HTML,1,BODY,5,DIV,3,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,1,DIV,0,A,0,DIV,0,IMG selector:div.pure-u-1-3 > a > div.homepage-lower-btn > img.homepage-lower-icon snippet:<img src="//b.cdnst.net/images/icg_troubleshoot_wifi.svg" alt="Wi-Fi troubleshooting" class="homepage-lower-icon"> type:node] score:0.004777 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:689 height:25 left:355 right:371 top:664 width:16] lhId:page-5-IMG nodeLabel:Arrow down image path:1,HTML,1,BODY,5,DIV,1,DIV,2,DIV,0,DIV,2,DIV,0,DIV,2,DIV,2,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,1,A,0,IMG selector:div.ispComponent > div.connection-mobile > a.connection-mobile-scroll > img snippet:<img src="/images/scroll_for_more.svg" alt="Arrow down image"> type:node]]] type:subitems]]]

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.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:237.397 label:Time to first byte subpart:timeToFirstByte] map[duration:2362.696 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-DIV
nodeLabel: We and our 998 partners store and access personal data, like browsing data or u…
path: 1,HTML,1,BODY,13,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,3,DIV
selector: div.ot-sdk-row > div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text
snippet: <div id="onetrust-policy-text">

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
div.mobile-banner-container > a.webstore-app-links > div.download-images > img#banner-image div.mobile-banner-container > a.webstore-app-links > div.download-images > img#banner-image
b.cdnst.net/images/app-promo-image@2x.png148.1 KiB123.5 KiB
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 KiB7.0 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

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
SPEEDTEST® Advertise Speedtest Awards™ Speedtest Servers™ Speedtest Performance… body.layout-mobile > div > footer.footer
0.122
Wi-Fi troubleshooting div.pure-u-1-3 > a > div.homepage-lower-btn > img.homepage-lower-icon
0.005

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 26.3 KiB
URLTransfer SizeEst Savings
b.cdnst.net/styles/main.c94cd88435f3e907a9963e080e58198b.css28.9 KiB26.3 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 Evaluation9.6 s
Script Parsing & Compilation2.1 s
Other1.6 s
Style & Layout306 ms
Garbage Collection285 ms
Parse HTML & CSS146 ms
Rendering72 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
div.mobile-banner-container > a.webstore-app-links > div.download-images > img#banner-image div.mobile-banner-container > a.webstore-app-links > div.download-images > img#banner-image
b.cdnst.net/images/app-promo-image@2x.png
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
Mobile Apps div.pure-u-1-3 > a > div.homepage-lower-btn > img.homepage-lower-icon
b.cdnst.net/images/mobile_apps.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
Help div.pure-u-1-3 > a > div.homepage-lower-btn > img.homepage-lower-icon
b.cdnst.net/images/icg_get_help.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
Get it on Google Play a.webstore-app-links > div.download-images > span > img
b.cdnst.net/images/mobile-badges/google-play-EN.svg
Arrow down image div.ispComponent > div.connection-mobile > a.connection-mobile-scroll > img
www.speedtest.net/images/scroll_for_more.svg

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

Optimize DOM size
Forced reflow
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 13 user timings
Avoid long main-thread tasks 20 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 180 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 210 ms
INP breakdown
LCP request discovery
Avoid non-composited animations
86

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Speedtest is better with the app. Download the Speedtest app for more metrics, … div.main-view > div > div.mobile-pretest > div.mobile-pretest-new

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.mobile-pretest > div.mobile-pretest-new > a.close-btn div > div.mobile-pretest > div.mobile-pretest-new > a.close-btn

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.

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.pure-u-1 > div.mobile-start-wrapper > div.start-button > a.js-start-test

These are opportunities to improve keyboard navigation in your application.

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
Android div.apps > ul.menu-footer > li > a
Apple TV div.apps > ul.menu-footer > li > a
macOS div.apps > ul.menu-footer > li > a
Windows div.apps > ul.menu-footer > li > a

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
GO div.pure-u-1 > div.mobile-start-wrapper > 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
`[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.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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.
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
Uncaught Error: Minified React error #200; visit https://reactjs.org/docs/error-decoder.html?invariant=200 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
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
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