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.

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
tailwindcss.com/_next/static/chunks/0aa6f91bf69bba4f.css	78.0 KiB	451 ms
tailwindcss.com/_next/static/chunks/22067bb27c370d37.css	1.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
div.bg-white > div.mt-6 > div.relative > img.sm:hidden `div.bg-white > div.mt-6 > div.relative > img.sm:hidden`	tailwindcss.com/_next/static/media/css-grid-1.mobile.683ba765.png	584.7 KiB	547.1 KiB
div.flex > div.relative > div.grid > img.h-48 `div.flex > div.relative > div.grid > img.h-48`	tailwindcss.com/_next/static/media/responsive-1.369fbbd4.png	454.3 KiB	417.7 KiB
div.h-112 > div.@container > div.absolute > img.size-64 `div.h-112 > div.@container > div.absolute > img.size-64`	tailwindcss.com/_next/static/media/filters.09770f52.png	323.5 KiB	290.8 KiB
div.absolute > div.@container > div.relative > img.size-48 `div.absolute > div.@container > div.relative > img.size-48`	tailwindcss.com/_next/static/media/cover.f75d494c.png	211.0 KiB	192.6 KiB
div.isolate > div.relative > div.col-start-1 > img.absolute `div.isolate > div.relative > div.col-start-1 > img.absolute`	tailwindcss.com/_next/static/media/dark-mode.light.4b26783a.png	113.8 KiB	38.8 KiB
div.isolate > div.relative > div.col-start-1 > img `div.isolate > div.relative > div.col-start-1 > img`	tailwindcss.com/_next/static/media/dark-mode.dark.9634b3d8.png	106.0 KiB	36.1 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.

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

URL	Transfer Size	Est Savings
tailwindcss.com/_next/static/chunks/396c9350f71c1071.js	28.2 KiB	27.1 KiB
tailwindcss.com/_next/static/chunks/16a6a8ec5f5434fe.js	27.5 KiB	25.5 KiB
tailwindcss.com/_next/static/chunks/33e576c593493439.js	69.6 KiB	23.7 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
tailwindcss.com/	3.1 s	65 ms	180 ms
tailwindcss.com/_next/static/chunks/33e576c593493439.js	2.2 s	1.4 s	34 ms
tailwindcss.com/_next/static/chunks/70e258b44c36445b.js	1.7 s	651 ms	19 ms
Unattributable	713 ms	44 ms	0.0 ms
tailwindcss.com/_next/static/chunks/6120162fc820413f.js	262 ms	159 ms	19 ms
tailwindcss.com/_next/static/chunks/0aa6f91bf69bba4f.css	169 ms	0.0 ms	0.0 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
Style & Layout	2.4 s
Script Evaluation	2.4 s
Other	2.2 s
Rendering	527 ms
Script Parsing & Compilation	355 ms
Parse HTML & CSS	343 ms
Garbage Collection	21 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
tailwindcss.com/_next/static/media/templates-col-2.17fea2a5.png	593.7 KiB
tailwindcss.com/_next/static/media/css-grid-1.8a3ab48a.png	585.9 KiB
tailwindcss.com/_next/static/media/css-grid-1.mobile.683ba765.png	585.8 KiB
tailwindcss.com/_next/static/media/responsive-1.369fbbd4.png	455.4 KiB
tailwindcss.com/_next/static/media/css-grid-4.31d79ba9.png	453.0 KiB
tailwindcss.com/_next/static/media/templates-col-1.3d4d7b6a.png	449.8 KiB
tailwindcss.com/_next/static/media/templates-col-3.4c4b09ad.png	392.4 KiB
tailwindcss.com/_next/static/media/InterVariable_Italic-s.p.8c0e9517.woff2	379.8 KiB
tailwindcss.com/_next/static/media/InterVariable-s.p.53d7b668.woff2	344.8 KiB
tailwindcss.com/_next/static/media/filters.09770f52.png	324.4 KiB

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoid long main-thread tasks 9 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 80 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 30 ms

●Avoid large layout shifts 4 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
index.html `div.flex > div.isolate > div.sticky > button.isolate`
Terminal `div.flex > div.isolate > div.sticky > button.isolate`
build.css `div.flex > div.isolate > div.sticky > button.isolate`

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.

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
text-4xl text-gray-950 tracking-tighter `div.grid > div.grid > div > div.flex`
text-4xl `div.grid > div > div.flex > span.hidden`
text-gray-950 `div.grid > div > div.flex > span.inline`
text-lg text-gray-950 font-medium `div.grid > div.grid > div > div.flex`
text-gray-950 `div.grid > div > div.flex > span.inline`
Quick search Ctrl K `div > div.mt-4 > div.flex > button.grid`
SPONSORS `div.grid > div.relative > div.2xl:before:hidden > p.text-sky-500`
text-base text-gray-950 `div.grid > div.grid > div.relative > div.flex`
text-gray-950 `div.grid > div.relative > div.flex > span.inline`
WHY TAILWIND CSS? `div.grid > div.relative > div.2xl:before:hidden > p.text-pink-500`
text-base text-gray-950 `div.grid > div.grid > div.relative > div.flex`
text-gray-950 `div.grid > div.relative > div.flex > span.inline`
HOW IT WORKS `div.grid > div.relative > div.2xl:before:hidden > p.text-sky-500`
text-base text-gray-950 `div.grid > div.grid > div.relative > div.flex`
text-gray-950 `div.grid > div.relative > div.flex > span.inline`
text-4xl text-gray-950 tracking-tighter `div.grid > div.grid > div.relative > div.h-6`
text-gray-950 `div.grid > div.relative > div.h-6 > span.inline`
TAILWIND IN THE WILD `div.grid > div.relative > div.2xl:before:hidden > p.text-fuchsia-500`
text-base text-gray-950 `div.grid > div.grid > div.relative > div.flex`
text-gray-950 `div.grid > div.relative > div.flex > span.inline`
text-base text-gray-950 `div.grid > div.grid > div.relative > div.flex`
text-gray-950 `div.grid > div.relative > div.flex > span.inline`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.isolate > div.relative > div.col-start-1 > img.absolute `div.isolate > div.relative > div.col-start-1 > img.absolute`
div.isolate > div.relative > div.col-start-1 > img `div.isolate > div.relative > div.col-start-1 > img`

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.inter_6a166f28-module__775SPq__variable `html.inter_6a166f28-module__775SPq__variable`

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
v4.2 `div.bg-white > div.flex > div.flex > button#headlessui-menu-button-_R_ualulb_`

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●ARIA toggle fields have accessible names

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[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 the `role=text` attribute do not have focusable descendents.

○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

○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

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

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

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
div.bg-white > div.mt-6 > div.relative > img.aspect-2/1 `div.bg-white > div.mt-6 > div.relative > img.aspect-2/1`	tailwindcss.com/_next/static/media/css-grid-4.31d79ba9.png	392 x 196 (2.00)	784 x 384 (2.04)
div.absolute > div.@container > div.relative > img.size-48 `div.absolute > div.@container > div.relative > img.size-48`	tailwindcss.com/_next/static/media/cover.f75d494c.png	190 x 192 (0.99)	384 x 384 (1.00)

●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

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.isolate > div.relative > div.col-start-1 > img.absolute `div.isolate > div.relative > div.col-start-1 > img.absolute`
div.isolate > div.relative > div.col-start-1 > img `div.isolate > div.relative > div.col-start-1 > img`

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 have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`