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.

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:49.201 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

value: no origins were preconnected

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

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
/_next/static/chunks/1ulxm8je42reo.css?dpl=dpl_4QWkBNARjj...	2.0 KiB	150 ms
/_next/static/chunks/0mta2usetb963.css?dpl=dpl_4QWkBNARjj...	59.1 KiB	300 ms
/_next/static/chunks/3-sarejflg6w8.css?dpl=dpl_4QWkBNARjj...	18.7 KiB	150 ms
/_next/static/chunks/3_0z56c80yk_-.css?dpl=dpl_4QWkBNARjj...	4.4 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
cdn.cr-relay.com/v1/site/f6dd8ada-7a97-4d9d-8ec4-9c2bff6cd234/signals.js	3600.0 s	7.1 KiB

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.

	URL	Resource Size	Est Savings
An image gallery built on Next.js and Cloudinary. `div.flex > div.flex > div.flex > img.templates-module__f0q_8W__image`	/_next/image?url=https%3A%2F%2Fh8DxKfmAPhn8O0p3.public.bl...	121.2 KiB	118.3 KiB
An all-in-one starter kit for high-performance ecommerce sites. `div.flex > div.flex > div.flex > img.templates-module__f0q_8W__image`	/_next/image?url=https%3A%2F%2Fh8DxKfmAPhn8O0p3.public.bl...	44.1 KiB	43.7 KiB
A Next.js starter from create-next-app. `div.flex > div.flex > div.flex > img.templates-module__f0q_8W__image`	/_next/image?url=https%3A%2F%2Fh8DxKfmAPhn8O0p3.public.bl...	16.3 KiB	16.1 KiB
A tree structure of 3D spheres are connected by lines `div > a.features-module__KQTBcq__card > div > img.features-module__KQTBcq__lightMode`	/_next/image?url=https%3A%2F%2Fh8DxKfmAPhn8O0p3.public.bl...	18.3 KiB	15.1 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.

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.

Estimated savings: 300 ms 85.9 KiB

URL	Transfer Size	Est Savings
/_next/static/chunks/3u6nxjif50jic.js?dpl=dpl_4QWkBNARjjn...	35.5 KiB	35.3 KiB
/_next/static/chunks/0la2krl14st5p.js?dpl=dpl_4QWkBNARjjn...	48.0 KiB	27.6 KiB
/_next/static/chunks/0a1x1u7w7w_b6.js?dpl=dpl_4QWkBNARjjn...	71.1 KiB	23.0 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.

URL	Total CPU Time	Script Evaluation	Script Parse
/_next/static/chunks/0a1x1u7w7w_b6.js?dpl=dpl_4QWkBNARjjn...	1.5 s	1.3 s	28 ms
nextjs.org/	1.3 s	53 ms	33 ms
/_next/static/chunks/23n3nv5rywuse.js?dpl=dpl_4QWkBNARjjn...	823 ms	145 ms	5.1 ms
Unattributable	567 ms	13 ms	0.0 ms
/_next/static/chunks/turbopack-1amk6zjhjcqld.js?dpl=dpl_4...	213 ms	211 ms	1.5 ms
/_next/static/chunks/0la2krl14st5p.js?dpl=dpl_4QWkBNARjjn...	151 ms	91 ms	26 ms
/_next/static/chunks/14k92bxdc7_ks.js?dpl=dpl_4QWkBNARjjn...	78 ms	45 ms	22 ms

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
Script Evaluation	1.9 s
Other	1.4 s
Style & Layout	957 ms
Rendering	319 ms
Script Parsing & Compilation	233 ms
Parse HTML & CSS	113 ms
Garbage Collection	29 ms

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 14.0 KiB

URL	Transfer Size	Est Savings
/_next/static/chunks/3-sarejflg6w8.css?dpl=dpl_4QWkBNARjj...	18.4 KiB	14.0 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●Avoid long main-thread tasks 10 long tasks found

●Avoid non-composited animations 7 animated elements found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 60 ms

●Server Backend Latencies 30 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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

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
▲ ~ npx create-next-app@latest `div.intro-module__l-DIkW__intro > div.flex > div.flex > button.intro-module__l-DIkW__copy`
Built-in Optimizations Automatic Image, Font, and Script Optimizations for impr… `div.flex > div.features-module__KQTBcq__grid > div > a.features-module__KQTBcq__card`
Dynamic HTML Streaming Instantly stream UI from the server, integrated with the… `div.flex > div.features-module__KQTBcq__grid > div > a.features-module__KQTBcq__card`
React Server Components Add components without sending additional client-side J… `div.flex > div.features-module__KQTBcq__grid > div > a.features-module__KQTBcq__card`
Next.js 16 The power of full-stack to the frontend. Read the release notes. `div.flex > div.features-module__KQTBcq__grid > div > a.features-module__KQTBcq__card`

○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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●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

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

○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

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

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

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.

Source	Description
nextjs.org/api/get-session	`Failed to load resource: the server responded with a status of 401 ()`
nextjs.org/ line 5, col 0	`Loading the font 'https://k2mkucxia43oc7fa.public.blob.vercel-storage.com/front/fonts/space-mono/space-mono-v11-latin-regular.woff2' violates the following Content Security Policy directive: "font-src 'self' .nextjs.org .vercel.com .gstatic.com vercel.live .vercel.sh". The action has been blocked.`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●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

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`