Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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.

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

Performance issues directly impact user engagement and conversion rates.

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.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
beavercheck.com/favicons/build-tech.ai.png	604800.0 s	5.4 KiB
beavercheck.com/favicons/beavercheck.com.png	604800.0 s	4.8 KiB
beavercheck.com/favicons/icetrayweedclub.com.png	604800.0 s	3.9 KiB
beavercheck.com/favicons/uniqlo.com.png	604800.0 s	1.9 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
https://build-tech.ai favicon `div.max-w-2xl > div.space-y-2 > a.flex > img.w-5`	beavercheck.com/favicons/build-tech.ai.png	5.2 KiB	5.2 KiB
https://beavercheck.com favicon `div.max-w-2xl > div.space-y-2 > a.flex > img.w-5`	beavercheck.com/favicons/beavercheck.com.png	4.6 KiB	4.6 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
beavercheck.com/static/css/output.css?v=9d79544	18.5 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 0.6 s

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 210 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.5 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 200 ms

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

●Avoid large layout shifts 2 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 page `section#top > div.max-w-3xl > h1.text-4xl > span.text-amber-500`
CHECKS `div.max-w-3xl > div.grid > div.rounded-2xl > div.mt-1`
ANALYSIS TABS `div.max-w-3xl > div.grid > div.rounded-2xl > div.mt-1`
SCAN `div.max-w-3xl > div.grid > div.rounded-2xl > div.mt-1`
Advanced options `div.max-w-3xl > form.max-w-md > div.mt-3 > button.flex`
· 2h ago `div.bc-ticker > div.bc-ticker-track > a.inline-flex > span.font-mono`
· 9h ago `div.bc-ticker > div.bc-ticker-track > a.inline-flex > span.font-mono`
· 1d ago `div.bc-ticker > div.bc-ticker-track > a.inline-flex > span.font-mono`
· 1d ago `div.bc-ticker > div.bc-ticker-track > a.inline-flex > span.font-mono`
· 1d ago `div.bc-ticker > div.bc-ticker-track > a.inline-flex > span.font-mono`
· 2h ago `div.bc-ticker > div.bc-ticker-track > a.inline-flex > span.font-mono`
· 9h ago `div.bc-ticker > div.bc-ticker-track > a.inline-flex > span.font-mono`
· 1d ago `div.bc-ticker > div.bc-ticker-track > a.inline-flex > span.font-mono`
· 1d ago `div.bc-ticker > div.bc-ticker-track > a.inline-flex > span.font-mono`
· 1d ago `div.bc-ticker > div.bc-ticker-track > a.inline-flex > span.font-mono`
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 28, 2026 18:01 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Apr 28, 2026 11:00 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Apr 27, 2026 17:13 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Apr 27, 2026 08:14 `div.space-y-2 > a.flex > div.flex-1 > p.text-xs`
Apr 27, 2026 00:01 `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=9d79544 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`