Skip to content
Audit Complete

Results for https://www.vercel.com/templates

Visit site
Singapore Singapore · Singapore Completed: Apr 6, 2026 15:09 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C76

Site Health

Score: 76 / 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)

1

Content-Security-Policy header is missing

Security › Security Headers
2

No Content-Security-Policy header found

Security › Content Security Policy
3

26 link(s) with no accessible text

Accessibility › Link & Button Quality
4

No <main> landmark found

Accessibility › Landmark Structure
5

Soft 404: server returns HTTP 200 for non-existent pages

Accessibility › 404 Error Page
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.vercel.com%2Ftemplates)](https://beavercheck.com/results/c1759d9a-59ad-43a1-afc9-71b570951cd5)
<a href="https://beavercheck.com/results/c1759d9a-59ad-43a1-afc9-71b570951cd5"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.vercel.com%2Ftemplates" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.vercel.com%2Ftemplates

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

36
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
84
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

10.11 s

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

1.82 s

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.

6.15 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.29 s

Detailed Report

Audit breakdown by category with detailed findings.

36

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:86.763 source:map[column:4933 line:73 type:source-location url:https://vercel.com/_next/static/chunks/0zys9gxbu7opo.js?dpl=dpl_D7a52sP1BY5YFBPfWdXK3AGrWRR9 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:50.568 source:map[column:25105 line:11 type:source-location url:https://vercel.com/_next/static/chunks/3rnezpgon52jr.js?dpl=dpl_D7a52sP1BY5YFBPfWdXK3AGrWRR9 urlProvider:network]] map[reflowTime:3.213 source:map[column:18044 line:11 type:source-location url:https://vercel.com/_next/static/chunks/3rnezpgon52jr.js?dpl=dpl_D7a52sP1BY5YFBPfWdXK3AGrWRR9 urlProvider:network]] map[reflowTime:0.789 source:map[column:17549 line:5 type:source-location url:https://vercel.com/_next/static/chunks/23rk8htg3kl9p.js?dpl=dpl_D7a52sP1BY5YFBPfWdXK3AGrWRR9 urlProvider:network]] map[reflowTime:36.566 source:map[column:24854 line:11 type:source-location url:https://vercel.com/_next/static/chunks/3rnezpgon52jr.js?dpl=dpl_D7a52sP1BY5YFBPfWdXK3AGrWRR9 urlProvider:network]] map[reflowTime:32.193 source:map[column:11783 line:5 type:source-location url:https://vercel.com/_next/static/chunks/23rk8htg3kl9p.js?dpl=dpl_D7a52sP1BY5YFBPfWdXK3AGrWRR9 urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:100.52 label:Time to first byte subpart:timeToFirstByte] map[duration:1429.385 label:Resource load delay subpart:resourceLoadDelay] map[duration:56.321 label:Resource load duration subpart:resourceLoadDuration] map[duration:951.42 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: Next.js Boilerplate
path: 1,HTML,1,BODY,2,DIV,12,DIV,1,DIV,3,DIV,0,DIV,1,DIV,0,DIV,0,A,1,IMG
selector: div.w-full > div.mt-20 > a.link-module__Q1NRQq__link > img.image-module__ssnYEW__intrinsic
snippet: <img data-version="v1" alt="Next.js Boilerplate" loading="lazy" width="300" height="100" decoding="async" data-nimg="1" class="image-module__ssnYEW__intrinsic absolute top-[110px] -right-10 rotate-[-5d…" style="color:transparent;box-shadow:var(--shadow-small)" srcset="/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fe5382hct74si%2F1aHob…" src="/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fe5382hct74si%2F1aHob…">

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

lhId: page-0-IMG
nodeLabel: Next.js Boilerplate
path: 1,HTML,1,BODY,2,DIV,12,DIV,1,DIV,3,DIV,0,DIV,1,DIV,0,DIV,0,A,1,IMG
selector: div.w-full > div.mt-20 > a.link-module__Q1NRQq__link > img.image-module__ssnYEW__intrinsic
snippet: <img data-version="v1" alt="Next.js Boilerplate" loading="lazy" width="300" height="100" decoding="async" data-nimg="1" class="image-module__ssnYEW__intrinsic absolute top-[110px] -right-10 rotate-[-5d…" style="color:transparent;box-shadow:var(--shadow-small)" srcset="/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fe5382hct74si%2F1aHob…" src="/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fe5382hct74si%2F1aHob…">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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

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

URLResource SizeEst Savings
Image Gallery Starter div.w-full > div.mt-20 > a.link-module__Q1NRQq__link > img.image-module__ssnYEW__intrinsic
/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fe53...39.1 KiB30.6 KiB
ISR Blog with Next.js and WordPress div.w-full > div.mt-20 > a.link-module__Q1NRQq__link > img.image-module__ssnYEW__intrinsic
/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fe53...23.6 KiB18.5 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.

Estimated savings: 753 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.

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

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.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

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

CategoryTime Spent
Script Evaluation2.8 s
Other1.0 s
Style & Layout882 ms
Script Parsing & Compilation477 ms
Parse HTML & CSS330 ms
Garbage Collection97 ms
Rendering53 ms

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
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,663 KiB
User Timing marks and measures 7 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 230 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
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
84

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Get started with Next.js and React in seconds. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
An image gallery built on Next.js and Cloudinary. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Simple, powerful and flexible markdown-powered docs site. Built with Next.js. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Deploy Hono backends using the Bun runtime. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
This template creates a voice chat using Hume AI's Empathic Voice Interface. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Starter kit for high-performance commerce with Shopify. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
An inbound lead qualification and research agent built with Next.js, AI SDK, Wo… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Examples of many Next.js App Router features. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Easily create a portfolio with Next.js and Markdown. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
An Incremental Static Regeneration Blog Example Using Next.js and WordPress div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Enterprise-grade Next.js boilerplate built with Tailwind CSS, Radix UI, TypeScr… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A statically generated blog example using Next.js and Markdown. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A blog template with Next.js 13 App Router, Contentlayer, Tailwind CSS and dark… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Use a Large Language Model to summarize customer feedback. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A Nuxt.js 3 app, bootstrapped with create-nuxt-app. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
An AI chatbot template to build your own chatbot powered by Nuxt MDC and Vercel… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
AI answer engine with Generative UI. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A personal website built with Next.js and Sanity featuring visual editing, live… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A clean Next.js + Sanity starter with visual editing, drag-and-drop page builde… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A Next.js starter chatbot using Vercel's AI SDK and implements the Retrieval-Au… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Real-time collaborative product starter kit built with Next.js and Liveblocks div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A link-in-bio SaaS built with Nuxt.js, where the data lives in the URL – no dat… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
The all-in-one subscription starter kit for high-performance SaaS applications,… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
QrGPT is an AI tool for you to generate beautiful QR codes using AI with one cl… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A SvelteKit app including nested routes, layouts, and page endpoints. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A Next.js App Router template configured with cookie-based auth using Supabase,… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-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.

Failing Elements
Next.js Boilerplate a.link-module__Q1NRQq__link > div.flex > div.flex > h3.text-heading-16

These are opportunities to improve keyboard navigation in your application.

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.

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.

Failing Elements
head > meta head > meta

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

Failing Elements
html.geist_mono_98cac566-module__bcNCwW__className html.geist_mono_98cac566-module__bcNCwW__className

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
`[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
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
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
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.
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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
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.
96

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

SourceDescription
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 404 ()
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
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

84
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
81
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

646 ms

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

1.45 s

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

268 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.09 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.

2.19 s

Detailed Report

Audit breakdown by category with detailed findings.

84

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:104.212 source:map[column:4933 line:73 type:source-location url:https://vercel.com/_next/static/chunks/0zys9gxbu7opo.js?dpl=dpl_D7a52sP1BY5YFBPfWdXK3AGrWRR9 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:48.359 source:map[type:text value:[unattributed]]] map[reflowTime:0.958 source:map[column:18494 line:1 type:source-location url:https://vercel.com/_next/static/chunks/2z13w0dnu8cfe.js?dpl=dpl_D7a52sP1BY5YFBPfWdXK3AGrWRR9 urlProvider:network]] map[reflowTime:1.621 source:map[column:5475 line:5 type:source-location url:https://vercel.com/_next/static/chunks/23jow6d422ghv.js?dpl=dpl_D7a52sP1BY5YFBPfWdXK3AGrWRR9 urlProvider:network]] map[reflowTime:103.254 source:map[column:18044 line:11 type:source-location url:https://vercel.com/_next/static/chunks/3rnezpgon52jr.js?dpl=dpl_D7a52sP1BY5YFBPfWdXK3AGrWRR9 urlProvider:network]] map[reflowTime:30.596 source:map[column:8005 line:28 type:source-location url:https://vercel.com/_next/static/chunks/1hjy0pji8y2k-.js?dpl=dpl_D7a52sP1BY5YFBPfWdXK3AGrWRR9 urlProvider:network]] map[reflowTime:0.208 source:map[column:7899 line:1 type:source-location url:https://vercel.com/_next/static/chunks/3v44cb6r3lq3z.js?dpl=dpl_D7a52sP1BY5YFBPfWdXK3AGrWRR9 urlProvider:network]]]

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

lhId: page-0-IMG
nodeLabel: Image Gallery Starter
path: 1,HTML,1,BODY,2,DIV,12,DIV,1,DIV,3,DIV,0,DIV,1,DIV,0,DIV,1,A,1,IMG
selector: div.w-full > div.mt-20 > a.link-module__Q1NRQq__link > img.image-module__ssnYEW__intrinsic
snippet: <img data-version="v1" alt="Image Gallery Starter" loading="lazy" width="300" height="100" decoding="async" data-nimg="1" class="image-module__ssnYEW__intrinsic absolute top-[110px] -right-10 rotate-[-5d…" style="color:transparent;box-shadow:var(--shadow-small)" srcset="/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fe5382hct74si%2F3Pkqi…" src="https://vercel.com/_next/image?url=https%3A%2F%2Fimages.ctfassets.net%2Fe5…">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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

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

RequestCache TTLTransfer Size
vercel.com/_stream/external/cdn.sift.com/s.js86400.0 s21.7 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

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

CategoryTime Spent
Script Evaluation1.2 s
Style & Layout733 ms
Other604 ms
Script Parsing & Compilation117 ms
Parse HTML & CSS102 ms
Garbage Collection86 ms
Rendering58 ms

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

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

Estimated savings: 202 ms
Time to Interactive 2.2 s
Max Potential First Input Delay 120 ms
Layout shift culprits
Optimize DOM size
Font display
Improve image delivery
LCP breakdown
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 2,149 KiB
User Timing marks and measures 7 user timings
JavaScript execution time 1.1 s
Avoid long main-thread tasks 12 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 230 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
INP breakdown
Avoid non-composited animations
Avoid large layout shifts
81

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.

Failing Elements
AI Cloud v0 Build applications with AI AI SDK The AI Toolkit for TypeScript … div > ul.navigation-menu-module__AENi4G__list > li > div#radix-_r_0_-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_0_-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_0_-content-solutions
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a
label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a label.checkbox-module__Em-o0q__container > span.checkbox-module__Em-o0q__text > div.flex > a

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.

Failing Elements
Get started with Next.js and React in seconds. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
An image gallery built on Next.js and Cloudinary. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A full-featured, hackable Next.js AI chatbot built by Vercel div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Simple, powerful and flexible markdown-powered docs site. Built with Next.js. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Deploy Hono backends using the Bun runtime. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Starter kit for high-performance commerce with Shopify. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
An inbound lead qualification and research agent built with Next.js, AI SDK, Wo… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Examples of many Next.js App Router features. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Easily create a portfolio with Next.js and Markdown. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
This is a Slack Agent template built with Bolt for JavaScript (TypeScript) and … div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
An Incremental Static Regeneration Blog Example Using Next.js and WordPress div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Enterprise-grade Next.js boilerplate built with Tailwind CSS, Radix UI, TypeScr… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A statically generated blog example using Next.js and Markdown. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A blog template with Next.js 13 App Router, Contentlayer, Tailwind CSS and dark… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Use a Large Language Model to summarize customer feedback. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A Nuxt.js 3 app, bootstrapped with create-nuxt-app. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
An AI chatbot template to build your own chatbot powered by Nuxt MDC and Vercel… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
AI answer engine with Generative UI. div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A personal website built with Next.js and Sanity featuring visual editing, live… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A clean Next.js + Sanity starter with visual editing, drag-and-drop page builde… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A Next.js starter chatbot using Vercel's AI SDK and implements the Retrieval-Au… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
Real-time collaborative product starter kit built with Next.js and Liveblocks div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
A link-in-bio SaaS built with Nuxt.js, where the data lives in the URL – no dat… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-14
The all-in-one subscription starter kit for high-performance SaaS applications,… div.mt-20 > a.link-module__Q1NRQq__link > div.flex > div.text-label-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.

Failing Elements
Filter Templates div.hidden > div.flex > div.flex > h4.m-0

These are opportunities to improve keyboard navigation in your application.

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.

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.

Failing Elements
head > meta head > meta

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

Failing Elements
html.geist_mono_98cac566-module__bcNCwW__className html.geist_mono_98cac566-module__bcNCwW__className

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
`[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
Elements use only permitted ARIA attributes
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
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.
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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
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.
96

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

SourceDescription
Failed to load resource: the server responded with a status of 403 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
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
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback