C — https://unpkg.com | BeaverCheck Audit

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

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

HSTS sites average 74

At average

Better than 61% of HSTS sites See full HSTS benchmark →

HTTP/3 sites average 74

At average

Better than 66% of HTTP/3 sites See full HTTP/3 benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

4 link(s) with no accessible text

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

Accessibility › Link & Button Quality

4 third-party resources (92% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

Cross-Origin-Embedder-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

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%2Funpkg.com)](https://beavercheck.com/results/e968646f-188f-496b-9025-afd4bd74d465)

HTML

<a href="https://beavercheck.com/results/e968646f-188f-496b-9025-afd4bd74d465"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Funpkg.com" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. The 1 performance issue below shapes how fast users perceive your page. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

1 accessibility issue excludes users who rely on assistive technology.

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

Conversion Barriers

4 warning

4 barrier(s) likely increasing bounce by ~9%.

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (2)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$500 investment → $0.08/month returns + USD 157,500 risk avoided

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

Investment

$500

5h · 5 findings

Monthly returns

$0.08 /mo

~$0.94 / year

Bandwidth savings $0.08

Regulatory risk avoided

USD 157,500

if kept compliant

ADA Title III USD 150,000
CCPA/CPRA USD 7,500

$150 — in quick wins — start here for the fastest payback

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

$500

5.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$150 3 fixes in ~90 minutes

Start here for the best return on investment

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

$13,125 / month at risk

~$157,501 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA

No privacy policy link detected
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no cookie policy found
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no privacy policy found
CCPA/CPRA: USD 2,500 – USD 7,500

+2 more

Bandwidth Waste

$0.08 /mo

981.0 MB/mo × 0.080 USD/GB

Optimize transfer: save ~98 KB per page load
Saves $0.08/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 3 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!

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.

Performance

Accessibility

100

Best Practices

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.

826 ms

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

826 ms

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

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

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

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

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
www.google-analytics.com/analytics.js	7200.0 s	20.9 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
unpkg.com/_assets/code-light-B2LHUSJR.css	462 B
unpkg.com/_assets/styles-LG6W3OHZ.css	6.7 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 129.6 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-79NC4YX69Q&cx=c&gtm=4e64f0	157.0 KiB	66.6 KiB
www.googletagmanager.com/gtag/js?id=UA-140352188-1	116.4 KiB	63.0 KiB

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

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 319 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.4 s

●Minimizes main-thread work 0.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 30 ms

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

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

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

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
"my-package" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
"./dist/index.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"https://unpkg.com/my-package" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"my-package" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
"./dist/exp.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"https://unpkg.com/my-package/exp" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
fetch `section#overview > div.mt-8 > div.p-4 > span.hljs-built_in`
"my-package" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
"./dist/index.unpkg.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
// This works `section#overview > div.mt-8 > div.p-4 > span.hljs-comment`
"./dist/index.unpkg.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
// This works, too `section#overview > div.mt-8 > div.p-4 > span.hljs-comment`
"./dist/index.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
<!doctype html> `section#nobuild-apps > div.mt-8 > div.p-4 > span.hljs-meta`
html `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"en" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
head `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
meta `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"UTF-8" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"importmap" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
"imports" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"preact" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"https://unpkg.com/preact@10.25.4/dist/preact.module.js" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"preact/hooks" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"https://unpkg.com/preact@10.25.4/hooks/dist/hooks.module.js" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"htm" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"https://unpkg.com/htm@3.1.1/dist/htm.module.js" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
head `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
body `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"module" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
"preact" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"preact/hooks" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"htm" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
bind `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-title`
App `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-title`
useState `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-title`
div `span.language-javascript > span.language-xml > span.hljs-tag > span.hljs-name`
${count} `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-subst`
button `span.language-javascript > span.language-xml > span.hljs-tag > span.hljs-name`
${() => setCount(count + 1)} `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-subst`
button `span.language-javascript > span.language-xml > span.hljs-tag > span.hljs-name`
div `span.language-javascript > span.language-xml > span.hljs-tag > span.hljs-name`
render `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-title`
${App} `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-subst`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
body `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
html `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"react-router" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"7.3.0" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"/dist/" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
path `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-selector-tag`
"/dist/development/dom-export.js" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"text/javascript" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"sha256-z5j8OHOsGkvfGAjBtW8sbj+M68LLmgLTSjDHk4A5uYA=" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
path `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-selector-tag`
"/dist/production/dom-export.js" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"text/javascript" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"sha256-Gh8wMHW9MO5IMaBq7fOc7szDMRemnO/7Qr8kTK4ebgY=" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`

These are opportunities to improve the legibility of your content.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > section#nobuild-apps > h2.mt-16 > a.outline-none `div > section#nobuild-apps > h2.mt-16 > a.outline-none`
div > section#metadata-api > h2.mt-16 > a.outline-none `div > section#metadata-api > h2.mt-16 > a.outline-none`
div > section#cache-performance > h2.mt-16 > a.outline-none `div > section#cache-performance > h2.mt-16 > a.outline-none`
div > section#about > h2.mt-16 > a.outline-none `div > section#about > h2.mt-16 > a.outline-none`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○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-hidden="true"]` is not present on the document `<body>`

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

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●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

●Document has a main landmark.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

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

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

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

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

○Buttons have an accessible name

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

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

○Form elements have associated labels

○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

●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

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
1	`module.exports = createMiddleware`	`Syntax not understood`
3	`var readFileSync = require('fs').readFileSync`	`Syntax not understood`
4	`, crypto = require('crypto')`	`Syntax not understood`
6	`function createMiddleware(path, options) {`	`Syntax not understood`
8	`// Defaults`	`Syntax not understood`
9	`options = options \|\| {}`	`Syntax not understood`
11	`if (!path) throw new Error('No path provided for robots.txt file')`	`Syntax not understood`
13	`var maxAge = options.maxAge \|\| 86400000`	`Syntax not understood`
14	`, txt = readFileSync(path)`	`Syntax not understood`
15	`, headers =`	`Syntax not understood`
16	`{ 'Content-Type': 'text/plain'`	`Unknown directive`
17	`, 'Content-Length': txt.length`	`Unknown directive`
18	`, 'ETag': '"' + crypto.createHash('md5').update(txt).digest('hex') + '"'`	`Unknown directive`
19	`, 'Cache-Control': 'public, max-age=' + (maxAge / 1000)`	`Unknown directive`
20	`}`	`Syntax not understood`
22	`return function middleware(req, res, next) {`	`Syntax not understood`
23	`if ('/robots.txt' !== req.url) return next()`	`Syntax not understood`
24	`res.writeHead(200, headers)`	`Syntax not understood`
25	`res.end(txt)`	`Syntax not understood`
26	`}`	`Syntax not understood`
28	`}`	`Syntax not understood`

To appear in search results, crawlers need access to your app.

○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

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

100

Performance

Accessibility

100

Best Practices

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.

387 ms

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

414 ms

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

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

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

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

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.

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	Duration
unpkg.com/_assets/code-light-B2LHUSJR.css	609 B	134 ms
unpkg.com/_assets/styles-LG6W3OHZ.css	6.8 KiB	54 ms

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
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB

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

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.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 129.2 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-79NC4YX69Q&cx=c&gtm=4e64f0h1&bs=ctrl2	157.0 KiB	66.2 KiB
www.googletagmanager.com/gtag/js?id=UA-140352188-1	116.4 KiB	63.0 KiB

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

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.0 s

●Max Potential First Input Delay 50 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 320 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.2 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 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 30 ms

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○Avoid large layout shifts

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
"my-package" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
"./dist/index.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"https://unpkg.com/my-package" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"my-package" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
"./dist/exp.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"https://unpkg.com/my-package/exp" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
fetch `section#overview > div.mt-8 > div.p-4 > span.hljs-built_in`
"my-package" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
"./dist/index.unpkg.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
// This works `section#overview > div.mt-8 > div.p-4 > span.hljs-comment`
"./dist/index.unpkg.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
// This works, too `section#overview > div.mt-8 > div.p-4 > span.hljs-comment`
"./dist/index.js" `section#overview > div.mt-8 > div.p-4 > span.hljs-string`
<!doctype html> `section#nobuild-apps > div.mt-8 > div.p-4 > span.hljs-meta`
html `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"en" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
head `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
meta `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"UTF-8" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"importmap" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
"imports" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"preact" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"https://unpkg.com/preact@10.25.4/dist/preact.module.js" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"preact/hooks" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"https://unpkg.com/preact@10.25.4/hooks/dist/hooks.module.js" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"htm" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"https://unpkg.com/htm@3.1.1/dist/htm.module.js" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
head `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
body `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"module" `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-string`
"preact" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"preact/hooks" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
"htm" `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-string`
bind `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-title`
App `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-title`
useState `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-title`
div `span.language-javascript > span.language-xml > span.hljs-tag > span.hljs-name`
${count} `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-subst`
button `span.language-javascript > span.language-xml > span.hljs-tag > span.hljs-name`
${() => setCount(count + 1)} `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-subst`
button `span.language-javascript > span.language-xml > span.hljs-tag > span.hljs-name`
div `span.language-javascript > span.language-xml > span.hljs-tag > span.hljs-name`
render `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-title`
${App} `div.mt-8 > div.p-4 > span.language-javascript > span.hljs-subst`
script `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
body `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
html `div.mt-8 > div.p-4 > span.hljs-tag > span.hljs-name`
"react-router" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"7.3.0" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"/dist/" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
path `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-selector-tag`
"/dist/development/dom-export.js" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"text/javascript" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"sha256-z5j8OHOsGkvfGAjBtW8sbj+M68LLmgLTSjDHk4A5uYA=" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
path `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-selector-tag`
"/dist/production/dom-export.js" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"text/javascript" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`
"sha256-Gh8wMHW9MO5IMaBq7fOc7szDMRemnO/7Qr8kTK4ebgY=" `section#metadata-api > div.mt-8 > div.p-4 > span.hljs-string`

These are opportunities to improve the legibility of your content.

Names and labels

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > section#nobuild-apps > h2.mt-16 > a.outline-none `div > section#nobuild-apps > h2.mt-16 > a.outline-none`
div > section#metadata-api > h2.mt-16 > a.outline-none `div > section#metadata-api > h2.mt-16 > a.outline-none`
div > section#cache-performance > h2.mt-16 > a.outline-none `div > section#cache-performance > h2.mt-16 > a.outline-none`
div > section#about > h2.mt-16 > a.outline-none `div > section#about > h2.mt-16 > a.outline-none`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○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-hidden="true"]` is not present on the document `<body>`

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

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●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

●Document has a main landmark.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

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

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

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

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

○Buttons have an accessible name

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

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

○Form elements have associated labels

○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

●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

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

SEO

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
1	`module.exports = createMiddleware`	`Syntax not understood`
3	`var readFileSync = require('fs').readFileSync`	`Syntax not understood`
4	`, crypto = require('crypto')`	`Syntax not understood`
6	`function createMiddleware(path, options) {`	`Syntax not understood`
8	`// Defaults`	`Syntax not understood`
9	`options = options \|\| {}`	`Syntax not understood`
11	`if (!path) throw new Error('No path provided for robots.txt file')`	`Syntax not understood`
13	`var maxAge = options.maxAge \|\| 86400000`	`Syntax not understood`
14	`, txt = readFileSync(path)`	`Syntax not understood`
15	`, headers =`	`Syntax not understood`
16	`{ 'Content-Type': 'text/plain'`	`Unknown directive`
17	`, 'Content-Length': txt.length`	`Unknown directive`
18	`, 'ETag': '"' + crypto.createHash('md5').update(txt).digest('hex') + '"'`	`Unknown directive`
19	`, 'Cache-Control': 'public, max-age=' + (maxAge / 1000)`	`Unknown directive`
20	`}`	`Syntax not understood`
22	`return function middleware(req, res, next) {`	`Syntax not understood`
23	`if ('/robots.txt' !== req.url) return next()`	`Syntax not understood`
24	`res.writeHead(200, headers)`	`Syntax not understood`
25	`res.end(txt)`	`Syntax not understood`
26	`}`	`Syntax not understood`
28	`}`	`Syntax not understood`

To appear in search results, crawlers need access to your app.

○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

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`

Results for https://unpkg.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Trust (1)

Content (2)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

SEO

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

SEO

Crawling and Indexing

Keyboard Shortcuts