Lighthouse Desktop

· 0 checks — Desktop 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.

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.

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:344.817 source:map[column:1408 line:2 type:source-location url:https://vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1-65qcxzqctbe.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:329.241 source:map[type:text value:[unattributed]]] map[reflowTime:167.761 source:map[column:23675 line:15 type:source-location url:https://vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3mm19j3ia9zba.js urlProvider:network]] map[reflowTime:149.876 source:map[column:83284 line:1 type:source-location url:https://vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2g0iixaa64x0_.js urlProvider:network]] map[reflowTime:27.18 source:map[column:5068 line:1 type:source-location url:https://vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0yul-944xrh9z.js urlProvider:network]] map[reflowTime:140.422 source:map[column:5411 line:5 type:source-location url:https://vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1l-4u1_f4ddv9.js urlProvider:network]]]

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
/vc-ap-vercel-marketing/_next/static/immutable/chunks/0iz...	21.5 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/085...	51.4 KiB	80 ms
/vc-ap-vercel-marketing/_next/static/immutable/chunks/2za...	1.5 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/3tv...	1.3 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/0oo...	4.2 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/2og...	1.0 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/3qr...	2.3 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/2wx...	22.0 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/1wd...	598 B
/vc-ap-vercel-marketing/_next/static/immutable/chunks/0xo...	6.6 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/1uw...	653 B
/vc-ap-vercel-marketing/_next/static/immutable/chunks/23y...	12.0 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/0k5...	20.6 KiB

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: 523 ms

URL	Time Spent
vercel.app/	208 ms
vercel.com/	237 ms
vercel.app/	77 ms
vercel.com/	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.

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 rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 110 ms 103.7 KiB

URL	Transfer Size	Est Savings
/vc-ap-vercel-marketing/_next/static/immutable/chunks/085...	51.2 KiB	48.6 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/2wx...	21.9 KiB	20.0 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/0iz...	21.3 KiB	19.0 KiB
/vc-ap-vercel-marketing/_next/static/immutable/chunks/0k5...	20.3 KiB	16.0 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: 290 ms 1.8 MiB

URL	Transfer Size	Est Savings
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2v8ocn096msqz.js	416.0 KiB	415.1 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0nbpg8r2gvzy6.js	312.6 KiB	312.4 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/29k4sdsukttbk.js	175.5 KiB	175.4 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2qhhacxgmf2tp.js	131.6 KiB	131.4 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/429dyqb5th9wr.js	98.8 KiB	98.1 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0urlyd8z5tw0q.js	110.4 KiB	77.0 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1xwg-6kkipjgj.js	98.1 KiB	68.1 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1z9x4h01yl33f.js	50.9 KiB	50.5 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/235f_4o6yktb1.js	50.8 KiB	50.4 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3e7u3u-t7m47p.js	46.4 KiB	46.0 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/20s2sg17ja02k.js	44.7 KiB	44.3 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0cuved4_1243a.js	42.6 KiB	42.3 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0p4kaafh2wtb5.js	47.2 KiB	39.3 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/13atrcwey96d2.js	36.5 KiB	30.4 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1f8o-hndgzm-2.js	47.7 KiB	28.7 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1nj6mvy5zl9j2.js	36.2 KiB	27.0 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2-s84n78n6gfg.js	26.9 KiB	26.7 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/13iwodg_oya6l.js	26.8 KiB	26.7 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/44h9p3yjpqrcq.js	26.6 KiB	26.4 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3mzjbivu6r-l6.js	27.9 KiB	25.7 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/15gxb8eyghk83.js	26.3 KiB	25.7 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3wg0inht0c92f.js	24.4 KiB	24.2 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/01rjajv5hfmpc.js	23.8 KiB	23.5 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0_-hcfe9kjhp-.js	21.0 KiB	20.8 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/3i10da-jzrqb8.js	20.5 KiB	20.2 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
vercel.com/	1.8 s	28 ms	30 ms
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1-65qcxzqctbe.js	1.5 s	1.1 s	5.8 ms
Unattributable	426 ms	15 ms	0.0 ms
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2e0m6jqy7ljly.js	396 ms	223 ms	6.4 ms
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0fp_d96x8-js3.js	156 ms	14 ms	1.3 ms
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1l-4u1_f4ddv9.js	141 ms	0.4 ms	0.6 ms
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1f8o-hndgzm-2.js	71 ms	67 ms	3.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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Style & Layout	1.6 s
Script Evaluation	1.5 s
Other	1.2 s
Script Parsing & Compilation	361 ms
Rendering	155 ms
Parse HTML & CSS	103 ms
Garbage Collection	69 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
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2v8ocn096msqz.js	417.8 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0nbpg8r2gvzy6.js	312.8 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/29k4sdsukttbk.js	175.8 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/2qhhacxgmf2tp.js	131.8 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/0urlyd8z5tw0q.js	110.7 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1xwg-6kkipjgj.js	101.8 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/429dyqb5th9wr.js	99.1 KiB
vercel.com/	91.7 KiB
vercel.com/blog?_rsc=1w9ql	67.8 KiB
vercel.com/vc-ap-vercel-marketing/_next/static/immutable/chunks/1-65qcxzqctbe.js	64.3 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

●Optimize DOM size

●Font display

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 2 user timings

●Avoid long main-thread tasks 13 long tasks found

●Avoid non-composited animations 2 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 40 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 0 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
AI Cloud AI Gateway One endpoint, all your models Sandbox Isolated, safe cod… `div > ul.navigation-menu-module__AENi4G__list > li > div#radix-_r_7_-content-features`
Company Customers Trusted by the best teams Blog The latest posts and change… `div > ul.navigation-menu-module__AENi4G__list > li > div#radix-_r_7_-content-resources`
Use Cases AI Apps Deploy at the speed of AI Composable Commerce Power storef… `div > ul.navigation-menu-module__AENi4G__list > li > div#radix-_r_7_-content-solutions`
Sign Up `div.flex > div#header-content > div.morphing-button-link-module__KniueW__morphing > a.button-module__QyrFCa__base`

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
customer.domain.com project.domain.com jane.domain.com joe.domain.com `div.grid-module__4pDFEa__block > div.flex > div.w-full > div.flex`

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
'openai/gpt-5.4' `pre.relative > code.whitespace-pre-wrap > span.animate > span.px-1`
30.0% `div.flex > div.flex > div.flex > p.text-right`
9.6% `div.flex > div.flex > div.flex > p.text-right`
8.5% `div.flex > div.flex > div.flex > p.text-right`
6.2% `div.flex > div.flex > div.flex > p.text-right`
5.3% `div.flex > div.flex > div.flex > p.text-right`
4.6% `div.flex > div.flex > div.flex > p.text-right`
4.6% `div.flex > div.flex > div.flex > p.text-right`
3.6% `div.flex > div.flex > div.flex > p.text-right`
2.9% `div.flex > div.flex > div.flex > p.text-right`
10 `div.flex > div.flex > div.flex > p.font-mono`
2.9% `div.flex > div.flex > div.flex > p.text-right`
LOADING STATUS… `div.footer-module__ESbTrq__statusRow > a.link-module__Q1NRQq__link > div.status-indicator-module__razUwq__content > p.text-copy-14`

These are opportunities to improve the legibility of your content.

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
Your product, delivered. `div.grid-module__4pDFEa__gridSystem > section.grid-module__4pDFEa__grid > div.grid-module__4pDFEa__block > h3.text-heading-20`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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#header-wrapper > header.header-module__6nzVrW__header > div.flex > a#menu-button-_R_1ab5tj9abqpfivbH1_ `div#header-wrapper > header.header-module__6nzVrW__header > div.flex > a#menu-button-_R_1ab5tj9abqpfivbH1_`
div.grid-module__4pDFEa__block > div.flex > header.p-6 > a.button-module__QyrFCa__base `div.grid-module__4pDFEa__block > div.flex > header.p-6 > a.button-module__QyrFCa__base`
div.grid-module__4pDFEa__block > div.flex > header.p-6 > a.button-module__QyrFCa__base `div.grid-module__4pDFEa__block > div.flex > header.p-6 > a.button-module__QyrFCa__base`
div.grid-module__4pDFEa__block > div.flex > header.p-6 > a.button-module__QyrFCa__base `div.grid-module__4pDFEa__block > div.flex > header.p-6 > a.button-module__QyrFCa__base`
div.grid-module__4pDFEa__block > div.flex > header.p-6 > a.button-module__QyrFCa__base `div.grid-module__4pDFEa__block > div.flex > header.p-6 > a.button-module__QyrFCa__base`
div.grid-module__4pDFEa__block > div.flex > header.p-6 > a.button-module__QyrFCa__base `div.grid-module__4pDFEa__block > div.flex > header.p-6 > a.button-module__QyrFCa__base`

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
Vercel logo `nav > div.grid > div > ul.list-none`

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

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

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

●Image elements have `[alt]` attributes

●Form elements have associated labels

●ARIA attributes are used as specified for the element's role

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

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

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

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
vercel.com/api/jwt	`Failed to load resource: the server responded with a status of 403 ()`

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.

●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 issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
vercel.com/fluid	Learn more

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 are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`