Skip to content
https://vitejs.dev

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

90

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.

RequestCache TTLTransfer Size
vite.dev/assets/vite-ssr-support.DvdwoLgL.png604800.0 s122.3 KiB
vite.dev/assets/vite-by-voidzero.D7bblMgo.png604800.0 s78.9 KiB
vite.dev/assets/vite-featurepanel-2-terminal.ChpAU6sR.png604800.0 s63.6 KiB
vite.dev/assets/vite-typed-api.B7gyuuaS.svg604800.0 s22.9 KiB
vite.dev/assets/vite-ci.rfkpyz0p.svg604800.0 s17.8 KiB
vite.dev/assets/vite-featurepanel-4-terminal.BRnxuy_J.svg604800.0 s16.1 KiB
vite.dev/assets/vite-featurepanel-1-terminal.CQVUoUSU.svg604800.0 s15.2 KiB
sponsors.vuejs.org/images/follower24.svg86400.0 s2.5 KiB
sponsors.vuejs.org/images/catalyst.svg86400.0 s2.5 KiB
sponsors.vuejs.org/images/handsontable.svg86400.0 s2.2 KiB
sponsors.vuejs.org/images/convex.svg?v286400.0 s1.8 KiB
sponsors.vuejs.org/images/sanity.svg86400.0 s1.6 KiB
sponsors.vuejs.org/images/railway.svg86400.0 s1.4 KiB
sponsors.vuejs.org/images/nx.svg86400.0 s1.1 KiB
sponsors.vuejs.org/images/mux.svg86400.0 s1.0 KiB
sponsors.vuejs.org/images/mojam.svg86400.0 s950 B
vite.dev/trusted-by/linear.svg604800.0 s2.3 KiB
vite.dev/assets/vite-dark.D2ACe7TL.svg604800.0 s2.0 KiB
vite.dev/assets/vite-light.t8GCa_VF.svg604800.0 s2.0 KiB
vite.dev/trusted-by/shopify.svg604800.0 s1.9 KiB
vite.dev/trusted-by/clickup.svg604800.0 s1.7 KiB
vite.dev/trusted-by/openai.svg604800.0 s1.4 KiB
vite.dev/trusted-by/wiz.svg604800.0 s1.1 KiB
vite.dev/trusted-by/stripe.svg604800.0 s1.0 KiB

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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
vite.dev/assets/KHTekaMono-Regular.CiZ9ZkmZ.woff280 ms
vite.dev/assets/APK-Protocol-Medium.C7Mq9oGh.woff260 ms
vite.dev/assets/KHTekaMono-Medium.CxAWoJPq.woff235 ms

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:47.654 source:map[column:9366 line:0 type:source-location url:https://vite.dev/assets/chunks/client.CPtIGuYZ.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.

URLResource SizeEst Savings
div.marketing-layout > div.top-banner > a.group > img.absolute div.marketing-layout > div.top-banner > a.group > img.absolute
vite.dev/assets/footer-background.BIgtbvhx.jpg351.9 KiB320.3 KiB
section.wrapper > div.flex > div.relative > img.absolute section.wrapper > div.flex > div.relative > img.absolute
vite.dev/assets/vite-featurepanel-1-background.BHnDg8j4.jpg198.6 KiB146.2 KiB
section.wrapper > div.flex > div.relative > img.absolute section.wrapper > div.flex > div.relative > img.absolute
vite.dev/assets/vite-featurepanel-4-background.Bnx0RZk-.jpg181.0 KiB128.4 KiB
SSR Support div > section.wrapper > div.p-5 > img.w-full
vite.dev/assets/vite-ssr-support.DvdwoLgL.png122.0 KiB100.3 KiB
div.flex > div.flex > a.button > ::before div.flex > div.flex > a.button > ::before
vite.dev/assets/primary-button-background.CHnwvuqy.jpg55.1 KiB50.4 KiB
lightning fast hot module replacement section.wrapper > div.flex > div.flex > img.md:max-w-[80%]
vite.dev/assets/vite-featurepanel-2-terminal.ChpAU6sR.png63.5 KiB49.6 KiB
div.flex > div.flex > a.button > ::before div.flex > div.flex > a.button > ::before
vite.dev/assets/primary-button-background.Bjk7gn3x.jpg45.1 KiB41.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-IMG
nodeLabel: div.marketing-layout > div.top-banner > a.group > img.absolute
path: 1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,0,A,0,IMG
selector: div.marketing-layout > div.top-banner > a.group > img.absolute
snippet: <img src="/assets/footer-background.BIgtbvhx.jpg" alt="" aria-hidden="true" class="absolute inset-0 w-full h-full object-cover object-bottom z-0" loading="eager">

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
value: No additional origins are good candidates for preconnecting

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: 231 ms
URLTime Spent
vitejs.dev/231 ms
vite.dev/0.0 ms

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

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.

CategoryTime Spent
Script Evaluation1.3 s
Other725 ms
Style & Layout314 ms
Rendering142 ms
Parse HTML & CSS26 ms
Script Parsing & Compilation15 ms
Garbage Collection15 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
shopify div.overflow-hidden > div.flex > div.logo-container-static > img.max-w-full
vite.dev/trusted-by/shopify.svg
Brought to you by VoidZero div.wrapper > div.flex > a.flex > img.h-44
vite.dev/assets/vite-by-voidzero.D7bblMgo.png
wiz div.overflow-hidden > div.flex > div.logo-container-static > img.max-w-full
vite.dev/trusted-by/wiz.svg
linear div.overflow-hidden > div.flex > div.logo-container-static > img.max-w-full
vite.dev/trusted-by/linear.svg
stripe div.overflow-hidden > div.flex > div.logo-container-static > img.max-w-full
vite.dev/trusted-by/stripe.svg
openai div.overflow-hidden > div.flex > div.logo-container-static > img.max-w-full
vite.dev/trusted-by/openai.svg
clickup div.overflow-hidden > div.flex > div.logo-container-static > img.max-w-full
vite.dev/trusted-by/clickup.svg
Vite header.wrapper > div.flex > a.flex > img.h-4
vite.dev/assets/vite-light.t8GCa_VF.svg

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

●Time to Interactive 1.7 s
●Layout shift culprits
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 2,121 KiB
●JavaScript execution time 1.2 s
●Avoid long main-thread tasks 7 long tasks found
●Avoid non-composited animations 18 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 70 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 20 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○User Timing marks and measures
91

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.vp-doc > div.vp-code-group > div.language-bash > button.copy div.vp-doc > div.vp-code-group > div.language-bash > button.copy

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.

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
Trusted by the world's best software teams div > div > section.wrapper > h6.text-center
Instant Server Start section.wrapper > div.flex > div.p-5 > h5.text-balance
Flexible Plugin System div > section.wrapper > div.p-5 > h5.text-balance

These are opportunities to improve keyboard navigation in your application.

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 html

These items highlight common accessibility best practices.

○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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
●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.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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
○`<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
vite.dev/assets/rive.BagEuNN0.wasm
●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
○Redirects HTTP traffic to HTTPS
○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`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback