A — https://beavercheck.com | BeaverCheck Audit

Site Health

Score: 93 / 100 +1

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Strong security — your users are well protected.

Mostly accessible, but some users still face barriers.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Strong compliance posture across regulations.

Rich content metadata — your pages look great everywhere.

Lean and efficient — low environmental impact per visit.

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.

How the composite score is calculated

How you compare

Alpine.js sites average 83

+10 above average

Better than 72% of Alpine.js sites See full Alpine.js benchmark →

Google Search Console sites average 75

+18 above average

Better than 97% of Google Search Console sites See full Google Search Console benchmark →

Top Priorities (5)

1 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

1 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

Unattributable: 308ms CPU time

Performance issues directly impact user engagement and conversion rates.

Performance › JS Execution Cost

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

Performance issues directly impact user engagement and conversion rates.

Performance › JS Execution Cost

DNS resolution is slow (474 ms)

Infrastructure issues create a performance ceiling that no frontend optimization can overcome.

Infrastructure › DNS Records

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Nothing in this quadrant — good news.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fbeavercheck.com)](https://beavercheck.com/results/f18ef6bb-b2e5-4bb8-bdc8-d4797ffc166e)

HTML

<a href="https://beavercheck.com/results/f18ef6bb-b2e5-4bb8-bdc8-d4797ffc166e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbeavercheck.com" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

What fixing these means

Your site is in great shape. The remaining improvements are refinements rather than critical fixes. Your server takes 2343ms to respond — every other performance metric inherits that delay. Addressing the critical issues below would have the most immediate impact on your audience reach.

2 accessibility issues exclude users who rely on assistive technology.

2 performance issues — Akamai's research found 53% of mobile users abandon pages over 3s.

1 infrastructure issue creates a performance ceiling no frontend fix can overcome.

Return on Investment

€880 investment → €0.04/month returns

Payback period: > 2 years First-year ROI: -100%

Investment

€880

11h · 5 findings

Monthly returns

€0.04 /mo

~€0.51 / year

Bandwidth savings €0.04

Regulatory risk avoided

No applicable regulations in this jurisdiction

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€880

11.0 developer hours at €80/hr

Based on France rates (€80/hr)

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€0.04 / month at risk

~€0.51 / year if left unfixed

Bandwidth Waste

€0.04 /mo

577.6 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~58 KB per page load
Saves €0.04/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 2 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

Global Performance 6/6 locations ✓

SG Singapore

Full audit

2343ms

DNS 334ms · TLS 169ms

ES Madrid

2346ms

DNS 1ms · TLS 23ms

UN New York

1912ms

DNS 156ms · TLS 78ms

NL Amsterdam

3101ms

DNS 27ms · TLS 14ms

US Santa Clara

2499ms

DNS 307ms · TLS 164ms

BR Sao Paulo

3993ms

DNS 438ms · TLS 213ms

CDN: No CDN · Avg TTFB: 2699ms · Cache: max-age=60

Recent Trends

Performance stable →

100

TTFB degrading ↓

2.6s

FCP improving ↑

1.1s

LCP stable →

1.4s

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

96 -4

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.19 s

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

1.19 s

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

195 ms

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

0.002

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

3.26 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.17 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
beavercheck.com/static/css/output.css?v=71c1a9e	17.0 KiB

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 873 ms

URL	Time Spent
beavercheck.com/	973 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Time to Interactive 2.2 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

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 188 KiB

●JavaScript execution time 0.3 s

●Minimizes main-thread work 1.6 s

●Avoid long main-thread tasks 3 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 160 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Avoid large layout shifts 9 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 13, 2026 09:24 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Apr 12, 2026 21:45 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Apr 12, 2026 14:13 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Apr 12, 2026 14:10 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Apr 12, 2026 14:10 `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`
© 2026 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	beavercheck.com/static/js/alpine.min.js?v=71c1a9e 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

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.

425 ms

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

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

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

627 ms

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:3922.552 label:Time to first byte subpart:timeToFirstByte] map[duration:316.335 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-H1

nodeLabel: 100+ Checks. 11 Analysis Tabs. One Scan.

path: 1,HTML,1,BODY,2,MAIN,1,SECTION,0,DIV,2,H1

selector: main#main-content > section#top > div.max-w-2xl > h1.text-4xl

snippet: <h1 class="text-4xl font-bold tracking-tight text-beaver-900 dark:text-gray-100 sm:te…" data-testid="hero-heading">

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
beavercheck.com/static/css/output.css?v=71c1a9e	17.0 KiB

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 3.2 s

URL	Time Spent
beavercheck.com/	3.3 s

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 0.6 s

●Max Potential First Input Delay 50 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 188 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.4 s

●Avoid long main-thread tasks 1 long task found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 150 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Avoid large layout shifts 7 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 13, 2026 09:24 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Apr 12, 2026 21:45 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Apr 12, 2026 14:13 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Apr 12, 2026 14:10 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Apr 12, 2026 14:10 `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`
© 2026 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	beavercheck.com/static/js/alpine.min.js?v=71c1a9e 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

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Bandwidth Waste

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