C — https://turbo.build | BeaverCheck Audit

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)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

1 link(s) with no accessible text

Accessibility › Link & Button Quality

No <main> landmark found

Accessibility › Landmark Structure

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fturbo.build)](https://beavercheck.com/results/a891f6d0-e656-4b3e-a6b6-737e57b3612a)

HTML

<a href="https://beavercheck.com/results/a891f6d0-e656-4b3e-a6b6-737e57b3612a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fturbo.build" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fturbo.build

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience.

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

3.79 s

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

7.14 s

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

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

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

7.23 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

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

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

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.

URL	Transfer Size	Duration
/_next/static/chunks/116fgwn6b2j.0.css?dpl=dpl_AhZCer3oC1...	36.5 KiB	300 ms
/_next/static/chunks/0uw7j8cbs-2_5.css?dpl=dpl_AhZCer3oC1...	945 B

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

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

URL	Time Spent
turbo.build/	795 ms
turborepo.dev/	0.0 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

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 JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 1.5 s 314.9 KiB

URL	Transfer Size	Est Savings
/_next/static/chunks/0u9800iq0j6k4.js?dpl=dpl_AhZCer3oC1s...	171.4 KiB	124.8 KiB
/_next/static/chunks/06v~4zbsc~-e0.js?dpl=dpl_AhZCer3oC1s...	116.4 KiB	93.7 KiB
/_next/static/chunks/0paypp_ypnc3m.js?dpl=dpl_AhZCer3oC1s...	44.7 KiB	44.6 KiB
/_next/static/chunks/0grf_cr1gt3-0.js?dpl=dpl_AhZCer3oC1s...	39.7 KiB	28.2 KiB
/_next/static/chunks/18bubx_dzn8wd.js?dpl=dpl_AhZCer3oC1s...	70.6 KiB	23.6 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.

URL	Total CPU Time	Script Evaluation	Script Parse
/_next/static/chunks/18bubx_dzn8wd.js?dpl=dpl_AhZCer3oC1s...	1.1 s	830 ms	55 ms
turborepo.dev/	817 ms	25 ms	33 ms
/_next/static/chunks/0zhvh253il8cl.js?dpl=dpl_AhZCer3oC1s...	722 ms	716 ms	4.9 ms
/_next/static/chunks/0grf_cr1gt3-0.js?dpl=dpl_AhZCer3oC1s...	656 ms	225 ms	15 ms
/_next/static/chunks/17mu01cho.7j6.js?dpl=dpl_AhZCer3oC1s...	356 ms	334 ms	5.5 ms
Unattributable	352 ms	17 ms	0.0 ms
/_next/static/chunks/0u9800iq0j6k4.js?dpl=dpl_AhZCer3oC1s...	163 ms	48 ms	88 ms
/_next/static/chunks/0jpsxqebiafav.js?dpl=dpl_AhZCer3oC1s...	134 ms	82 ms	32 ms
/_next/static/chunks/0laj74pxovg~a.js?dpl=dpl_AhZCer3oC1s...	117 ms	116 ms	0.8 ms
/_next/static/chunks/06v~4zbsc~-e0.js?dpl=dpl_AhZCer3oC1s...	53 ms	0.8 ms	52 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Category	Time Spent
Script Evaluation	2.5 s
Other	778 ms
Style & Layout	662 ms
Script Parsing & Compilation	494 ms
Rendering	306 ms
Parse HTML & CSS	60 ms
Garbage Collection	16 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 967 KiB

●Avoid long main-thread tasks 13 long tasks found

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

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 20 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

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
Turborepo logomark `header.sticky > div.mx-auto > div.flex > a`

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
Toggle navigation menu `header.sticky > div.mx-auto > div.ml-auto > button.inline-flex`

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

Failing Elements
html.geist_f7ab312d-module__AHFjPq__variable `html.geist_f7ab312d-module__AHFjPq__variable`

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

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

●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

●Skip links are focusable.

●Deprecated ARIA roles were not used

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

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

Source	Description
turborepo.dev/images/product-icons/repo-dark-32x32.png	`Failed to load resource: the server responded with a status of 404 ()`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

URL
/_next/static/chunks/0u9800iq0j6k4.js?dpl=dpl_AhZCer3oC1s...

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●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

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

567 ms

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

1.18 s

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

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

936 ms

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

1.45 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

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

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

URL	Transfer Size	Duration
/_next/static/chunks/116fgwn6b2j.0.css?dpl=dpl_AhZCer3oC1...	36.6 KiB	80 ms
/_next/static/chunks/0uw7j8cbs-2_5.css?dpl=dpl_AhZCer3oC1...	1005 B

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

URL	Time Spent
turbo.build/	217 ms
turborepo.dev/	0.0 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

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: 150 ms 315.4 KiB

URL	Transfer Size	Est Savings
/_next/static/chunks/0u9800iq0j6k4.js?dpl=dpl_AhZCer3oC1s...	171.4 KiB	125.2 KiB
/_next/static/chunks/06v~4zbsc~-e0.js?dpl=dpl_AhZCer3oC1s...	116.4 KiB	93.7 KiB
/_next/static/chunks/0paypp_ypnc3m.js?dpl=dpl_AhZCer3oC1s...	44.7 KiB	44.6 KiB
/_next/static/chunks/0grf_cr1gt3-0.js?dpl=dpl_AhZCer3oC1s...	39.7 KiB	28.3 KiB
/_next/static/chunks/18bubx_dzn8wd.js?dpl=dpl_AhZCer3oC1s...	70.6 KiB	23.6 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

●Time to Interactive 1.5 s

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 968 KiB

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.3 s

●Avoid long main-thread tasks 3 long tasks found

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

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 30 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

Accessibility

Names and labels

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

Failing Elements
div.flex > div.flex > div.flex > button.inline-flex `div.flex > div.flex > div.flex > button.inline-flex`
div.flex > div.flex > div.flex > button.inline-flex `div.flex > div.flex > div.flex > button.inline-flex`
div.flex > div.flex > div.flex > button.inline-flex `div.flex > div.flex > div.flex > button.inline-flex`

Failing Elements
Turborepo logomark `header.sticky > div.mx-auto > div.flex > a`

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

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

Failing Elements
html.geist_f7ab312d-module__AHFjPq__variable `html.geist_f7ab312d-module__AHFjPq__variable`

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

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

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

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

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

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

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

Source	Description
turborepo.dev/images/product-icons/repo-dark-32x32.png	`Failed to load resource: the server responded with a status of 404 ()`

URL
/_next/static/chunks/0u9800iq0j6k4.js?dpl=dpl_AhZCer3oC1s...

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://turbo.build

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best practices

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best practices

Best Practices

General

SEO

Keyboard Shortcuts