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 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
pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/aqueduct-30s.jpg	0.0 ms	89.1 KiB
/videos/wan3-demos/cinematic-drone.jpg	0.0 ms	88.8 KiB
/videos/wan3-demos/reference-multi.jpg	0.0 ms	88.2 KiB
pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/character-walk.jpg	0.0 ms	57.3 KiB
pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/hero-audio.jpg	0.0 ms	53.4 KiB
pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/fashion-runway.jpg	0.0 ms	24.5 KiB
pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/product-spin.jpg	0.0 ms	20.8 KiB

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:107.539 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.

	URL	Resource Size	Est Savings
div.grid > div.relative > div.relative > video.absolute `div.grid > div.relative > div.relative > video.absolute`	/videos/wan3-demos/reference-multi.jpg	87.9 KiB	81.6 KiB
Aerial brand pass `div.grid > article.group > div.relative > img.absolute`	/videos/wan3-demos/cinematic-drone.jpg	88.5 KiB	77.9 KiB
Character walk cycle `div.grid > article.group > div.relative > img.absolute`	pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/character-walk.jpg	57.0 KiB	50.2 KiB
Sound-led moment `div.grid > article.group > div.relative > img.absolute`	pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/hero-audio.jpg	53.1 KiB	46.8 KiB
WAN 3.0 Video demo still — cinematic AI video with native audio `section#hero-screen > div.absolute > div.pointer-events-none > img.absolute`	pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/aqueduct-30s.jpg	88.8 KiB	43.3 KiB
Runway energy `div.grid > article.group > div.relative > img.absolute`	pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/fashion-runway.jpg	24.3 KiB	21.4 KiB
Product turntable `div.grid > article.group > div.relative > img.absolute`	pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/product-spin.jpg	20.5 KiB	15.4 KiB

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/aqueduct-30s.jpg	http/1.1
/videos/wan3-demos/reference-multi.jpg	http/1.1
pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/fashion-runway.jpg	http/1.1
pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/hero-audio.jpg	http/1.1
/videos/wan3-demos/cinematic-drone.jpg	http/1.1
pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/product-spin.jpg	http/1.1
pub-9b1817b5121741ee93af6f9118d81391.r2.dev/videos/wan3-demos/character-walk.jpg	http/1.1

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

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
wan3video.art/assets/index-BUJFAmxC.css	32.8 KiB	300 ms

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

Diagnostics

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
Style & Layout	770 ms
Script Evaluation	672 ms
Other	613 ms
Rendering	96 ms
Parse HTML & CSS	60 ms
Script Parsing & Compilation	29 ms

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

●Max Potential First Input Delay 90 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●LCP request discovery

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 916 KiB

●JavaScript execution time 0.7 s

●Avoid long main-thread tasks 6 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 220 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 150 ms

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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 free `div.mt-3 > div.min-w-0 > button.inline-flex > span`
Fashion `div.grid > article.group > div.flex > p.mt-3`
Sound-forward · ~15s `div.grid > article.group > div.flex > p.mt-3`
Wide establishing `div.grid > article.group > div.flex > p.mt-3`
Tabletop `div.grid > article.group > div.flex > p.mt-3`
Identity `div.grid > article.group > div.flex > p.mt-3`
Travel `div.grid > article.group > div.flex > p.mt-3`
Today on this desk: text-to-video, image-to-video, references, duration/aspect … `section#multimodal-proof > div.mx-auto > div.mx-auto > p.mt-2`
01 `div.mt-12 > article.group > div.flex > span.font-display`
02 `div.mt-12 > article.group > div.flex > span.font-display`
03 `div.mt-12 > article.group > div.flex > span.font-display`
04 `div.mt-12 > article.group > div.flex > span.font-display`
05 `div.mt-12 > article.group > div.flex > span.font-display`
06 `div.mt-12 > article.group > div.flex > span.font-display`
When starter credits are enabled, new accounts receive a trial balance for a fi… `div.mx-auto > div.flex > details.group > div.px-5`
VIDEO `div > div.flex > div.flex > div.mt-1`
CREATE `div.mx-auto > div.grid > div > p.mb-4`
USE CASES `div.mx-auto > div.grid > div > p.mb-4`
LEGAL `div.mx-auto > div.grid > div > p.mb-4`
CONTACT `div.mx-auto > div.grid > div > p.mt-8`
FEATURED ON `footer#contact-section > section.border-t > div.mx-auto > p.mb-2.5`

These are opportunities to improve the legibility of your content.

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
AI Enhance `div.flex > div.relative > div.absolute > button.flex`

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
Install App `div.relative > div.fixed > div.group > button.inline-flex`

○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

●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

●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"]`

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

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

○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

●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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`