C — https://www.bandcamp.com

Site Health

Score: 71 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

Page weighs 8.6 MB (4.4 MB transferred)

Performance › Page Weight Budget

1 control(s) without accessible label

Accessibility › Form Accessibility

1 image(s) missing alt attribute

Accessibility › Alt Text Quality

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.bandcamp.com)](https://beavercheck.com/results/eec37385-7bc8-3a5b-df58-facb197996ec)

HTML

<a href="https://beavercheck.com/results/eec37385-7bc8-3a5b-df58-facb197996ec"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.bandcamp.com" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

100

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience.

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

5.16 s

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

7.57 s

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

2.51 s

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

0.005

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

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

21.69 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

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

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

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

	URL	Resource Size	Est Savings
T-Shirts `div.page-wrapper > ul > li > a.image-tile`	/vite/homepage/client/v1/en/assets/merch-card_tshirt_2x-B...	142.3 KiB	102.5 KiB
div.small-items > div.featured-editorial-item > a.g-button > img.g-image `div.small-items > div.featured-editorial-item > a.g-button > img.g-image`	f4.bcbits.com/img/0044155556_170.jpg	72.4 KiB	52.3 KiB
div.small-items > div.featured-editorial-item > a.g-button > img.g-image `div.small-items > div.featured-editorial-item > a.g-button > img.g-image`	f4.bcbits.com/img/0043670458_170.jpg	38.1 KiB	20.4 KiB
div.small-items > div.featured-editorial-item > a.g-button > img.g-image `div.small-items > div.featured-editorial-item > a.g-button > img.g-image`	f4.bcbits.com/img/0043987082_170.jpg	29.0 KiB	15.6 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-4-IMG

nodeLabel: div.container > div.featured-editorial-item > a.g-button > img.g-image

path: 1,HTML,1,BODY,5,DIV,0,DIV,5,MAIN,2,SECTION,0,DIV,1,DIV,0,DIV,0,A,2,IMG

selector: div.container > div.featured-editorial-item > a.g-button > img.g-image

snippet: <img data-v-35b10209="" data-v-b4b67806="" class="g-image" src="https://f4.bcbits.com/img/0043986172_170.jpg" alt="">

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

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

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

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

URL	Transfer Size	Duration
s4.bcbits.com/vite/homepage/client/v1/en/assets/HomepageApp-DOcMBKq6.css	48.2 KiB	301 ms
/client-bundle/1/ArtistsLabelsPages_1/salesfeed_css-5828a...	2.5 KiB	757 ms

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

Request	Cache TTL	Transfer Size
js.stripe.com/basil/stripe.js	120.0 s	219.8 KiB
m.stripe.network/out-4.5.45.js	300.0 s	16.5 KiB
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	5.0 ms

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 981 ms

URL	Time Spent
www.bandcamp.com/	981 ms
bandcamp.com/	0.0 ms

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.

Estimated savings: 773 ms

URL	Time Spent
bandcamp.com/	873 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

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

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 300 ms 42.5 KiB

URL	Transfer Size	Est Savings
s4.bcbits.com/vite/homepage/client/v1/en/assets/HomepageApp-DOcMBKq6.css	48.0 KiB	42.5 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 600 ms 567.9 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	362.6 KiB	161.6 KiB
js.stripe.com/basil/stripe.js	219.4 KiB	159.9 KiB
/vite/homepage/client/v1/en/entrypoints/HomepageApp.vue_e...	274.7 KiB	116.5 KiB
www.googletagmanager.com/gtag/js?id=GT-WV86TPST&cx=c&gtm=4e6460	175.4 KiB	68.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-TKFS52TF	123.2 KiB	61.9 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

URL	Total CPU Time	Script Evaluation	Script Parse
/vite/homepage/client/v1/en/entrypoints/HomepageApp.vue_e...	3.4 s	3.2 s	5.1 ms
Unattributable	1.8 s	749 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=GT-WV86TPST&cx=c&gtm=4e6460	564 ms	483 ms	73 ms
bandcamp.com/	463 ms	8.6 ms	0.7 ms
js.stripe.com/basil/stripe.js	446 ms	199 ms	245 ms
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	408 ms	214 ms	121 ms
/client-bundle/1/ArtistsLabelsPages_1/salesfeed_js-3f3609...	197 ms	71 ms	1.2 ms
www.googletagmanager.com/gtm.js?id=GTM-TKFS52TF	194 ms	146 ms	46 ms
s4.bcbits.com/vite/homepage/client/v1/en/assets/HomepageApp-DOcMBKq6.css	69 ms	0.0 ms	0.0 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Category	Time Spent
Script Evaluation	5.1 s
Other	1.4 s
Script Parsing & Compilation	506 ms
Style & Layout	361 ms
Garbage Collection	148 ms
Parse HTML & CSS	119 ms
Rendering	69 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
/vite/homepage/client/v1/en/assets/merch-card_cassette_2x...	381.1 KiB
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	363.2 KiB
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	363.2 KiB
/vite/homepage/client/v1/en/entrypoints/HomepageApp.vue_e...	296.7 KiB
s4.bcbits.com/vite/homepage/client/v1/en/assets/merch-card_vinyl_2x-T-u5UH70.jpg	264.7 KiB
js.stripe.com/basil/stripe.js	219.8 KiB
s4.bcbits.com/vite/homepage/client/v1/en/assets/merch-card_cd_2x-DFrFD3A1.jpg	216.8 KiB
www.googletagmanager.com/gtag/js?id=GT-WV86TPST&cx=c&gtm=4e6460	175.4 KiB
/vite/homepage/client/v1/en/assets/merch-card_tshirt_2x-B...	142.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-TKFS52TF	123.6 KiB

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 8 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 1 animated element found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 190 ms

●Server Backend Latencies 250 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 1 layout shift found

○INP breakdown

100

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.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●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

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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

100

SEO

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

100

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

1.47 s

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

2.44 s

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

337 ms

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

0.070

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

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

4.50 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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

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

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

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

items: [map[reflowTime:10.916 source:map[column:7551 line:1 type:source-location url:https://s4.bcbits.com/client-bundle/1/ArtistsLabelsPages_1/salesfeed_js-3f36094f0eedfc37fb09195635bfd1c5.js urlProvider:network]]]

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

items: [map[reflowTime:23.688 source:map[type:text value:[unattributed]]] map[reflowTime:10.916 source:map[column:5468 line:0 type:source-location url:https://s4.bcbits.com/client-bundle/1/ArtistsLabelsPages_1/salesfeed_js-3f36094f0eedfc37fb09195635bfd1c5.js urlProvider:network]]]

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

	URL	Resource Size	Est Savings
div.container > div.featured-editorial-item > a.g-button > img.g-image `div.container > div.featured-editorial-item > a.g-button > img.g-image`	f4.bcbits.com/img/0043986172_0	421.6 KiB	343.1 KiB
Cassettes `div.page-wrapper > ul > li > a.image-tile`	/vite/homepage/client/v1/en/assets/merch-card_cassette_2x...	380.7 KiB	341.0 KiB
Vinyl `div.page-wrapper > ul > li > a.image-tile`	s4.bcbits.com/vite/homepage/client/v1/en/assets/merch-card_vinyl_2x-T-u5UH70.jpg	264.3 KiB	224.6 KiB
CDs `div.page-wrapper > ul > li > a.image-tile`	s4.bcbits.com/vite/homepage/client/v1/en/assets/merch-card_cd_2x-DFrFD3A1.jpg	216.4 KiB	176.6 KiB
T-Shirts `div.page-wrapper > ul > li > a.image-tile`	/vite/homepage/client/v1/en/assets/merch-card_tshirt_2x-B...	142.3 KiB	102.5 KiB
div.small-items > div.featured-editorial-item > a.g-button > img.g-image `div.small-items > div.featured-editorial-item > a.g-button > img.g-image`	f4.bcbits.com/img/0044155556_170.jpg	72.4 KiB	65.1 KiB
li.item > a > div.item-loc > span.flag-icon `li.item > a > div.item-loc > span.flag-icon`	/vite/homepage/client/v1/en/assets/_sprite-country-flags-...	71.2 KiB	46.3 KiB
div.small-items > div.featured-editorial-item > a.g-button > img.g-image `div.small-items > div.featured-editorial-item > a.g-button > img.g-image`	f4.bcbits.com/img/0043670458_170.jpg	38.1 KiB	31.6 KiB
div.small-items > div.featured-editorial-item > a.g-button > img.g-image `div.small-items > div.featured-editorial-item > a.g-button > img.g-image`	f4.bcbits.com/img/0043987082_170.jpg	29.0 KiB	24.2 KiB
Ms Nina - Pastillas (King Doudou Edit) `li.item > a > div.item-img > img`	f4.bcbits.com/img/a3948332483_7.jpg	16.8 KiB	15.0 KiB
Last Warning `li.item > a > div.item-img > img`	f4.bcbits.com/img/a4254779095_7.jpg	13.5 KiB	11.7 KiB
Dystopia `li.item > a > div.item-img > img`	f4.bcbits.com/img/a4118235707_7.jpg	9.0 KiB	7.2 KiB
"Gateways To Annihilation" T shirt (Reduced for Bandcamp Friday) `li.item > a > div.item-img > img`	f4.bcbits.com/img/0015390058_37.jpg	8.6 KiB	7.2 KiB
Salsoul Nugget (If You Wanna) [20th Anniversary Extended Klub Mix] `li.item > a > div.item-img > img`	f4.bcbits.com/img/a2431993523_7.jpg	8.5 KiB	6.6 KiB
EP `li.item > a > div.item-img > img`	f4.bcbits.com/img/a0111398991_7.jpg	8.2 KiB	6.4 KiB

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

title: Preconnected origins

value: no origins were preconnected

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

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

URL	Transfer Size	Duration
s4.bcbits.com/vite/homepage/client/v1/en/assets/HomepageApp-DOcMBKq6.css	48.2 KiB	81 ms
/client-bundle/1/ArtistsLabelsPages_1/salesfeed_css-5828a...	2.5 KiB	209 ms

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

Request	Cache TTL	Transfer Size
js.stripe.com/basil/stripe.js	120.0 s	219.8 KiB
m.stripe.network/out-4.5.45.js	300.0 s	16.5 KiB
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	10 ms

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 429 ms

URL	Time Spent
www.bandcamp.com/	429 ms
bandcamp.com/	0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

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

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 130 ms 577.4 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	362.6 KiB	161.8 KiB
js.stripe.com/basil/stripe.js	219.4 KiB	159.9 KiB
/vite/homepage/client/v1/en/entrypoints/HomepageApp.vue_e...	294.8 KiB	125.7 KiB
www.googletagmanager.com/gtag/js?id=GT-WV86TPST&cx=c&gtm=4e6460	175.4 KiB	68.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-TKFS52TF	123.2 KiB	61.9 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

URL	Total CPU Time	Script Evaluation	Script Parse
/vite/homepage/client/v1/en/entrypoints/HomepageApp.vue_e...	1.0 s	972 ms	1.2 ms
Unattributable	612 ms	231 ms	0.0 ms
bandcamp.com/	271 ms	2.5 ms	0.2 ms
www.googletagmanager.com/gtag/js?id=GT-WV86TPST&cx=c&gtm=4e6460	114 ms	95 ms	18 ms
js.stripe.com/basil/stripe.js	87 ms	55 ms	32 ms
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	86 ms	51 ms	29 ms
www.googletagmanager.com/gtm.js?id=GTM-TKFS52TF	59 ms	47 ms	12 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Category	Time Spent
Script Evaluation	1.5 s
Other	442 ms
Style & Layout	166 ms
Script Parsing & Compilation	93 ms
Rendering	61 ms
Garbage Collection	58 ms
Parse HTML & CSS	33 ms

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Estimated savings: 0.0 ms 15.9 KiB

URL	Transfer Size	Est Savings
s4.bcbits.com/vite/homepage/client/v1/en/assets/HomepageApp-DOcMBKq6.css	18.2 KiB	15.9 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
f4.bcbits.com/img/0043986172_0	421.9 KiB
/vite/homepage/client/v1/en/assets/merch-card_cassette_2x...	381.1 KiB
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	363.2 KiB
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	363.2 KiB
/vite/homepage/client/v1/en/entrypoints/HomepageApp.vue_e...	296.7 KiB
s4.bcbits.com/vite/homepage/client/v1/en/assets/merch-card_vinyl_2x-T-u5UH70.jpg	264.7 KiB
js.stripe.com/basil/stripe.js	219.8 KiB
s4.bcbits.com/vite/homepage/client/v1/en/assets/merch-card_cd_2x-DFrFD3A1.jpg	216.8 KiB
www.googletagmanager.com/gtag/js?id=GT-WV86TPST&cx=c&gtm=4e6460	175.4 KiB
/vite/homepage/client/v1/en/assets/merch-card_tshirt_2x-B...	142.7 KiB

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

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 8 user timings

●Avoid long main-thread tasks 8 long tasks found

●Avoid non-composited animations 11 animated elements 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 250 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 480 ms

●Avoid large layout shifts 12 layout shifts found

○INP breakdown

○LCP request discovery

100

Accessibility

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●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

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

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

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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.bandcamp.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

SEO

Keyboard Shortcuts