Skip to content
Audit Complete

Results for https://zed.dev

Visit site
Spain Spain · Madrid Completed: Apr 7, 2026 20:40 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 80 / 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

12 image-only link(s) without alt text

Accessibility › Link & Button Quality
2

41 button(s) with no accessible text

Accessibility › Link & Button Quality
3

9 control(s) without accessible label

Accessibility › Form Accessibility
4

156 HTTP requests — consider bundling or reducing

Performance › Page Weight Budget
5

Cookie '__cf_bm' has no SameSite attribute

Security › Cookie Security
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fzed.dev)](https://beavercheck.com/results/ea9f4a69-ced9-fcec-0800-c1d4286eeb26)
<a href="https://beavercheck.com/results/ea9f4a69-ced9-fcec-0800-c1d4286eeb26"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fzed.dev" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fzed.dev

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.

27
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
86
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.
92
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.

4.08 s

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

14.78 s

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

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

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

175.56 s

Detailed Report

Audit breakdown by category with detailed findings.

27

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.

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:203.853 source:map[column:84059 line:1 type:source-location url:https://zed.dev/_next/static/chunks/1929-38b078550affd7fb.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:76.308 source:map[column:2750 line:0 type:source-location url:https://zed.dev/_next/static/chunks/3589-5a52e63828192df1.js urlProvider:network]] map[reflowTime:74.907 source:map[column:25604 line:0 type:source-location url:https://zed.dev/_next/static/chunks/4587-73a1472f469140c9.js urlProvider:network]] map[reflowTime:52.638 source:map[column:9312 line:0 type:source-location url:https://zed.dev/_next/static/chunks/7725-58431a4787f9111a.js urlProvider:network]] map[reflowTime:91.591 source:map[column:6881 line:11 type:source-location url:https://zed.dev/_next/static/chunks/7725-58431a4787f9111a.js urlProvider:network]] map[reflowTime:26.503 source:map[column:18942 line:29 type:source-location url:https://zed.dev/_next/static/chunks/9619-b9f5b871350ea0ae.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.

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

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.

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
div.relative > div.size-full > div.group > img.aspect-video div.relative > div.size-full > div.group > img.aspect-video
zed.dev/_next/image?url=%2Fimg%2Fwindows%2Fwindows-home.webp&w=750&q=7516.5 KiB13.4 KiB
body.__variable_845651 > div.pointer-events-none body.__variable_845651 > div.pointer-events-none
zed.dev/_next/static/media/noise.f156f495.webp20.5 KiB9.9 KiB
Avatar div.flex > div.flex > button#base-ui-:R1rbeipucv9akq: > img.size-4
github.com/identicons/zed.png6.0 KiB6.0 KiB

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

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

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

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

Estimated savings: 330 ms 131.8 KiB

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
Other152.9 s
Script Evaluation18.5 s
Style & Layout3.6 s
Rendering2.6 s
Script Parsing & Compilation522 ms
Garbage Collection313 ms
Parse HTML & CSS274 ms

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

Layout shift culprits
Document request latency
Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 12 animated elements found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 310 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 110 ms
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid large layout shifts
86

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

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

Failing Elements
body.__variable_845651 > div.default-border-color > div.p-3 > button.group body.__variable_845651 > div.default-border-color > div.p-3 > button.group
div.size-full > div.tab-bar-height > div.flex > button.select-none div.size-full > div.tab-bar-height > div.flex > button.select-none
div.shrink > div > div.pr-1.5 > button.relative div.shrink > div > div.pr-1.5 > button.relative
div.relative > div > div.pr-1.5 > button.relative div.relative > div > div.pr-1.5 > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div.relative > div > div.pr-1.5 > button.relative div.relative > div > div.pr-1.5 > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div.shrink > div > div.pr-1.5 > button.relative div.shrink > div > div.pr-1.5 > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div.size-full > div > div.p-1 > button.select-none div.size-full > div > div.p-1 > button.select-none
div > div.p-1 > div.w-full > button.select-none div > div.p-1 > div.w-full > button.select-none
div.p-1 > div.w-full > div.flex > button.select-none div.p-1 > div.w-full > div.flex > button.select-none
div.size-full > div > div.p-1.5 > button.select-none div.size-full > div > div.p-1.5 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.pl-2 > div.h-8.5 > div.flex > button.select-none div.pl-2 > div.h-8.5 > div.flex > button.select-none
div.pl-2 > div.h-8.5 > div.flex > button.select-none div.pl-2 > div.h-8.5 > div.flex > button.select-none
div.pl-2 > div.h-8.5 > div.flex > button.select-none div.pl-2 > div.h-8.5 > div.flex > button.select-none
div.pl-2 > div.h-8.5 > div.flex > button.select-none div.pl-2 > div.h-8.5 > div.flex > button.select-none
div.relative > div.tab-bar-height > div.px-1 > button.select-none div.relative > div.tab-bar-height > div.px-1 > button.select-none
div.relative > div.tab-bar-height > div.px-1 > button.select-none div.relative > div.tab-bar-height > div.px-1 > button.select-none
div.relative > div.tab-bar-height > div.px-1 > button.select-none div.relative > div.tab-bar-height > div.px-1 > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Failing Elements
div > div.pr-1.5 > button.relative > input.[all:unset] div > div.pr-1.5 > button.relative > input.[all:unset]
div > div.pr-1.5 > button.relative > input.[all:unset] div > div.pr-1.5 > button.relative > input.[all:unset]
div.relative > div.relative > button.relative > input.[all:unset] div.relative > div.relative > button.relative > input.[all:unset]
div > div.pr-1.5 > button.relative > input.[all:unset] div > div.pr-1.5 > button.relative > input.[all:unset]
div.relative > div.relative > button.relative > input.[all:unset] div.relative > div.relative > button.relative > input.[all:unset]
div.relative > div.relative > button.relative > input.[all:unset] div.relative > div.relative > button.relative > input.[all:unset]
div > div.pr-1.5 > button.relative > input.[all:unset] div > div.pr-1.5 > button.relative > input.[all:unset]
div.relative > div.relative > button.relative > input.[all:unset] div.relative > div.relative > button.relative > input.[all:unset]
div.relative > div.relative > button.relative > input.[all:unset] div.relative > div.relative > button.relative > input.[all:unset]

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
Nathan Sobo's GitHub profile div.relative > div.mt-8 > div.-ml-1 > a.group
Antonio Scandurra's GitHub profile div.relative > div.mt-8 > div.-ml-1 > a.group

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
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 are distinguishable without relying on color.
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
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Elements with visible text labels have matching accessible names.
`[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
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
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.
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 401 ()

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.

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
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
92

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.

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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

52
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
80
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.
92
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.

594 ms

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

1.80 s

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

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

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

38.21 s

Detailed Report

Audit breakdown by category with detailed findings.

52

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.

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:180.298 source:map[column:84059 line:1 type:source-location url:https://zed.dev/_next/static/chunks/1929-38b078550affd7fb.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:89.042 source:map[type:text value:[unattributed]]] map[reflowTime:62.272 source:map[column:2750 line:0 type:source-location url:https://zed.dev/_next/static/chunks/3589-5a52e63828192df1.js urlProvider:network]] map[reflowTime:74.37 source:map[column:25604 line:0 type:source-location url:https://zed.dev/_next/static/chunks/4587-73a1472f469140c9.js urlProvider:network]] map[reflowTime:43.656 source:map[column:9312 line:0 type:source-location url:https://zed.dev/_next/static/chunks/7725-58431a4787f9111a.js urlProvider:network]] map[reflowTime:91.567 source:map[column:6881 line:11 type:source-location url:https://zed.dev/_next/static/chunks/7725-58431a4787f9111a.js urlProvider:network]] map[reflowTime:28.746 source:map[column:18942 line:29 type:source-location url:https://zed.dev/_next/static/chunks/9619-b9f5b871350ea0ae.js urlProvider:network]] map[reflowTime:32.716 source:map[column:63799 line:0 type:source-location url:https://zed.dev/_next/static/chunks/7938-06cb79a891b5035e.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.

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

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
body.__variable_845651 > div.pointer-events-none body.__variable_845651 > div.pointer-events-none
zed.dev/_next/static/media/noise.f156f495.webp20.5 KiB9.9 KiB
Avatar div.flex > div.flex > button#base-ui-:R1rbeipucv9akq: > img.size-4
github.com/identicons/zed.png6.0 KiB6.0 KiB

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.

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

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

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

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

Estimated savings: 50 ms 131.8 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.

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
Other42.1 s
Script Evaluation1.6 s
Style & Layout662 ms
Rendering242 ms
Script Parsing & Compilation120 ms
Garbage Collection89 ms
Parse HTML & CSS70 ms

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

Layout shift culprits
Document request latency
Optimize DOM size
Font display
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 12 animated elements found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 40 ms
Server Backend Latencies 400 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 570 ms
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid large layout shifts
80

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Failing Elements
Product Resources Extensions Docs Pricing header.sticky > nav.w-full > div.flex > ul.hidden
P Sign up S Download D div.relative > header.sticky > nav.w-full > ul.ml-auto

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.

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
body.__variable_845651 > div.default-border-color > div.p-3 > button.group body.__variable_845651 > div.default-border-color > div.p-3 > button.group
div.size-full > div.tab-bar-height > div.flex > button.select-none div.size-full > div.tab-bar-height > div.flex > button.select-none
div.shrink > div > div.pr-1.5 > button.relative div.shrink > div > div.pr-1.5 > button.relative
div.relative > div > div.pr-1.5 > button.relative div.relative > div > div.pr-1.5 > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div.relative > div > div.pr-1.5 > button.relative div.relative > div > div.pr-1.5 > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div.shrink > div > div.pr-1.5 > button.relative div.shrink > div > div.pr-1.5 > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div.size-full > div > div.p-1 > button.select-none div.size-full > div > div.p-1 > button.select-none
div > div.p-1 > div.w-full > button.select-none div > div.p-1 > div.w-full > button.select-none
div.p-1 > div.w-full > div.flex > button.select-none div.p-1 > div.w-full > div.flex > button.select-none
div.size-full > div > div.p-1.5 > button.select-none div.size-full > div > div.p-1.5 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.pl-2 > div.h-8.5 > div.flex > button.select-none div.pl-2 > div.h-8.5 > div.flex > button.select-none
div.pl-2 > div.h-8.5 > div.flex > button.select-none div.pl-2 > div.h-8.5 > div.flex > button.select-none
div.pl-2 > div.h-8.5 > div.flex > button.select-none div.pl-2 > div.h-8.5 > div.flex > button.select-none
div.pl-2 > div.h-8.5 > div.flex > button.select-none div.pl-2 > div.h-8.5 > div.flex > button.select-none
div.relative > div.tab-bar-height > div.px-1 > button.select-none div.relative > div.tab-bar-height > div.px-1 > button.select-none
div.relative > div.tab-bar-height > div.px-1 > button.select-none div.relative > div.tab-bar-height > div.px-1 > button.select-none
div.relative > div.tab-bar-height > div.px-1 > button.select-none div.relative > div.tab-bar-height > div.px-1 > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Failing Elements
div > div.pr-1.5 > button.relative > input.[all:unset] div > div.pr-1.5 > button.relative > input.[all:unset]
div > div.pr-1.5 > button.relative > input.[all:unset] div > div.pr-1.5 > button.relative > input.[all:unset]
div.relative > div.relative > button.relative > input.[all:unset] div.relative > div.relative > button.relative > input.[all:unset]
div > div.pr-1.5 > button.relative > input.[all:unset] div > div.pr-1.5 > button.relative > input.[all:unset]
div.relative > div.relative > button.relative > input.[all:unset] div.relative > div.relative > button.relative > input.[all:unset]
div.relative > div.relative > button.relative > input.[all:unset] div.relative > div.relative > button.relative > input.[all:unset]
div > div.pr-1.5 > button.relative > input.[all:unset] div > div.pr-1.5 > button.relative > input.[all:unset]
div.relative > div.relative > button.relative > input.[all:unset] div.relative > div.relative > button.relative > input.[all:unset]
div.relative > div.relative > button.relative > input.[all:unset] div.relative > div.relative > button.relative > input.[all:unset]

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.

Contrast

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

Failing Elements
import code.flex > span.group/line > span > span.leading-5
as code.flex > span.group/line > span > span.leading-5
from code.flex > span.group/line > span > span.leading-5
import code.flex > span.group/line > span > span.leading-5
from code.flex > span.group/line > span > span.leading-5
interface code.flex > span.group/line > span > span.leading-5
id code.flex > span.group/line > span > span.leading-5
title code.flex > span.group/line > span > span.leading-5
10 code.flex > span.group/line > span.pl-1 > span.w-[4ch]
11 code.flex > span.group/line > span.pl-1 > span.w-[4ch]
attendees code.flex > span.group/line > span > span.leading-5
12 code.flex > span.group/line > span.pl-1 > span.w-[4ch]
snacksProvided code.flex > span.group/line > span > span.leading-5
13 code.flex > span.group/line > span.pl-1 > span.w-[4ch]
actuallyStartsOnTime span.group/line > span > button#base-ui-:R3agddr5jeipucv9akq: > span.leading-5
Type 'string' is not assignable to type 'number'. pre > code.flex > span.group/line > span.relative
14 code.flex > span.group/line > span.pl-1 > span.w-[4ch]
15 code.flex > span.group/line > span.pl-1 > span.w-[4ch]
16 code.flex > span.group/line > span.pl-1 > span.w-[4ch]
type code.flex > span.group/line > span > span.leading-5
17 code.flex > span.group/line > span.pl-1 > span.w-[4ch]
18 code.flex > span.group/line > span.pl-1 > span.w-[4ch]
function code.flex > span.group/line > span > span.leading-5
19 code.flex > span.group/line > span.pl-1 > span.w-[4ch]
return code.flex > span.group/line > span > span.leading-5
length code.flex > span.group/line > span > span.leading-5
length code.flex > span.group/line > span > span.leading-5
20 code.flex > span.group/line > span.pl-1 > span.w-[4ch]
21 code.flex > span.group/line > span.pl-1 > span.w-[4ch]

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
div.shrink > div > div.pr-1.5 > button.relative div.shrink > div > div.pr-1.5 > button.relative
div.relative > div > div.pr-1.5 > button.relative div.relative > div > div.pr-1.5 > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div.relative > div > div.pr-1.5 > button.relative div.relative > div > div.pr-1.5 > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div.shrink > div > div.pr-1.5 > button.relative div.shrink > div > div.pr-1.5 > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div > div.relative > div.relative > button.relative div > div.relative > div.relative > button.relative
div.size-full > div > div.p-1 > button.select-none div.size-full > div > div.p-1 > button.select-none
div.p-1 > div.w-full > div.flex > button.select-none div.p-1 > div.w-full > div.flex > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none div.flex-1 > div.tab-bar-height > div.px-1 > button.select-none
div.pl-2 > div.h-8.5 > div.flex > button.select-none div.pl-2 > div.h-8.5 > div.flex > button.select-none
div.pl-2 > div.h-8.5 > div.flex > button.select-none div.pl-2 > div.h-8.5 > div.flex > button.select-none
div.pl-2 > div.h-8.5 > div.flex > button.select-none div.pl-2 > div.h-8.5 > div.flex > button.select-none
div.pl-2 > div.h-8.5 > div.flex > button.select-none div.pl-2 > div.h-8.5 > div.flex > button.select-none
div.relative > div.tab-bar-height > div.px-1 > button.select-none div.relative > div.tab-bar-height > div.px-1 > button.select-none
div.relative > div.tab-bar-height > div.px-1 > button.select-none div.relative > div.tab-bar-height > div.px-1 > button.select-none
div.relative > div.tab-bar-height > div.px-1 > button.select-none div.relative > div.tab-bar-height > div.px-1 > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
div#theme-preview-shell > div.flex > div.flex > button.select-none div#theme-preview-shell > div.flex > div.flex > button.select-none
Learn More div.grid > div#content_container > button#base-ui-:Rbempucv9akq: > a.fv-style
Learn More div.grid > div#content_container > button#base-ui-:Rleopucv9akq: > a.fv-style
Nathan Sobo's GitHub profile div.relative > div.mt-8 > div.-ml-1 > a.group
Antonio Scandurra's GitHub profile div.relative > div.mt-8 > div.-ml-1 > a.group

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
Watch Demo div.relative > div.isolate > div.z-50 > button#base-ui-:rs:
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-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
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
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
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
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
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.
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 401 ()

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.

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
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
92

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.

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`

Send Feedback