Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

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.

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.

URL	Transfer Size	Duration
workers.cloudflare.com/_astro/index.BTYsgzhb.css	56.0 KiB	450 ms
workers.cloudflare.com/_astro/_slug_.JLjW3X1R.css	1.0 KiB
ot.www.cloudflare.com/ot/scripttemplates/otSDKStub.js	8.5 KiB	775 ms
workers.cloudflare.com/_astro/agents.By3b-lcZ.css	1.5 KiB	150 ms
workers.cloudflare.com/_astro/_editorPath_.D7O2pGyb.css	4.2 KiB

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.

Request	Cache TTL	Transfer Size
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
cdn.cookielaw.org/logos/static/ot_close.svg	86400.0 s	881 B

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: 755 ms

URL	Time Spent
workers.dev/	755 ms
workers.cloudflare.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.

Estimated savings: 310 ms 550.4 KiB

URL	Transfer Size	Est Savings
workers.cloudflare.com/_astro/_icon.B3faMrhj.js	189.6 KiB	185.1 KiB
workers.cloudflare.com/_astro/registry.CI6CKhvu.js	149.2 KiB	147.3 KiB
workers.cloudflare.com/_astro/paper-full.BYcUELjp.js	118.0 KiB	82.8 KiB
ot.www.cloudflare.com/ot/scripttemplates/202503.1.0/otBannerSdk.js	109.8 KiB	66.2 KiB
workers.cloudflare.com/_astro/common.0FHQb7_N.js	25.1 KiB	24.3 KiB
workers.cloudflare.com/_astro/proxy.CVQLZZWt.js	38.9 KiB	23.3 KiB
workers.cloudflare.com/_astro/client.CaeA_d_Z.js	55.4 KiB	21.5 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Other	2.3 s
Script Evaluation	1.3 s
Style & Layout	1.2 s
Rendering	419 ms
Parse HTML & CSS	128 ms
Script Parsing & Compilation	84 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.relative > astro-island > div.fixed > img `div.relative > astro-island > div.fixed > img`	workers.cloudflare.com/companies/shopify.png
div.relative > astro-island > div.fixed > img `div.relative > astro-island > div.fixed > img`	workers.cloudflare.com/companies/coreweave.png
div.relative > astro-island > div.fixed > img `div.relative > astro-island > div.fixed > img`	workers.cloudflare.com/companies/wix.png
div.relative > astro-island > div.fixed > img `div.relative > astro-island > div.fixed > img`	workers.cloudflare.com/companies/leonardo.png
div.relative > astro-island > div.fixed > img `div.relative > astro-island > div.fixed > img`	workers.cloudflare.com/companies/anthropic.png
div.relative > astro-island > div.fixed > img `div.relative > astro-island > div.fixed > img`	workers.cloudflare.com/companies/asana.png
div.relative > astro-island > div.fixed > img `div.relative > astro-island > div.fixed > img`	workers.cloudflare.com/companies/atlassian.png
div.relative > astro-island > div.fixed > img `div.relative > astro-island > div.fixed > img`	workers.cloudflare.com/companies/stripe.png
div.relative > astro-island > div.fixed > img `div.relative > astro-island > div.fixed > img`	workers.cloudflare.com/companies/block.png
div.relative > astro-island > div.fixed > img `div.relative > astro-island > div.fixed > img`	workers.cloudflare.com/companies/canva.png
div.relative > astro-island > div.fixed > img `div.relative > astro-island > div.fixed > img`	workers.cloudflare.com/companies/intercom.png
div.relative > astro-island > div.fixed > img `div.relative > astro-island > div.fixed > img`	workers.cloudflare.com/companies/doordash.png

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 1,522 KiB

●JavaScript execution time 1.3 s

●Avoid long main-thread tasks 13 long tasks found

●Avoid non-composited animations 8 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 330 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 500 ms

●Avoid large layout shifts 11 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Start building `div.mx-auto > div#nav-action-buttons > astro-island > a.relative`
Cloudflare is your AI Cloud with compute, AI inference, and storage — letting y… `div.px-section > div.max-w-8xl > div.flex > p.text-light-foreground`
"Cloudflare provided everything from OAuth to out-of-the-box remote MCP support… `div.relative > div#architecture-panel-0 > div.pointer-events-none > p.text-foreground-100/50`
~/workspace/multiplayer-app git:(main) `div.bg-background-100 > astro-island > div.text-xs > div.mb-2`
Paid `div.relative > div.bg-background-100 > div.flex > code.text-accent-100`
Free `div.relative > div.bg-background-100 > div.flex > code.text-accent-100/50`
See more `div.divide-brand-6 > div.relative > div.flex > a.relative`
Starts at $5/month `div.relative > div.flex > div.flex > p.text-accent-100/70`
Start building for free `astro-island > a#start-building-button > astro-slot > span`
View docs `astro-island > a.relative > astro-slot > span`
Getting Started `div.grid > div.flex > div.mb-3 > span.text-foreground-200/50`
Resources `div.grid > div.flex > div.mb-3 > span.text-foreground-200/50`
Solutions `div.grid > div.flex > div.mb-3 > span.text-foreground-200/50`
© 2026 Cloudflare, Inc. `footer.z-10 > div.bg-background-100 > div.pointer-events-auto > span.text-foreground-200/40`
English `div.text-foreground-200/40 > astro-island > button#radix-_r65R_0_ > span`
Your Privacy Choices `div.text-foreground-200/40 > astro-island > button.inline-flex > span`
Privacy Policy, Terms of Service, GDPR `div.bg-background-100 > div.pointer-events-auto > div.text-foreground-200/40 > div`
Privacy Policy `div.pointer-events-auto > div.text-foreground-200/40 > div > a.hover:text-foreground-100/70`
Terms of Service `div.pointer-events-auto > div.text-foreground-200/40 > div > a.hover:text-foreground-100/70`
GDPR `div.pointer-events-auto > div.text-foreground-200/40 > div > a.hover:text-foreground-100/70`
Reject All `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-reject-all-handler`
Accept All Cookies `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-accept-btn-handler`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
The cloud that works for you, not the other way around `section#home-title-1 > div.flex > div.mx-auto > h3.text-foreground-100`
Run everywhere `div.relative > div.bg-background-100 > div.text-foreground-200 > h6.mt-2`
From first line to full scale `div > div.bg-background-100 > div.relative > h6.text-foreground-100`
Wall Clock vs. CPU Time `div.border-b > div.grid > div.flex > h6.text-foreground-200`
100,000 `div#home-pricing-panel-free-0 > div.flex > div.flex > h6.leading-none`
$0.30 `div#home-pricing-panel-paid-0 > div.flex > div.flex > h6.leading-none`
Fits into your existing workflows `div.lg:col-span-8 > div.bg-background-100 > div.flex > h6.text-foreground-100`

These are opportunities to improve keyboard navigation in your application.

○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

●`[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

●ARIA input fields have accessible names

●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

●Links are distinguishable without relying on color.

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

○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

General

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.

URL
workers.cloudflare.com/_astro/registry.CI6CKhvu.js
workers.cloudflare.com/_astro/_icon.B3faMrhj.js

●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

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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.

Link destination	Link Text
blog.cloudflare.com/	here
workers.cloudflare.com/plans	See more
workers.cloudflare.com/plans	See more

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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○Image elements have `[alt]` attributes