C — https://www.brave.com | BeaverCheck Audit

Site Health

Score: 79 / 100 +1

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

HSTS header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

2 button(s) with no accessible text

Accessibility › Link & Button Quality

2 image-only link(s) without alt text

Accessibility › Link & Button Quality

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.brave.com)](https://beavercheck.com/results/cebd74ef-4801-441f-86ea-f685fceb8ea3)

HTML

<a href="https://beavercheck.com/results/cebd74ef-4801-441f-86ea-f685fceb8ea3"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.brave.com" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Global Performance 6/6 locations ✓

ES Madrid

Full audit

258ms

DNS 64ms · TLS 19ms

UN New York

Full audit

37ms

DNS 30ms · TLS 4ms

US Santa Clara

Full audit

27ms

DNS 14ms · TLS 6ms

BR Sao Paulo

Full audit

214ms

DNS 12ms · TLS 6ms

SG Singapore

Full audit

236ms

DNS 44ms · TLS 4ms

NL Amsterdam

Full audit

295ms

DNS 286ms · TLS 4ms

CDN: AWS CloudFront (Miss from cloudfront) · Avg TTFB: 178ms · Cache: No cache headers

Recent Trends

Performance degrading ↓

TTFB degrading ↓

295ms

FCP degrading ↓

3.5s

LCP degrading ↓

4.2s

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

71 -4

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.

3.46 s

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

4.14 s

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

331 ms

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

0.067

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

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

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

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

Request	Cache TTL	Transfer Size
/js/brave-search-widget.961e53a4365debef5ed2bac4c11380ca7...	0.0 ms	65.6 KiB
brave.com/static-assets/fonts/inter/inter-latin-wght-normal.woff2	0.0 ms	48.5 KiB
/js/lottie-player.f8a02068d6eea9045634f798c4ae07cd41599d1...	0.0 ms	46.9 KiB
brave.com/static-assets/fonts/FlechaM/FlechaM-Medium.woff2	0.0 ms	42.7 KiB
/static-assets/css/main.min.f25ba329c7c76dabb55f8838e05ff...	0.0 ms	41.3 KiB
brave.com/matomo.js	0.0 ms	25.5 KiB
brave.com/home-assets/images/app-illustration.svg	0.0 ms	22.8 KiB
brave.com/static-assets/fonts/poppins/poppins-latin-600-italic.woff2	0.0 ms	9.7 KiB
brave.com/static-assets/fonts/poppins/poppins-latin-600-normal.woff2	0.0 ms	9.0 KiB
brave.com/static-assets/fonts/poppins/poppins-latin-400-normal.woff2	0.0 ms	8.9 KiB
brave.com/static-assets/fonts/poppins/poppins-latin-700-normal.woff2	0.0 ms	8.8 KiB
brave.com/vendors/brave-search-widget/style.css	0.0 ms	7.9 KiB
brave.com/home-assets/images/vpn-illustration.svg	0.0 ms	7.5 KiB
brave.com/static-assets/fonts/poppins/poppins-latin-ext-400-normal.woff2	0.0 ms	6.7 KiB
brave.com/home-assets/images/leo-illustration.svg	0.0 ms	5.7 KiB
brave.com/leo-icons/safari-color.svg	0.0 ms	4.1 KiB
brave.com/leo-icons/firefox-color.svg	0.0 ms	3.6 KiB
brave.com/static-assets/images/interstitial-download-qr.png	0.0 ms	3.5 KiB
brave.com/leo-icons/google-color.svg	0.0 ms	3.5 KiB
/js/5-set-download-urls.b5c47076524cf6c338c6950c01ce3274c...	0.0 ms	3.3 KiB
/js/navigation.dfd1f44125a1e31a3a0643daa3596bf331980a9e11...	0.0 ms	3.2 KiB
brave.com/static-assets/images/brave-logo.svg	0.0 ms	3.1 KiB
brave.com/static-assets/images/brave-logo-sans-text.svg	0.0 ms	2.9 KiB
brave.com/leo-icons/duckduckgo-color.svg	0.0 ms	2.7 KiB
brave.com/static-assets/js/analysis.js	0.0 ms	2.7 KiB
brave.com/leo-icons/social-brave-release-favicon-fullheight-color.svg	0.0 ms	2.6 KiB
brave.com/static-assets/images/brave-logo-text-only.svg	0.0 ms	2.5 KiB
/js/localization.eac6ebe6b760650c196b5ce8eb0033649e2db78e...	0.0 ms	2.2 KiB
brave.com/leo-icons/edge-color.svg	0.0 ms	2.2 KiB
brave.com/home-assets/images/line-waves.svg	0.0 ms	2.1 KiB
/js/4-details-summary-animation.2b2cb643f1890d8e7d4a6ec3c...	0.0 ms	2.0 KiB
/static-assets/css/fonts-latin.min.e207b9357b68ec783b0e1f...	0.0 ms	2.0 KiB
/js/tabs.4422877367929b6c6bcf6f974a9d2943058b06cf9af5f3a2...	0.0 ms	1.9 KiB
brave.com/static-assets/js/ie-shims.js	0.0 ms	1.9 KiB
/js/dev.730af03ea8ceb4d931331d7b8b5624ffabb540a8ce32625c7...	0.0 ms	1.9 KiB
/js/interstitial.ed54a6886dab8f7e38d1a18b72dd8100d64ccad1...	0.0 ms	1.8 KiB
/js/preserve-query-params.40023c3d4fc7197ee3f7968de935234...	0.0 ms	1.8 KiB
/js/card-carousel.717a7c5436ba434620e1d4b02317402f5169f01...	0.0 ms	1.8 KiB
brave.com/leo-icons/download.svg	0.0 ms	1.8 KiB
brave.com/scss/brave-search-widget-customizations.css	0.0 ms	1.8 KiB
/js/image-comparison-slider.024d5546db2bcf149a9c680bbc795...	0.0 ms	1.7 KiB
brave.com/leo-icons/chromerelease-color.svg	0.0 ms	1.7 KiB
/js/set-platform.a4b5c2cf36a94e5497142976e089e61ddf9a6d0c...	0.0 ms	1.6 KiB
brave.com/leo-icons/arrow-up-and-down.svg	0.0 ms	1.6 KiB
brave.com/static-assets/icons/close-icon.svg	0.0 ms	1.5 KiB
brave.com/leo-icons/search.svg	0.0 ms	1.5 KiB
/js/3-delay-animations.52117dc3caa2efe969d724cfc404c33601...	0.0 ms	1.4 KiB
brave.com/leo-icons/minus.svg	0.0 ms	1.4 KiB
brave.com/static-assets/icons/arrow-alt-down.svg	0.0 ms	1.3 KiB

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

lhId: page-0-IMG

nodeLabel: main.site-main > section#features-blocks > div.card > img.absolute

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

selector: main.site-main > section#features-blocks > div.card > img.absolute

snippet: <img class="absolute bottom-0 left-0 w-full max-h-[140px]" src="/home-assets/images/line-waves.svg" 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

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

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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

URL	Transfer Size	Duration
brave.com/matomo.js	25.5 KiB	759 ms
/static-assets/css/fonts-latin.min.e207b9357b68ec783b0e1f...	2.0 KiB	459 ms
/js/set-platform.a4b5c2cf36a94e5497142976e089e61ddf9a6d0c...	1.6 KiB	459 ms
brave.com/static-assets/js/analysis.js	2.7 KiB	459 ms
brave.com/static-assets/js/ie-shims.js	1.9 KiB	459 ms
/js/localization.eac6ebe6b760650c196b5ce8eb0033649e2db78e...	2.2 KiB	459 ms
/static-assets/css/main.min.f25ba329c7c76dabb55f8838e05ff...	41.3 KiB	1.1 s

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

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: 798 ms

URL	Time Spent
www.brave.com/	798 ms
brave.com/	0.0 ms

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

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

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: 150 ms 21.3 KiB

URL	Transfer Size	Est Savings
/static-assets/css/main.min.f25ba329c7c76dabb55f8838e05ff...	40.1 KiB	21.3 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: 0.0 ms 21.5 KiB

URL	Transfer Size	Est Savings
/js/lottie-player.f8a02068d6eea9045634f798c4ae07cd41599d1...	45.6 KiB	21.5 KiB

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.1 s
Other	994 ms
Style & Layout	603 ms
Garbage Collection	147 ms
Rendering	121 ms
Parse HTML & CSS	113 ms
Script Parsing & Compilation	25 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
App Illustration `main.site-main > section.full-bleed > div.flex > img.-mb-24`	brave.com/home-assets/images/app-illustration.svg
Brave Software home `footer.site-footer > div.site-footer__container > div.w-full > img.w-24`	brave.com/static-assets/images/brave-logo.svg
Brave Software home `header.site-header > div.relative > a > img.h-10`	brave.com/static-assets/images/brave-logo-sans-text.svg

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 520 KiB

●JavaScript execution time 1.0 s

●Avoid long main-thread tasks 9 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

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

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Failing Elements
Private search `main.site-main > section#features-blocks > div.card > h4.text-h2`
Brave vs Chrome `div.grid > div.w-[min(309px,calc(100vw-3rem))] > div > h4.text-h3`
USER RESOURCES `div.site-footer__container > div.site-footer__column > div.site-footer__grouping > h4.site-footer__heading`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Failing Elements
div#brave-vs-chrome > div.c-compare > div.c-compare__slider > input.c-compare__range `div#brave-vs-chrome > div.c-compare > div.c-compare__slider > input.c-compare__range`

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-*]` 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

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

●Select elements have associated label elements.

●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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Identical links have the same purpose.

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

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

○`<object>` elements have alternate text

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

○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

●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

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Link destination	Link Text
laptop-updates.brave.com/download/android/BRV002	here

Format your HTML in a way that enables crawlers to better understand your app’s content.

○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 are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

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

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

1.30 s

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

46 ms

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

0.004

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

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

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

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

Request	Cache TTL	Transfer Size
/js/brave-search-widget.961e53a4365debef5ed2bac4c11380ca7...	0.0 ms	65.6 KiB
brave.com/static-assets/fonts/inter/inter-latin-wght-normal.woff2	0.0 ms	48.5 KiB
/js/lottie-player.f8a02068d6eea9045634f798c4ae07cd41599d1...	0.0 ms	46.8 KiB
brave.com/static-assets/fonts/FlechaM/FlechaM-Medium.woff2	0.0 ms	42.7 KiB
/static-assets/css/main.min.f25ba329c7c76dabb55f8838e05ff...	0.0 ms	41.4 KiB
brave.com/matomo.js	0.0 ms	25.5 KiB
brave.com/home-assets/images/app-illustration.svg	0.0 ms	22.7 KiB
brave.com/static-assets/fonts/poppins/poppins-latin-600-italic.woff2	0.0 ms	9.7 KiB
brave.com/static-assets/fonts/poppins/poppins-latin-600-normal.woff2	0.0 ms	9.0 KiB
brave.com/static-assets/fonts/poppins/poppins-latin-400-normal.woff2	0.0 ms	8.9 KiB
brave.com/static-assets/fonts/poppins/poppins-latin-700-normal.woff2	0.0 ms	8.8 KiB
brave.com/vendors/brave-search-widget/style.css	0.0 ms	7.9 KiB
brave.com/home-assets/images/vpn-illustration.svg	0.0 ms	7.5 KiB
brave.com/static-assets/fonts/poppins/poppins-latin-ext-400-normal.woff2	0.0 ms	6.7 KiB
brave.com/home-assets/images/leo-illustration.svg	0.0 ms	5.7 KiB
brave.com/leo-icons/safari-color.svg	0.0 ms	4.1 KiB
brave.com/leo-icons/firefox-color.svg	0.0 ms	3.6 KiB
brave.com/static-assets/images/interstitial-download-qr.png	0.0 ms	3.5 KiB
brave.com/leo-icons/google-color.svg	0.0 ms	3.5 KiB
/js/5-set-download-urls.b5c47076524cf6c338c6950c01ce3274c...	0.0 ms	3.3 KiB
/js/navigation.dfd1f44125a1e31a3a0643daa3596bf331980a9e11...	0.0 ms	3.2 KiB
brave.com/static-assets/images/brave-logo.svg	0.0 ms	3.1 KiB
brave.com/static-assets/images/brave-logo-sans-text.svg	0.0 ms	2.9 KiB
brave.com/leo-icons/duckduckgo-color.svg	0.0 ms	2.7 KiB
brave.com/static-assets/js/analysis.js	0.0 ms	2.7 KiB
brave.com/leo-icons/social-brave-release-favicon-fullheight-color.svg	0.0 ms	2.6 KiB
brave.com/static-assets/images/brave-logo-text-only.svg	0.0 ms	2.5 KiB
/js/localization.eac6ebe6b760650c196b5ce8eb0033649e2db78e...	0.0 ms	2.2 KiB
brave.com/leo-icons/edge-color.svg	0.0 ms	2.2 KiB
brave.com/home-assets/images/line-waves.svg	0.0 ms	2.1 KiB
/js/4-details-summary-animation.2b2cb643f1890d8e7d4a6ec3c...	0.0 ms	2.0 KiB
/static-assets/css/fonts-latin.min.e207b9357b68ec783b0e1f...	0.0 ms	2.0 KiB
/js/tabs.4422877367929b6c6bcf6f974a9d2943058b06cf9af5f3a2...	0.0 ms	1.9 KiB
brave.com/static-assets/js/ie-shims.js	0.0 ms	1.9 KiB
/js/dev.730af03ea8ceb4d931331d7b8b5624ffabb540a8ce32625c7...	0.0 ms	1.9 KiB
/js/interstitial.ed54a6886dab8f7e38d1a18b72dd8100d64ccad1...	0.0 ms	1.8 KiB
/js/preserve-query-params.40023c3d4fc7197ee3f7968de935234...	0.0 ms	1.8 KiB
/js/card-carousel.717a7c5436ba434620e1d4b02317402f5169f01...	0.0 ms	1.8 KiB
brave.com/leo-icons/download.svg	0.0 ms	1.8 KiB
brave.com/scss/brave-search-widget-customizations.css	0.0 ms	1.8 KiB
/js/image-comparison-slider.024d5546db2bcf149a9c680bbc795...	0.0 ms	1.7 KiB
brave.com/leo-icons/chromerelease-color.svg	0.0 ms	1.7 KiB
/js/set-platform.a4b5c2cf36a94e5497142976e089e61ddf9a6d0c...	0.0 ms	1.6 KiB
brave.com/leo-icons/arrow-up-and-down.svg	0.0 ms	1.6 KiB
brave.com/static-assets/icons/close-icon.svg	0.0 ms	1.5 KiB
brave.com/leo-icons/search.svg	0.0 ms	1.5 KiB
brave.com/leo-icons/arrow-right.svg	0.0 ms	1.5 KiB
brave.com/leo-icons/arrow-left.svg	0.0 ms	1.5 KiB
brave.com/leo-icons/arrow-small-down.svg	0.0 ms	1.5 KiB
/js/3-delay-animations.52117dc3caa2efe969d724cfc404c33601...	0.0 ms	1.4 KiB
brave.com/leo-icons/minus.svg	0.0 ms	1.4 KiB
brave.com/static-assets/icons/arrow-alt-down.svg	0.0 ms	1.3 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

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

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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

URL	Transfer Size	Duration
brave.com/matomo.js	25.5 KiB	146 ms
brave.com/static-assets/js/analysis.js	2.7 KiB	146 ms
/js/localization.eac6ebe6b760650c196b5ce8eb0033649e2db78e...	2.2 KiB	146 ms
/js/set-platform.a4b5c2cf36a94e5497142976e089e61ddf9a6d0c...	1.6 KiB	146 ms
/static-assets/css/main.min.f25ba329c7c76dabb55f8838e05ff...	41.4 KiB	238 ms
/static-assets/css/fonts-latin.min.e207b9357b68ec783b0e1f...	2.0 KiB	146 ms
brave.com/static-assets/js/ie-shims.js	1.9 KiB	146 ms

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

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: 248 ms

URL	Time Spent
www.brave.com/	248 ms
brave.com/	0.0 ms

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

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: 100 ms 19.8 KiB

URL	Transfer Size	Est Savings
/static-assets/css/main.min.f25ba329c7c76dabb55f8838e05ff...	40.2 KiB	19.8 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: 0.0 ms 21.4 KiB

URL	Transfer Size	Est Savings
/js/lottie-player.f8a02068d6eea9045634f798c4ae07cd41599d1...	45.6 KiB	21.4 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
Download QR code `body.home-page > div#interstitial > div#mobile-qr-banner > img.h-20`	brave.com/static-assets/images/interstitial-download-qr.png
App Illustration `main.site-main > section.full-bleed > div.flex > img.-mb-24`	brave.com/home-assets/images/app-illustration.svg
Brave Software home `footer.site-footer > div.site-footer__container > div.w-full > img.w-24`	brave.com/static-assets/images/brave-logo.svg
Brave Software home `header.site-header > div.relative > a > img.h-10`	brave.com/static-assets/images/brave-logo-sans-text.svg
Brave logo `div#interstitial > section.bg-white > div.layout > img.w-[42px]`	brave.com/static-assets/images/brave-logo-sans-text.svg
close `div#interstitial > section.bg-white > button.close > img`	brave.com/static-assets/icons/close-icon.svg

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

●Time to Interactive 1.5 s

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 524 KiB

●JavaScript execution time 0.3 s

●Minimizes main-thread work 1.1 s

●Avoid long main-thread tasks 2 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 190 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

Accessibility

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Failing Elements
Browser `nav.site-nav > ul.block > li.border-t > span.nav-item`
Search `nav.site-nav > ul.block > li.border-t > span.nav-item`
Private AI `nav.site-nav > ul.block > li.border-t > span.nav-item`
Search API `nav.site-nav > ul.block > li.border-t > span.nav-item`
Brave for business `nav.site-nav > ul.block > li.border-t > span.nav-item`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Failing Elements
Private search `main.site-main > section#features-blocks > div.card > h4.text-h2`
Brave vs Chrome `div.grid > div.w-[min(309px,calc(100vw-3rem))] > div > h4.text-h3`
USER RESOURCES `div.site-footer__container > div.site-footer__column > div.site-footer__grouping > h4.site-footer__heading`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Failing Elements
div#brave-vs-chrome > div.c-compare > div.c-compare__slider > input.c-compare__range `div#brave-vs-chrome > div.c-compare > div.c-compare__slider > input.c-compare__range`

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

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

●Select elements have associated label elements.

●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

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

●Document has a main landmark.

●Identical links have the same purpose.

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

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

○`<object>` elements have alternate text

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

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

○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

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.brave.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Navigation

Names and labels

Best Practices

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Navigation

Names and labels

Best Practices

SEO

Keyboard Shortcuts