C — https://www.coinbase.com

Site Health

Score: 70 / 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

Cookie 'cb_logged_out_locale' is missing the Secure flag

Security › Cookie Security

Cookie 'coinbase_currency' is missing the Secure flag

Security › Cookie Security

Cookie 'coinbase_locale' is missing the Secure flag

Security › Cookie Security

No Content-Security-Policy header found

Security › Content Security Policy

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.coinbase.com)](https://beavercheck.com/results/c40dbaa1-3a5a-8da5-1994-64fb28774202)

HTML

<a href="https://beavercheck.com/results/c40dbaa1-3a5a-8da5-1994-64fb28774202"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.coinbase.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.coinbase.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

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.

4.28 s

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

7.88 s

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

842 ms

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

0.023

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

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

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

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
www.coinbase.com/assets/sw-cache/a_UN23PxTD.woff2	40 ms

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:82.252 source:map[type:text value:[unattributed]]]]

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
zero_fees_us.png `div.flex-ff5rfy6 > div.flex-ff5rfy6 > picture.sc-dIsA-D > img.sc-bqGHjI`	/o10es7wu5gm1/4CyfFj8M0X8tKnzh8AgdxT/e61182dc65396f8c5838...	87.4 KiB	73.3 KiB
Advanced Trade Mobile UI `div.flex-ff5rfy6 > div.flex-ff5rfy6 > picture.sc-dIsA-D > img.sc-bqGHjI`	/o10es7wu5gm1/3FwiGvu5fYVsludi8jgOY7/14e7039558786f182123...	81.3 KiB	72.5 KiB
	/o10es7wu5gm1/6NfeXgngo6HkPEPSodFgRN/fc3447a3104f762a704f...	23.1 KiB	16.3 KiB
USDC `div.flex-ff5rfy6 > div.flex-ff5rfy6 > div.flex-ff5rfy6 > img`	/3c15df5e2ac7d4abbe9499ed9335041f00c620f28e8de2f93474a9f4...	9.8 KiB	9.8 KiB
BNB `div.flex-ff5rfy6 > div.flex-ff5rfy6 > div.flex-ff5rfy6 > img`	/asset_icons/c347b6d1a7624e24c4e90089a69dfc8fb75523daf8ee...	9.4 KiB	9.1 KiB

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

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

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
www.coinbase.com/assets/sw-cache/a_Bkbd3lXW.css	23.3 KiB	300 ms

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

Request	Cache TTL	Transfer Size
static-assets.coinbase.com/marketing/videos/jan_es_1180_home.webm	7200.0 s	2.1 MiB
/3c15df5e2ac7d4abbe9499ed9335041f00c620f28e8de2f93474a9f4...	7200.0 s	10.4 KiB
/e785e0181f1a23a30d9476038d9be91e9f6c63959b538eabbc51a1ab...	7200.0 s	3.0 KiB
/41f6a93a3a222078c939115fc304a67c384886b7a9e6c15dcbfa6519...	7200.0 s	2.5 KiB
/dbb4b4983bde81309ddab83eb598358eb44375b930b94687ebe38bc2...	7200.0 s	2.5 KiB
/ui-infra/illustration/v1/pictogram/svg/light/safe-3.svg	7200.0 s	1.6 KiB
/e81509d2307f706f3a6f8999968874b50b628634abf5154fc91a7e5f...	7200.0 s	1.6 KiB
/ui-infra/illustration/v1/pictogram/svg/light/support-5.svg	7200.0 s	1.5 KiB
/ui-infra/illustration/v1/pictogram/svg/light/worldwide-3...	7200.0 s	787 B
/ui-infra/illustration/v1/pictogram/svg/light/trusted-5.svg	7200.0 s	786 B
/ui-infra/illustration/v1/pictogram/svg/light/coinbaseLog...	7200.0 s	691 B

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

URL	Time Spent
www.coinbase.com/	841 ms
www.coinbase.com/en-es/	0.0 ms
www.coinbase.com/en-es	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 JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Estimated savings: 980 ms 366.3 KiB

URL	Transfer Size	Est Savings
www.coinbase.com/assets/sw-cache/e_CPeMmKQD.js	554.2 KiB	212.6 KiB
accounts.google.com/gsi/client	92.7 KiB	69.7 KiB
www.coinbase.com/assets/sw-cache/c_Cpj0G-NY.js	67.6 KiB	60.2 KiB
www.coinbase.com/assets/sw-cache/c_CI3cnUDh.js	41.3 KiB	23.8 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
www.coinbase.com/assets/sw-cache/e_CPeMmKQD.js	3.5 s	2.7 s	9.6 ms
www.coinbase.com/en-es	1.4 s	6.3 ms	0.7 ms
Unattributable	964 ms	57 ms	0.0 ms
www.coinbase.com/assets/sw-cache/c_SDqiHuCG.js	351 ms	326 ms	0.2 ms
accounts.google.com/gsi/client	52 ms	24 ms	27 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	3.4 s
Other	1.6 s
Style & Layout	1.1 s
Rendering	408 ms
Garbage Collection	88 ms
Parse HTML & CSS	51 ms
Script Parsing & Compilation	47 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

URL	Transfer Size
static-assets.coinbase.com/marketing/videos/jan_es_1180_home.webm	2.1 MiB
www.coinbase.com/assets/sw-cache/e_CPeMmKQD.js	556.4 KiB
www.coinbase.com/assets/sw-cache/a_UN23PxTD.woff2	259.4 KiB
accounts.google.com/gsi/client	93.5 KiB
/o10es7wu5gm1/4CyfFj8M0X8tKnzh8AgdxT/e61182dc65396f8c5838...	87.8 KiB
/o10es7wu5gm1/3FwiGvu5fYVsludi8jgOY7/14e7039558786f182123...	81.7 KiB
www.coinbase.com/assets/sw-cache/c_Cpj0G-NY.js	68.1 KiB
www.coinbase.com/en-es	58.9 KiB
www.coinbase.com/assets/sw-cache/c_CI3cnUDh.js	41.8 KiB
www.coinbase.com/assets/sw-cache/a_B-911Gqf.woff2	41.0 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

●Reduce unused CSS

●User Timing marks and measures 12 user timings

●Avoid long main-thread tasks 19 long tasks found

●Avoid non-composited animations 20 animated elements found

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

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 120 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

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

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
Learn more 󰐲 `div.flex-ff5rfy6 > div.flex-ff5rfy6 > div.sc-kLokie > a#3irks3OX2b7AW6Ee473T12`
Careers `div.flex-ff5rfy6 > div.flex-ff5rfy6 > div.flex-ff5rfy6 > a.sc-bdnylu`
Affiliates `div.flex-ff5rfy6 > div.flex-ff5rfy6 > div.flex-ff5rfy6 > a.sc-bdnylu`
Press `div.flex-ff5rfy6 > div.flex-ff5rfy6 > div.flex-ff5rfy6 > a.sc-bdnylu`
Legal & privacy `div.flex-ff5rfy6 > div.flex-ff5rfy6 > div.flex-ff5rfy6 > a.sc-bdnylu`
Taxes `div.flex-ff5rfy6 > div.flex-ff5rfy6 > div.flex-ff5rfy6 > a.sc-bdnylu`
Create account `div.flex-ff5rfy6 > div.flex-ff5rfy6 > div.flex-ff5rfy6 > a.sc-bdnylu`

○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

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

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

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

●Elements use only permitted ARIA attributes

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

●Heading elements appear in a sequentially-descending order

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○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

○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

○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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Source	Description
www.coinbase.com/en-es	`Not signed in with the identity provider.`
www.coinbase.com/assets/sw-cache/e_CPeMmKQD.js line 83, col 2271	`ScriptLoader: Failed to load script: otSDKStub.js`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

●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 issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

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
/en-gb/coinbase/coinbase-staking/rewards/earn-rewards-wit...	Learn more
www.coinbase.com/en-es/advanced-trade	Learn more
www.coinbase.com/en-es/blog/coinbase-obtains-bank-of-spain-registration-in-spain	Learn more
/coinbase/other-topics/legal-policies/what-does-coinbase-...	Learn more
help.coinbase.com/en	Learn more

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

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.

300 ms

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

833 ms

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

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

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

833 ms

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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.

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

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

Request	Cache TTL	Transfer Size
www.coinbase.com/favicon.ico	7200.0 s	1.5 KiB
/cdn-cgi/challenge-platform/h/b/d/9e8bc051fc8e998d/177559...	0.0 ms	410 B
challenges.cloudflare.com/cdn-cgi/challenge-platform/h/b/cmg/1	0.0 ms	208 B

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

Diagnostics

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reason	Failure type
Pages that use WebXR are not currently eligible for back/forward cache.	Actionable
Only pages with a status code of 2XX can be cached.	Not actionable

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

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

Estimated savings: 228 ms

URL	Time Spent
www.coinbase.com/	228 ms
www.coinbase.com/	0.0 ms

●Max Potential First Input Delay 100 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Time to Interactive 0.8 s

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 496 KiB

●JavaScript execution time 0.4 s

●Minimizes main-thread work 0.5 s

●Avoid long main-thread tasks 3 long tasks found

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

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 30 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

Best practices

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

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

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

●`[role]` values are valid

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

●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 have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○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

○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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

○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

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

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Source	Description
www.coinbase.com/	`Failed to load resource: the server responded with a status of 403 ()`

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

Crawling and Indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Blocking Directive Source
`head > meta`

Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.

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

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

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

○Structured data is valid

●Document has a `<title>` element

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

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best practices

Best Practices

General

SEO

Crawling and Indexing

Content Best Practices

Keyboard Shortcuts

URL	Map URL
www.coinbase.com/assets/sw-cache/e_CPeMmKQD.js	www.coinbase.com/assets/sw-cache/e_CPeMmKQD.js.map
www.coinbase.com/assets/sw-cache/c_ysNT0ap1.js	www.coinbase.com/assets/sw-cache/c_ysNT0ap1.js.map
www.coinbase.com/assets/sw-cache/c_X5EwIX3J.js	www.coinbase.com/assets/sw-cache/c_X5EwIX3J.js.map
www.coinbase.com/assets/sw-cache/c_w-6iEb5o.js	www.coinbase.com/assets/sw-cache/c_w-6iEb5o.js.map
www.coinbase.com/assets/sw-cache/c_uTXMDFnW.js	www.coinbase.com/assets/sw-cache/c_uTXMDFnW.js.map
www.coinbase.com/assets/sw-cache/c_TZ9AZJOK.js	www.coinbase.com/assets/sw-cache/c_TZ9AZJOK.js.map
www.coinbase.com/assets/sw-cache/c_TyZ_q2nh.js	www.coinbase.com/assets/sw-cache/c_TyZ_q2nh.js.map
www.coinbase.com/assets/sw-cache/c_SDqiHuCG.js	www.coinbase.com/assets/sw-cache/c_SDqiHuCG.js.map
www.coinbase.com/assets/sw-cache/c_rjn79CYD.js	www.coinbase.com/assets/sw-cache/c_rjn79CYD.js.map
www.coinbase.com/assets/sw-cache/c_RcrwUx-d.js	www.coinbase.com/assets/sw-cache/c_RcrwUx-d.js.map
www.coinbase.com/assets/sw-cache/c_Q5--YJR1.js	www.coinbase.com/assets/sw-cache/c_Q5--YJR1.js.map
www.coinbase.com/assets/sw-cache/c_L3pYwZZ0.js	www.coinbase.com/assets/sw-cache/c_L3pYwZZ0.js.map
www.coinbase.com/assets/sw-cache/c_jA1pyJdG.js	www.coinbase.com/assets/sw-cache/c_jA1pyJdG.js.map
www.coinbase.com/assets/sw-cache/c_HStDg1Xy.js	www.coinbase.com/assets/sw-cache/c_HStDg1Xy.js.map
www.coinbase.com/assets/sw-cache/c_HRYrYZCI.js	www.coinbase.com/assets/sw-cache/c_HRYrYZCI.js.map
www.coinbase.com/assets/sw-cache/c_g1LcrEgV.js	www.coinbase.com/assets/sw-cache/c_g1LcrEgV.js.map
www.coinbase.com/assets/sw-cache/c_Dz_0aXDb.js	www.coinbase.com/assets/sw-cache/c_Dz_0aXDb.js.map
www.coinbase.com/assets/sw-cache/c_DyInOPXi.js	www.coinbase.com/assets/sw-cache/c_DyInOPXi.js.map
www.coinbase.com/assets/sw-cache/c_DqL8Lx3T.js	www.coinbase.com/assets/sw-cache/c_DqL8Lx3T.js.map
www.coinbase.com/assets/sw-cache/c_DL1llzJv.js	www.coinbase.com/assets/sw-cache/c_DL1llzJv.js.map
www.coinbase.com/assets/sw-cache/c_DkxkIMwB.js	www.coinbase.com/assets/sw-cache/c_DkxkIMwB.js.map
www.coinbase.com/assets/sw-cache/c_DktDIGJb.js	www.coinbase.com/assets/sw-cache/c_DktDIGJb.js.map
www.coinbase.com/assets/sw-cache/c_Dirx8Aan.js	www.coinbase.com/assets/sw-cache/c_Dirx8Aan.js.map
www.coinbase.com/assets/sw-cache/c_DHDa1QPs.js	www.coinbase.com/assets/sw-cache/c_DHDa1QPs.js.map
www.coinbase.com/assets/sw-cache/c_DeQ3ofbh.js	www.coinbase.com/assets/sw-cache/c_DeQ3ofbh.js.map
www.coinbase.com/assets/sw-cache/c_DcRmFwcz.js	www.coinbase.com/assets/sw-cache/c_DcRmFwcz.js.map
www.coinbase.com/assets/sw-cache/c_D8FG9MFc.js	www.coinbase.com/assets/sw-cache/c_D8FG9MFc.js.map
www.coinbase.com/assets/sw-cache/c_D7mIBtgy.js	www.coinbase.com/assets/sw-cache/c_D7mIBtgy.js.map
www.coinbase.com/assets/sw-cache/c_D55awcGq.js	www.coinbase.com/assets/sw-cache/c_D55awcGq.js.map
www.coinbase.com/assets/sw-cache/c_D3ZSCYSR.js	www.coinbase.com/assets/sw-cache/c_D3ZSCYSR.js.map
www.coinbase.com/assets/sw-cache/c_D2V_0Ztd.js	www.coinbase.com/assets/sw-cache/c_D2V_0Ztd.js.map
www.coinbase.com/assets/sw-cache/c_CyDhOLro.js	www.coinbase.com/assets/sw-cache/c_CyDhOLro.js.map
www.coinbase.com/assets/sw-cache/c_Cw5PNGq7.js	www.coinbase.com/assets/sw-cache/c_Cw5PNGq7.js.map
www.coinbase.com/assets/sw-cache/c_Cvk6ZQPS.js	www.coinbase.com/assets/sw-cache/c_Cvk6ZQPS.js.map
www.coinbase.com/assets/sw-cache/c_Cv7POSaS.js	www.coinbase.com/assets/sw-cache/c_Cv7POSaS.js.map
www.coinbase.com/assets/sw-cache/c_CV6BZIW_.js	www.coinbase.com/assets/sw-cache/c_CV6BZIW_.js.map
www.coinbase.com/assets/sw-cache/c_CuNIFUYH.js	www.coinbase.com/assets/sw-cache/c_CuNIFUYH.js.map
www.coinbase.com/assets/sw-cache/c_CrOMzC4s.js	www.coinbase.com/assets/sw-cache/c_CrOMzC4s.js.map
www.coinbase.com/assets/sw-cache/c_CrE9VJSo.js	www.coinbase.com/assets/sw-cache/c_CrE9VJSo.js.map
www.coinbase.com/assets/sw-cache/c_Cpj0G-NY.js	www.coinbase.com/assets/sw-cache/c_Cpj0G-NY.js.map
www.coinbase.com/assets/sw-cache/c_CO6p2xsw.js	www.coinbase.com/assets/sw-cache/c_CO6p2xsw.js.map
www.coinbase.com/assets/sw-cache/c_CmSc97sb.js	www.coinbase.com/assets/sw-cache/c_CmSc97sb.js.map
www.coinbase.com/assets/sw-cache/c_Cj2N3gjZ.js	www.coinbase.com/assets/sw-cache/c_Cj2N3gjZ.js.map
www.coinbase.com/assets/sw-cache/c_CI3otBnN.js	www.coinbase.com/assets/sw-cache/c_CI3otBnN.js.map
www.coinbase.com/assets/sw-cache/c_CI3cnUDh.js	www.coinbase.com/assets/sw-cache/c_CI3cnUDh.js.map
www.coinbase.com/assets/sw-cache/c_Ch50ya4g.js	www.coinbase.com/assets/sw-cache/c_Ch50ya4g.js.map
www.coinbase.com/assets/sw-cache/c_CgYUVQbF.js	www.coinbase.com/assets/sw-cache/c_CgYUVQbF.js.map
www.coinbase.com/assets/sw-cache/c_CgekLoky.js	www.coinbase.com/assets/sw-cache/c_CgekLoky.js.map
www.coinbase.com/assets/sw-cache/c_CG1oB3en.js	www.coinbase.com/assets/sw-cache/c_CG1oB3en.js.map
www.coinbase.com/assets/sw-cache/c_CFOUK3I6.js	www.coinbase.com/assets/sw-cache/c_CFOUK3I6.js.map
www.coinbase.com/assets/sw-cache/c_Cf8wZY4X.js	www.coinbase.com/assets/sw-cache/c_Cf8wZY4X.js.map
www.coinbase.com/assets/sw-cache/c_CC0NZLNn.js	www.coinbase.com/assets/sw-cache/c_CC0NZLNn.js.map
www.coinbase.com/assets/sw-cache/c_CamGwVL_.js	www.coinbase.com/assets/sw-cache/c_CamGwVL_.js.map
www.coinbase.com/assets/sw-cache/c_C8Ajc6GT.js	www.coinbase.com/assets/sw-cache/c_C8Ajc6GT.js.map
www.coinbase.com/assets/sw-cache/c_C541nKh_.js	www.coinbase.com/assets/sw-cache/c_C541nKh_.js.map
www.coinbase.com/assets/sw-cache/c_BzEDHLAA.js	www.coinbase.com/assets/sw-cache/c_BzEDHLAA.js.map
www.coinbase.com/assets/sw-cache/c_BvoB-3h9.js	www.coinbase.com/assets/sw-cache/c_BvoB-3h9.js.map
www.coinbase.com/assets/sw-cache/c_BUJ-iIkL.js	www.coinbase.com/assets/sw-cache/c_BUJ-iIkL.js.map
www.coinbase.com/assets/sw-cache/c_BsKrf6L3.js	www.coinbase.com/assets/sw-cache/c_BsKrf6L3.js.map
www.coinbase.com/assets/sw-cache/c_bnknJcWj.js	www.coinbase.com/assets/sw-cache/c_bnknJcWj.js.map
www.coinbase.com/assets/sw-cache/c_BNigQxJa.js	www.coinbase.com/assets/sw-cache/c_BNigQxJa.js.map
www.coinbase.com/assets/sw-cache/c_Bn0h1yQM.js	www.coinbase.com/assets/sw-cache/c_Bn0h1yQM.js.map
www.coinbase.com/assets/sw-cache/c_BmLoDlXf.js	www.coinbase.com/assets/sw-cache/c_BmLoDlXf.js.map
www.coinbase.com/assets/sw-cache/c_BlWoaOcB.js	www.coinbase.com/assets/sw-cache/c_BlWoaOcB.js.map
www.coinbase.com/assets/sw-cache/c_BkWcoLTJ.js	www.coinbase.com/assets/sw-cache/c_BkWcoLTJ.js.map
www.coinbase.com/assets/sw-cache/c_BHKBAqMl.js	www.coinbase.com/assets/sw-cache/c_BHKBAqMl.js.map
www.coinbase.com/assets/sw-cache/c_BbLHalhQ.js	www.coinbase.com/assets/sw-cache/c_BbLHalhQ.js.map
www.coinbase.com/assets/sw-cache/c_Ba0o2jzA.js	www.coinbase.com/assets/sw-cache/c_Ba0o2jzA.js.map
www.coinbase.com/assets/sw-cache/c_B7A5ZlmX.js	www.coinbase.com/assets/sw-cache/c_B7A5ZlmX.js.map
www.coinbase.com/assets/sw-cache/c_B6Pw_4Fk.js	www.coinbase.com/assets/sw-cache/c_B6Pw_4Fk.js.map
www.coinbase.com/assets/sw-cache/c_B39S26YY.js	www.coinbase.com/assets/sw-cache/c_B39S26YY.js.map
www.coinbase.com/assets/sw-cache/c_B2c7Cgx4.js	www.coinbase.com/assets/sw-cache/c_B2c7Cgx4.js.map
www.coinbase.com/assets/sw-cache/c_B0chDisy.js	www.coinbase.com/assets/sw-cache/c_B0chDisy.js.map
www.coinbase.com/assets/sw-cache/c_6GJmLfPv.js	www.coinbase.com/assets/sw-cache/c_6GJmLfPv.js.map
www.coinbase.com/assets/sw-cache/c_0ZuYNXFi.js	www.coinbase.com/assets/sw-cache/c_0ZuYNXFi.js.map
www.coinbase.com/assets/sw-cache/c_0GFxC2Fi.js	www.coinbase.com/assets/sw-cache/c_0GFxC2Fi.js.map
www.coinbase.com/assets/sw-cache/c__TiwkVVg.js	www.coinbase.com/assets/sw-cache/c__TiwkVVg.js.map