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.

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.16965200000000008] map[node:map[boundingRect:map[bottom:770 height:343 left:16 right:396 top:427 width:380] lhId:page-6-P nodeLabel:Bun is a fast, incrementally adoptable all-in-one JavaScript, TypeScript & JSX … path:1,HTML,1,BODY,5,DIV,1,MAIN,0,DIV,5,P selector:div#homepage > main.mx-auto > div.flex-1 > p.text-[1.3rem] snippet:<p class="text-[1.3rem] leading-normal dark:text-gray-300"> type:node] score:0.142751] map[node:map[boundingRect:map[bottom:397 height:42 left:150 right:173 top:355 width:22] lhId:page-5-SPAN nodeLabel:| path:1,HTML,1,BODY,5,DIV,1,MAIN,0,DIV,2,H1,7,SPAN selector:main.mx-auto > div.flex-1 > h1.mt-0 > span.blink snippet:<span class="blink font-light" style="visibility: visible;"> type:node] score:0.001281] map[node:map[boundingRect:map[bottom:397 height:42 left:150 right:173 top:355 width:22] lhId:page-5-SPAN nodeLabel:| path:1,HTML,1,BODY,5,DIV,1,MAIN,0,DIV,2,H1,7,SPAN selector:main.mx-auto > div.flex-1 > h1.mt-0 > span.blink snippet:<span class="blink font-light" style="visibility: visible;"> type:node] score:0.001281] map[node:map[boundingRect:map[bottom:397 height:42 left:150 right:173 top:355 width:22] lhId:page-5-SPAN nodeLabel:| path:1,HTML,1,BODY,5,DIV,1,MAIN,0,DIV,2,H1,7,SPAN selector:main.mx-auto > div.flex-1 > h1.mt-0 > span.blink snippet:<span class="blink font-light" style="visibility: visible;"> type:node] score:0.001281] map[node:map[boundingRect:map[bottom:397 height:42 left:150 right:173 top:355 width:22] lhId:page-5-SPAN nodeLabel:| path:1,HTML,1,BODY,5,DIV,1,MAIN,0,DIV,2,H1,7,SPAN selector:main.mx-auto > div.flex-1 > h1.mt-0 > span.blink snippet:<span class="blink font-light" style="visibility: visible;"> type:node] score:0.001281]]

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:248.34 source:map[column:16 line:598 type:source-location url:https://bun.sh/inkeep.min.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:155.536 source:map[type:text value:[unattributed]]] map[reflowTime:165.149 source:map[column:30 line:113585 type:source-location url:https://bun.sh/inkeep.min.js urlProvider:network]] map[reflowTime:60.298 source:map[column:24 line:120968 type:source-location url:https://bun.sh/inkeep.min.js urlProvider:network]] map[reflowTime:4.559 source:map[column:16 line:120933 type:source-location url:https://bun.sh/inkeep.min.js urlProvider:network]] map[reflowTime:3.426 source:map[column:15 line:120959 type:source-location url:https://bun.sh/inkeep.min.js urlProvider:network]] map[reflowTime:0.504 source:map[column:21 line:138851 type:source-location url:https://bun.sh/inkeep.min.js urlProvider:network]] map[reflowTime:7.431 source:map[column:12 line:98153 type:source-location url:https://bun.sh/inkeep.min.js urlProvider:network]] map[reflowTime:2.757 source:map[column:26 line:97798 type:source-location url:https://bun.sh/inkeep.min.js urlProvider:network]] map[reflowTime:5.202 source:map[column:59 line:97798 type:source-location url:https://bun.sh/inkeep.min.js urlProvider:network]]]

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
body.min-h-[100vh] > div#homepage > div.pointer-events-none > div.absolute `body.min-h-[100vh] > div#homepage > div.pointer-events-none > div.absolute`	bun.sh/hero.jpg	581.5 KiB	191.5 KiB
div.w-full > div.overflow-hidden > div.video-player-wrapper > video#claude-code-video `div.w-full > div.overflow-hidden > div.video-player-wrapper > video#claude-code-video`	bun.sh/bun-homepage-cc-boris-poster.jpg	79.2 KiB	72.3 KiB
div.w-full > div.overflow-hidden > div.video-player-wrapper > video#railway-video-section `div.w-full > div.overflow-hidden > div.video-player-wrapper > video#railway-video-section`	bun.sh/bun-homepage-railway-jake-poster.jpg	78.1 KiB	71.3 KiB
div.w-full > div.overflow-hidden > div.video-player-wrapper > video#midjourney-video `div.w-full > div.overflow-hidden > div.video-player-wrapper > video#midjourney-video`	bun.sh/bun-homepage-midjourney-cheng-poster.jpg	58.1 KiB	53.1 KiB
main.mx-auto > div.flex-1 > div.pointer-events-none > img.mt-4 `main.mx-auto > div.flex-1 > div.pointer-events-none > img.mt-4`	bun.sh/images/logo-bar.png	20.6 KiB	20.5 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV

nodeLabel: body.min-h-[100vh] > div#homepage > div.pointer-events-none > div.absolute

path: 1,HTML,1,BODY,5,DIV,0,DIV,0,DIV

selector: body.min-h-[100vh] > div#homepage > div.pointer-events-none > div.absolute

snippet: <div aria-hidden="true" class="absolute inset-0 h-full w-full bg-cover bg-fixed bg-center opacity-10" style="background-image:url(/hero.jpg)">

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
cdn.jsdelivr.net/npm/@docsearch/css@3	3.7 KiB	755 ms

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
scripts.clarity.ms/0.8.59/clarity.js	86400.0 s	26.2 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
cdn.jsdelivr.net/npm/@docsearch/js@3	604800.0 s	35.7 KiB
cdn.jsdelivr.net/npm/@docsearch/css@3	604800.0 s	3.7 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.

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.

Element	Layout shift score
Bun is a fast, incrementally adoptable all-in-one JavaScript, TypeScript & JSX … `div#homepage > main.mx-auto > div.flex-1 > p.text-[1.3rem]`	0.143
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001
\| `main.mx-auto > div.flex-1 > h1.mt-0 > span.blink`	0.001

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

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.1 s 421.4 KiB

URL	Transfer Size	Est Savings
bun.sh/inkeep.min.js	1.3 MiB	421.4 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.

Estimated savings: 1.8 s 451.3 KiB

URL	Transfer Size	Est Savings
bun.sh/inkeep.min.js	1.3 MiB	357.6 KiB
www.googletagmanager.com/gtag/js?id=G-4B43HPM4TV	155.9 KiB	64.1 KiB
cdn.jsdelivr.net/npm/@docsearch/js@3	35.5 KiB	29.6 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
bun.sh/inkeep.min.js	5.6 s	3.8 s	34 ms
bun.sh/	4.3 s	674 ms	19 ms
Unattributable	1.3 s	18 ms	0.0 ms
scripts.clarity.ms/0.8.59/clarity.js	406 ms	353 ms	8.8 ms
www.googletagmanager.com/gtag/js?id=G-4B43HPM4TV	393 ms	305 ms	50 ms
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	82 ms	41 ms	4.1 ms
cdn.jsdelivr.net/npm/@docsearch/js@3	55 ms	14 ms	13 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	5.9 s
Style & Layout	3.0 s
Other	2.6 s
Rendering	944 ms
Garbage Collection	161 ms
Parse HTML & CSS	140 ms
Script Parsing & Compilation	130 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
bun.sh/inkeep.min.js	1.3 MiB
bun.sh/bun-frontend-hmr-demo.mp4	769.3 KiB
bun.sh/hero.jpg	582.5 KiB
www.googletagmanager.com/gtag/js?id=G-4B43HPM4TV	156.2 KiB
bun.sh/bun-homepage-cc-boris-poster.jpg	79.8 KiB
bun.sh/bun-homepage-railway-jake-poster.jpg	78.6 KiB
bun.sh/	60.5 KiB
bun.sh/bun-homepage-midjourney-cheng-poster.jpg	58.6 KiB
cdn.jsdelivr.net/npm/@docsearch/js@3	35.7 KiB
bun.sh/bun-homepage-cursor-leerob-1-poster.jpg	28.1 KiB

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
CodeRabbit logo `div.flex-1 > div.pointer-events-none > div.mt-4 > img.h-6`	bun.sh/logos/coderabbit.svg
main.mx-auto > div.flex-1 > div.pointer-events-none > img.mt-4 `main.mx-auto > div.flex-1 > div.pointer-events-none > img.mt-4`	bun.sh/images/logo-bar.png
Lovable logo `div.flex-1 > div.pointer-events-none > div.mt-4 > img.h-6`	bun.sh/logos/lovable.svg
Replit logo `div.flex-1 > div.pointer-events-none > div.mt-4 > img.h-7`	bun.sh/logos/replit-wordmark.svg
Cursor logo `div.flex-1 > div.pointer-events-none > div.mt-4 > img.relative`	bun.sh/logos/cursor.svg
ai chat avatar `button.chakra-button > div.css-gmuwbf > div.css-cntv2f > img.chakra-image`	bun.sh/logo_avatar.svg

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

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 17 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 120 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

○INP breakdown

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

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mt-6 > div.overflow-hidden > div.flex > button#dVjQXKqEuFBK:copy `div.mt-6 > div.overflow-hidden > div.flex > button#dVjQXKqEuFBK:copy`
section.dark > div.overflow-hidden > div.flex > button#YPBCdturNXaQ:copy `section.dark > div.overflow-hidden > div.flex > button#YPBCdturNXaQ:copy`

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
main.mx-auto > div.flex-1 > div.pointer-events-none > img.mt-4 `main.mx-auto > div.flex-1 > div.pointer-events-none > img.mt-4`

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.flex > div.text-lg > div.flex > a `div.flex > div.text-lg > div.flex > a`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Build Docs Reference Guides Blog Discord `div.dark > header.w-screen-xl > div#default-slider-menu-menu > ul.m-auto`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Builtin Core Features Bun Node Node.js compatibility Web Standard … `body.min-h-[100vh] > section.dark > div.w-min-content > table.border-collapse`

○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

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

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

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

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

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

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

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

○Elements with visible text labels have matching accessible names.

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	Map URL
bun.sh/inkeep.min.js
cdn.jsdelivr.net/npm/@docsearch/js@3	cdn.jsdelivr.net/npm/@docsearch/index.js.map

●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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

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
main.mx-auto > div.flex-1 > div.pointer-events-none > img.mt-4 `main.mx-auto > div.flex-1 > div.pointer-events-none > img.mt-4`

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

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`