A — https://beavercheck.com/

Site Health

Score: 92 / 100 Same as last audit

Based on 8 categories, 59 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 (3)

Unattributable: 369ms CPU time

Performance › JS Execution Cost

https://beavercheck.com/: 717ms CPU time

Performance › JS Execution Cost

DNS resolution is slow (321 ms)

Infrastructure › DNS Records

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fbeavercheck.com%2F)](https://beavercheck.com/results/27109da9-b6e9-4bd5-a614-5275fa1f4427)

HTML

<a href="https://beavercheck.com/results/27109da9-b6e9-4bd5-a614-5275fa1f4427"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbeavercheck.com%2F" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Global Performance 5/5 locations ✓

UN Santa Clara

Full audit

925ms

DNS 300ms · TLS 159ms

UN New York

472ms

DNS 150ms · TLS 83ms

NL Amsterdam

38ms

DNS 7ms · TLS 11ms

SG Singapore

1228ms

DNS 572ms · TLS 167ms

BR Sao Paulo

1237ms

DNS 412ms · TLS 209ms

CDN: No CDN · Avg TTFB: 780ms · Cache: No cache headers

Recent Trends

Performance stable →

TTFB degrading ↓

930ms

FCP stable →

1.0s

LCP improving ↑

1.0s

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.

1.02 s

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

1.02 s

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

127 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.035

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.00 s

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

2.19 s

Detailed Report

Audit breakdown by category with detailed findings.

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
beavercheck.com/static/css/output.css?v=83e3419	19.7 KiB	150 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 2.2 s

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●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

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 184 KiB

●JavaScript execution time 0.4 s

●Minimizes main-thread work 1.7 s

●Avoid long main-thread tasks 5 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 150 ms

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

●Avoid large layout shifts 6 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

Accessibility

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

Contrast

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

Failing Elements
One Scan. `section#top > div.max-w-2xl > h1.text-4xl > span.text-amber-500`
Run Audit `div.max-w-2xl > form.max-w-md > button.flex > span.htmx-hide-on-request`
Advanced options `div.max-w-2xl > form.max-w-md > div.mt-3 > button.flex`
Lab + real-user speed metrics `div.bg-white > div.flex > div > p.text-xs`
SSL, headers, vulnerabilities `div.bg-white > div.flex > div > p.text-xs`
WCAG compliance + visual contrast `div.bg-white > div.flex > div > p.text-xs`
Search engine optimization `div.bg-white > div.flex > div > p.text-xs`
Quality, readability, images `div.bg-white > div.flex > div > p.text-xs`
DNS, hosting, domain intelligence `div.bg-white > div.flex > div > p.text-xs`
Full technology stack detection `div.bg-white > div.flex > div > p.text-xs`
GDPR, privacy, tracker detection `div.bg-white > div.flex > div > p.text-xs`
Uptime, protocols, transport `div.bg-white > div.flex > div > p.text-xs`
Carbon footprint & green hosting `div.bg-white > div.flex > div > p.text-xs`
Google Lighthouse raw scores `div.bg-white > div.flex > div > p.text-xs`
PageSpeed Insights `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
SecurityHeaders.com `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
SSL Labs `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
BuiltWith `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
GTmetrix `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
WAVE `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
Website Carbon `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
Apr 1, 2026 21:51 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Start Your Free Analysis `div.max-w-2xl > form.mt-8 > div.flex > button.rounded-xl`
Built with beaver-powered love for the open web. `footer.border-t > div.max-w-5xl > div.mt-8 > p.text-xs`
© 2025 BeaverCheck `footer.border-t > div.max-w-5xl > div.mt-8 > p.mt-1`

These are opportunities to improve the legibility of your content.

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

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

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

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

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

○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

○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

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / Warning	Source
SharedStorage	beavercheck.com/static/js/alpine.min.js?v=83e3419 line 4, col 16571

●Uses HTTPS

●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

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○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

100

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.

311 ms

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

311 ms

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

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.008

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

311 ms

Detailed Report

Audit breakdown by category with detailed findings.

100

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.

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
beavercheck.com/static/css/output.css?v=83e3419	19.7 KiB

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 0.3 s

●Max Potential First Input Delay 40 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 184 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.4 s

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 140 ms

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

●Avoid large layout shifts 8 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

Accessibility

Contrast

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

Failing Elements
One Scan. `section#top > div.max-w-2xl > h1.text-4xl > span.text-amber-500`
Run Audit `div.max-w-2xl > form.max-w-md > button.flex > span.htmx-hide-on-request`
Advanced options `div.max-w-2xl > form.max-w-md > div.mt-3 > button.flex`
Lab + real-user speed metrics `div.bg-white > div.flex > div > p.text-xs`
SSL, headers, vulnerabilities `div.bg-white > div.flex > div > p.text-xs`
WCAG compliance + visual contrast `div.bg-white > div.flex > div > p.text-xs`
Search engine optimization `div.bg-white > div.flex > div > p.text-xs`
Quality, readability, images `div.bg-white > div.flex > div > p.text-xs`
DNS, hosting, domain intelligence `div.bg-white > div.flex > div > p.text-xs`
Full technology stack detection `div.bg-white > div.flex > div > p.text-xs`
GDPR, privacy, tracker detection `div.bg-white > div.flex > div > p.text-xs`
Uptime, protocols, transport `div.bg-white > div.flex > div > p.text-xs`
Carbon footprint & green hosting `div.bg-white > div.flex > div > p.text-xs`
Google Lighthouse raw scores `div.bg-white > div.flex > div > p.text-xs`
PageSpeed Insights `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
SecurityHeaders.com `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
SSL Labs `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
BuiltWith `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
GTmetrix `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
WAVE `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
Website Carbon `div.max-w-3xl > div.space-y-3 > div.flex > span.text-sm`
Apr 1, 2026 21:51 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Start Your Free Analysis `div.max-w-2xl > form.mt-8 > div.flex > button.rounded-xl`
Built with beaver-powered love for the open web. `footer.border-t > div.max-w-5xl > div.mt-8 > p.text-xs`
© 2025 BeaverCheck `footer.border-t > div.max-w-5xl > div.mt-8 > p.mt-1`

These are opportunities to improve the legibility of your content.

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

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

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

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

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

○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

○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

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / Warning	Source
SharedStorage	beavercheck.com/static/js/alpine.min.js?v=83e3419 line 4, col 16571

●Uses HTTPS

●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

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○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://beavercheck.com/

Site Health

Top Priorities (3)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Accessibility

Contrast

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Accessibility

Contrast

Best Practices

General

SEO

Keyboard Shortcuts