C — https://docusaurus.io | BeaverCheck Audit

Site Health

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

HSTS header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

2 image-only link(s) without alt text

Accessibility › Link & Button Quality

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fdocusaurus.io)](https://beavercheck.com/results/c2cf3f55-18ab-4a9f-bbdd-7dd802dc774a)

HTML

<a href="https://beavercheck.com/results/c2cf3f55-18ab-4a9f-bbdd-7dd802dc774a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdocusaurus.io" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fdocusaurus.io

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience.

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

1.59 s

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

4.09 s

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

749 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.68 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.

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

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:107.18 source:map[type:text value:[unattributed]]]]

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

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

Request	Cache TTL	Transfer Size
i.ytimg.com/vi_webp/_An9EsKPhp0/maxresdefault.webp	7200.0 s	31.9 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
api.github.com/repos/facebook/docusaurus?callback=callback	60.0 s	3.0 KiB

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

	URL	Resource Size	Est Savings
Mark Erikson `div.card > div.card__header > div.avatar > img.avatar__photo`	unavatar.io/x/acemarke?fallback=https://github.com/markerikson.png	23.6 KiB	22.6 KiB
Supabase `div.card > div.card__header > div.avatar > img.avatar__photo`	unavatar.io/x/supabase?fallback=https://github.com/supabase.png	5.6 KiB	5.4 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.

URL	Transfer Size	Duration
docusaurus.io/assets/css/styles.5a210472.css	32.1 KiB	802 ms
docusaurus.io/katex/katex.min.css	3.6 KiB	173 ms

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

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

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: 160 ms 112.1 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-E5CR2Q1NRE	154.0 KiB	65.1 KiB
docusaurus.io/assets/js/main.59adb867.js	237.2 KiB	46.9 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
docusaurus.io/assets/js/main.59adb867.js	1.3 s	994 ms	174 ms
docusaurus.io/	999 ms	36 ms	4.0 ms
Unattributable	721 ms	11 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-E5CR2Q1NRE	487 ms	349 ms	134 ms
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	51 ms	35 ms	5.6 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	1.5 s
Other	929 ms
Style & Layout	641 ms
Script Parsing & Compilation	340 ms
Rendering	150 ms
Garbage Collection	99 ms
Parse HTML & CSS	82 ms

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

	URL
Meta Open Source Logo `div.footer__bottom > div.margin-bottom--sm > a.footerLogoLink_CiM_ > img.footer__logo`	docusaurus.io/img/meta_opensource_logo_negative.svg

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

●Avoids enormous network payloads Total size was 712 KiB

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 8 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

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

○INP breakdown

○LCP request discovery

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

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
Powered by MDX `div.container > div.row > div.col > h3.featureHeading_TLGJ`

These are opportunities to improve keyboard navigation in your application.

○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

●Links have a discernible name

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

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

○Skip links are focusable.

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

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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

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

100

Best Practices

General

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

URL
docusaurus.io/assets/js/main.59adb867.js

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

100

SEO

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●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

100

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

450 ms

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

1.08 s

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

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

657 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.57 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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

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

Request	Cache TTL	Transfer Size
i.ytimg.com/vi_webp/_An9EsKPhp0/maxresdefault.webp	7200.0 s	31.9 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
api.github.com/repos/facebook/docusaurus?callback=callback	60.0 s	3.0 KiB

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:119.097 source:map[type:text value:[unattributed]]]]

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

title: Preconnected origins

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

title: Preconnect candidates

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

	URL	Resource Size	Est Savings
Paul Armstrong `div.card > div.card__header > div.avatar > img.avatar__photo`	unavatar.io/x/paularmstrong?fallback=https://github.com/paularmstrong.png	35.9 KiB	35.5 KiB
Debbie O'Brien `div.card > div.card__header > div.avatar > img.avatar__photo`	unavatar.io/x/debs_obrien?fallback=https://github.com/debs-obrien.png	35.2 KiB	34.8 KiB
Maël `div.card > div.card__header > div.avatar > img.avatar__photo`	unavatar.io/x/arcanis?fallback=https://github.com/arcanis.png	35.1 KiB	34.8 KiB
Max Lynch `div.card > div.card__header > div.avatar > img.avatar__photo`	unavatar.io/x/maxlynch?fallback=https://github.com/mlynch.png	24.6 KiB	24.3 KiB
Mark Erikson `div.card > div.card__header > div.avatar > img.avatar__photo`	unavatar.io/x/acemarke?fallback=https://github.com/markerikson.png	23.6 KiB	23.3 KiB
swyx `div.card > div.card__header > div.avatar > img.avatar__photo`	unavatar.io/x/swyx?fallback=https://github.com/sw-yx.png	23.4 KiB	23.0 KiB
Kent C. Dodds `div.card > div.card__header > div.avatar > img.avatar__photo`	unavatar.io/x/kentcdodds?fallback=https://github.com/kentcdodds.png	21.9 KiB	21.6 KiB
Dr.Electron `div.card > div.card__header > div.avatar > img.avatar__photo`	unavatar.io/x/Dr_Electron?fallback=https://github.com/Dr-Electron.png	18.6 KiB	18.3 KiB
Supabase `div.card > div.card__header > div.avatar > img.avatar__photo`	unavatar.io/x/supabase?fallback=https://github.com/supabase.png	5.6 KiB	5.5 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.

URL	Transfer Size	Duration
docusaurus.io/assets/css/styles.5a210472.css	32.1 KiB	188 ms
docusaurus.io/katex/katex.min.css	3.6 KiB	53 ms

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

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

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 112.9 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-E5CR2Q1NRE	154.0 KiB	65.1 KiB
docusaurus.io/assets/js/main.59adb867.js	237.2 KiB	47.8 KiB

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

	URL
Meta Open Source Logo `div.footer__bottom > div.margin-bottom--sm > a.footerLogoLink_CiM_ > img.footer__logo`	docusaurus.io/img/meta_opensource_logo_negative.svg

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

●Time to Interactive 1.6 s

●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

●Avoids enormous network payloads Total size was 1,182 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.1 s

●Avoid long main-thread tasks 4 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

Accessibility

Navigation

Failing Elements
Powered by MDX `div.container > div.row > div.col > h3.featureHeading_TLGJ`

These are opportunities to improve keyboard navigation in your application.

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
Search Ctrl K `div.navbar__inner > div.theme-layout-navbar-right > div.navbarSearchContainer_dDCC > button.DocSearch`

○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

●`<frame>` or `<iframe>` elements have a title

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

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

●Links have a discernible name

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

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

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

100

Best Practices

General

URL
docusaurus.io/assets/js/main.59adb867.js

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://docusaurus.io

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Navigation

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Navigation

Best Practices

General

SEO

Keyboard Shortcuts