C — https://vitejs.dev | BeaverCheck Audit

Site Health

Score: 73 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

5 button(s) with no accessible text

Accessibility › Link & Button Quality

No <main> landmark found

Accessibility › Landmark Structure

101 HTTP requests — consider bundling or reducing

Performance › Page Weight Budget

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fvitejs.dev)](https://beavercheck.com/results/e2a95b60-9df6-4c6d-961d-bd80bce72b19)

HTML

<a href="https://beavercheck.com/results/e2a95b60-9df6-4c6d-961d-bd80bce72b19"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fvitejs.dev" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fvitejs.dev

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.24 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

11.37 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

1.68 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.001

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

3.89 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

11.58 s

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.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

URL	Est Savings
vite.dev/assets/KHTekaMono-Regular.CiZ9ZkmZ.woff2	25 ms
vite.dev/assets/APK-Protocol-Medium.C7Mq9oGh.woff2	25 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
Footer background `footer.bg-primary > section.wrapper > div.relative > img.absolute`	vite.dev/assets/footer-background.BIgtbvhx.jpg	351.9 KiB	316.0 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.jpg	198.6 KiB	178.1 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-.jpg	181.0 KiB	160.4 KiB
SSR Support `div > section.wrapper > div.p-5 > img.w-full`	vite.dev/assets/vite-ssr-support.DvdwoLgL.png	122.0 KiB	113.8 KiB
Brought to you by VoidZero `div.wrapper > div.flex > a.flex > img.h-44`	vite.dev/assets/vite-by-voidzero.D7bblMgo.png	78.7 KiB	70.2 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.png	63.5 KiB	55.0 KiB
div.flex > div.flex > a.button > ::before `div.flex > div.flex > a.button > ::before`	vite.dev/assets/primary-button-background.CHnwvuqy.jpg	55.1 KiB	50.4 KiB
div.flex > div.flex > a.button > ::before `div.flex > div.flex > a.button > ::before`	vite.dev/assets/primary-button-background.Bjk7gn3x.jpg	45.1 KiB	41.5 KiB
SerpApi `div.border-t > div.grid > a.spsr-link > img.spsr-logo`	sponsors.vuejs.org/images/serpapi.png	13.0 KiB	11.2 KiB
Greptile `div.border-t > div.grid > a.spsr-link > img.spsr-logo`	sponsors.vuejs.org/images/greptile.png	7.1 KiB	6.1 KiB
CodeRabbit `div.border-t > div.grid > a.spsr-link > img.spsr-logo`	sponsors.vuejs.org/images/coderabbit_.png	7.0 KiB	5.8 KiB
Storyblok `div.border-t > div.grid > a.spsr-link > img.spsr-logo`	sponsors.vuejs.org/images/storyblok.png	6.0 KiB	4.3 KiB

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.

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

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
vite.dev/assets/vite-ssr-support.DvdwoLgL.png	604800.0 s	122.2 KiB
vite.dev/assets/vite-by-voidzero.D7bblMgo.png	604800.0 s	78.9 KiB
vite.dev/assets/vite-featurepanel-2-terminal.ChpAU6sR.png	604800.0 s	63.7 KiB
vite.dev/assets/vite-typed-api.B7gyuuaS.svg	604800.0 s	22.9 KiB
vite.dev/assets/vite-featurepanel-4-terminal.BRnxuy_J.svg	604800.0 s	16.1 KiB
vite.dev/assets/vite-featurepanel-1-terminal.CQVUoUSU.svg	604800.0 s	15.2 KiB
sponsors.vuejs.org/images/catalyst.svg	86400.0 s	2.5 KiB
sponsors.vuejs.org/images/follower24.svg	86400.0 s	2.4 KiB
sponsors.vuejs.org/images/handsontable.svg	86400.0 s	2.1 KiB
sponsors.vuejs.org/images/convex.svg?v2	86400.0 s	1.8 KiB
sponsors.vuejs.org/images/sanity.svg	86400.0 s	1.6 KiB
sponsors.vuejs.org/images/railway.svg	86400.0 s	1.5 KiB
sponsors.vuejs.org/images/nx.svg	86400.0 s	1.1 KiB
sponsors.vuejs.org/images/mux.svg	86400.0 s	1.0 KiB
sponsors.vuejs.org/images/mojam.svg	86400.0 s	948 B
vite.dev/trusted-by/linear.svg	604800.0 s	2.3 KiB
vite.dev/assets/vite-dark.D2ACe7TL.svg	604800.0 s	2.1 KiB
vite.dev/assets/vite-light.t8GCa_VF.svg	604800.0 s	2.0 KiB
vite.dev/trusted-by/shopify.svg	604800.0 s	1.9 KiB
vite.dev/trusted-by/clickup.svg	604800.0 s	1.7 KiB
vite.dev/trusted-by/openai.svg	604800.0 s	1.4 KiB
vite.dev/trusted-by/wiz.svg	604800.0 s	1.1 KiB
vite.dev/trusted-by/stripe.svg	604800.0 s	1.0 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.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 818 ms

URL	Time Spent
vitejs.dev/	818 ms
vite.dev/	0.0 ms

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.

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 reduce Javascript execution time.

URL	Total CPU Time	Script Evaluation	Script Parse
vite.dev/assets/index.md.DHMIRVbV.lean.js	7.8 s	5.4 s	1.4 ms
Unattributable	1.8 s	679 ms	0.0 ms
vite.dev/	1.5 s	54 ms	21 ms
vite.dev/assets/chunks/client.CPtIGuYZ.js	200 ms	84 ms	0.4 ms
vite.dev/assets/style.BaItNzON.css	72 ms	0.0 ms	0.0 ms
vite.dev/assets/chunks/FooterNav.Gx_p0gCh.js	57 ms	40 ms	0.4 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

Category	Time Spent
Script Evaluation	6.2 s
Other	3.6 s
Style & Layout	978 ms
Rendering	660 ms
Parse HTML & CSS	109 ms
Garbage Collection	53 ms
Script Parsing & Compilation	31 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
shopify `div.scroll-content > div.flex > div.logo-container > img.max-w-full`	vite.dev/trusted-by/shopify.svg
shopify `div.scroll-content > div.flex > div.logo-container > 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.scroll-content > div.flex > div.logo-container > img.max-w-full`	vite.dev/trusted-by/wiz.svg
wiz `div.scroll-content > div.flex > div.logo-container > img.max-w-full`	vite.dev/trusted-by/wiz.svg
linear `div.scroll-content > div.flex > div.logo-container > img.max-w-full`	vite.dev/trusted-by/linear.svg
linear `div.scroll-content > div.flex > div.logo-container > img.max-w-full`	vite.dev/trusted-by/linear.svg
stripe `div.scroll-content > div.flex > div.logo-container > img.max-w-full`	vite.dev/trusted-by/stripe.svg
stripe `div.scroll-content > div.flex > div.logo-container > img.max-w-full`	vite.dev/trusted-by/stripe.svg
openai `div.scroll-content > div.flex > div.logo-container > img.max-w-full`	vite.dev/trusted-by/openai.svg
openai `div.scroll-content > div.flex > div.logo-container > img.max-w-full`	vite.dev/trusted-by/openai.svg
clickup `div.scroll-content > div.flex > div.logo-container > img.max-w-full`	vite.dev/trusted-by/clickup.svg
clickup `div.scroll-content > div.flex > div.logo-container > img.max-w-full`	vite.dev/trusted-by/clickup.svg

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●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,055 KiB

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 10 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

○LCP request discovery

○User Timing marks and measures

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.

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.

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.

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

●Touch targets have sufficient size and spacing.

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

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

○No element has a `[tabindex]` value greater than 0

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

○Elements with visible text labels have matching accessible names.

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

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

811 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.23 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

206 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.06 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.72 s

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.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
vite.dev/assets/vite-ssr-support.DvdwoLgL.png	604800.0 s	122.3 KiB
vite.dev/assets/vite-by-voidzero.D7bblMgo.png	604800.0 s	78.9 KiB
vite.dev/assets/vite-featurepanel-2-terminal.ChpAU6sR.png	604800.0 s	63.6 KiB
vite.dev/assets/vite-typed-api.B7gyuuaS.svg	604800.0 s	22.9 KiB
vite.dev/assets/vite-ci.rfkpyz0p.svg	604800.0 s	17.8 KiB
vite.dev/assets/vite-featurepanel-4-terminal.BRnxuy_J.svg	604800.0 s	16.1 KiB
vite.dev/assets/vite-featurepanel-1-terminal.CQVUoUSU.svg	604800.0 s	15.2 KiB
sponsors.vuejs.org/images/follower24.svg	86400.0 s	2.5 KiB
sponsors.vuejs.org/images/catalyst.svg	86400.0 s	2.5 KiB
sponsors.vuejs.org/images/handsontable.svg	86400.0 s	2.2 KiB
sponsors.vuejs.org/images/convex.svg?v2	86400.0 s	1.8 KiB
sponsors.vuejs.org/images/sanity.svg	86400.0 s	1.6 KiB
sponsors.vuejs.org/images/railway.svg	86400.0 s	1.4 KiB
sponsors.vuejs.org/images/nx.svg	86400.0 s	1.1 KiB
sponsors.vuejs.org/images/mux.svg	86400.0 s	1.0 KiB
sponsors.vuejs.org/images/mojam.svg	86400.0 s	950 B
vite.dev/trusted-by/linear.svg	604800.0 s	2.3 KiB
vite.dev/assets/vite-dark.D2ACe7TL.svg	604800.0 s	2.0 KiB
vite.dev/assets/vite-light.t8GCa_VF.svg	604800.0 s	2.0 KiB
vite.dev/trusted-by/shopify.svg	604800.0 s	1.9 KiB
vite.dev/trusted-by/clickup.svg	604800.0 s	1.7 KiB
vite.dev/trusted-by/openai.svg	604800.0 s	1.4 KiB
vite.dev/trusted-by/wiz.svg	604800.0 s	1.1 KiB
vite.dev/trusted-by/stripe.svg	604800.0 s	1.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.

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.

URL	Est Savings
vite.dev/assets/KHTekaMono-Regular.CiZ9ZkmZ.woff2	80 ms
vite.dev/assets/APK-Protocol-Medium.C7Mq9oGh.woff2	60 ms
vite.dev/assets/KHTekaMono-Medium.CxAWoJPq.woff2	35 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.

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

	URL	Resource Size	Est 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.jpg	351.9 KiB	320.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.jpg	198.6 KiB	146.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-.jpg	181.0 KiB	128.4 KiB
SSR Support `div > section.wrapper > div.p-5 > img.w-full`	vite.dev/assets/vite-ssr-support.DvdwoLgL.png	122.0 KiB	100.3 KiB
div.flex > div.flex > a.button > ::before `div.flex > div.flex > a.button > ::before`	vite.dev/assets/primary-button-background.CHnwvuqy.jpg	55.1 KiB	50.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.png	63.5 KiB	49.6 KiB
div.flex > div.flex > a.button > ::before `div.flex > div.flex > a.button > ::before`	vite.dev/assets/primary-button-background.Bjk7gn3x.jpg	45.1 KiB	41.5 KiB

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

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.

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.

Estimated savings: 231 ms

URL	Time 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.

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

Category	Time Spent
Script Evaluation	1.3 s
Other	725 ms
Style & Layout	314 ms
Rendering	142 ms
Parse HTML & CSS	26 ms
Script Parsing & Compilation	15 ms
Garbage Collection	15 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	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

Accessibility

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.

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

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.

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

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

○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

Results for https://vitejs.dev

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Navigation

Best practices

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Navigation

Best practices

Best Practices

General

SEO

Keyboard Shortcuts