C — https://www.stripe.dev | BeaverCheck Audit

Site Health

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

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Cross-Origin-Opener-Policy header is missing

Security › Security Headers

External script from plausible.io lacks integrity attribute

Security › Subresource Integrity

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.stripe.dev)](https://beavercheck.com/results/705ea3f0-18ba-e4fa-05c1-161bf8171604)

HTML

<a href="https://beavercheck.com/results/705ea3f0-18ba-e4fa-05c1-161bf8171604"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.stripe.dev" alt="BeaverCheck Score"></a>

Image URL

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

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

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.

1.83 s

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

3.45 s

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

475 ms

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

0.001

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

2.06 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.93 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.

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

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
stripe.dev/fonts/Sohne.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: 755 ms

URL	Time Spent
www.stripe.dev/	755 ms
stripe.dev/	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: 300 ms 227.5 KiB

URL	Transfer Size	Est Savings
stripe.dev/_next/static/chunks/04vp02y0.g70m.js	99.6 KiB	69.0 KiB
stripe.dev/_next/static/chunks/16cer0h2fduw2.js	52.3 KiB	52.0 KiB
stripe.dev/_next/static/chunks/02-c.cxhqmdyv.js	52.3 KiB	52.0 KiB
stripe.dev/_next/static/chunks/0b29c3sj~k-mz.js	52.4 KiB	30.2 KiB
stripe.dev/_next/static/chunks/0uvx_1ip89~4x.js	65.8 KiB	24.3 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
stripe.dev/_next/static/chunks/0uvx_1ip89~4x.js	2.3 s	1.2 s	26 ms
stripe.dev/_next/static/chunks/0wuvx6-x2fqhp.js	1.6 s	163 ms	4.5 ms
stripe.dev/	827 ms	7.1 ms	0.7 ms
Unattributable	292 ms	13 ms	0.0 ms
stripe.dev/_next/static/chunks/0nd2wb02x-834.js	143 ms	15 ms	3.3 ms
stripe.dev/_next/static/chunks/turbopack-0hiarq.gu0mr6.js	138 ms	135 ms	1.5 ms
stripe.dev/_next/static/chunks/0c.n5x18151dz.js	130 ms	126 ms	3.9 ms
stripe.dev/_next/static/chunks/0t9t-9dsl2dxg.js	113 ms	109 ms	3.9 ms
stripe.dev/_next/static/chunks/turbopack-0e9tu6_ctnf0t.js	77 ms	75 ms	1.7 ms
stripe.dev/_next/static/chunks/0b29c3sj~k-mz.js	68 ms	11 ms	20 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
Other	2.7 s
Script Evaluation	1.9 s
Style & Layout	662 ms
Rendering	442 ms
Script Parsing & Compilation	217 ms
Parse HTML & CSS	50 ms

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

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 638 KiB

●User Timing marks and measures 7 user timings

●Avoid long main-thread tasks 13 long tasks found

●Avoid non-composited animations 3 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 100 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

Accessibility

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

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Event (5) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(5) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Video (5) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(5) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Blog (10) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(10) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Agentic (2) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(2) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
AI (5) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(5) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Best Practices (2) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(2) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
CLI (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Crypto (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Developer Productivity (2) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(2) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Engineering (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Event Destinations (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Getting Started (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Infrastructure (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
LLMs (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Meetup (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Partners (2) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(2) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Payments (4) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(4) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Tour (3) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(3) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Workflows (2) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(2) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Workshop (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

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

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○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
stripetour.com/berlin	Go
stripetour.com/paris	Go
stripetour.com/london	Go
www.meetup.com/stripe-london/events/313852834/	Go
www.meetup.com/stripe-paris/events/313537353/	Go
docs.stripe.com/	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

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

584 ms

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

831 ms

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

1 ms

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

0.002

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

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

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

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:18.179 source:map[column:3209 line:1 type:source-location url:https://stripe.dev/_next/static/chunks/0uvx_1ip89~4x.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:62.586 source:map[type:text value:[unattributed]]] map[reflowTime:12.089 source:map[column:134687 line:0 type:source-location url:https://stripe.dev/_next/static/chunks/0b29c3sj~k-mz.js urlProvider:network]] map[reflowTime:16.466 source:map[column:1373 line:0 type:source-location url:https://stripe.dev/_next/static/chunks/0t9t-9dsl2dxg.js urlProvider:network]] map[reflowTime:0.515 source:map[column:29098 line:0 type:source-location url:https://stripe.dev/_next/static/chunks/0wuvx6-x2fqhp.js urlProvider:network]] map[reflowTime:0.362 source:map[column:28122 line:0 type:source-location url:https://stripe.dev/_next/static/chunks/0wuvx6-x2fqhp.js urlProvider:network]] map[reflowTime:0.56 source:map[column:27748 line:0 type:source-location url:https://stripe.dev/_next/static/chunks/0wuvx6-x2fqhp.js urlProvider:network]] map[reflowTime:3.111 source:map[column:787 line:0 type:source-location url:https://plausible.io/js/script.outbound-links.tagged-events.js urlProvider:network]]]

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

value: No additional origins are good candidates for preconnecting

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
stripe.dev/fonts/Sohne.woff2	5.0 ms

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

Diagnostics

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

Estimated savings: 80 ms 227.0 KiB

URL	Transfer Size	Est Savings
stripe.dev/_next/static/chunks/04vp02y0.g70m.js	113.2 KiB	78.4 KiB
stripe.dev/_next/static/chunks/02-c.cxhqmdyv.js	51.4 KiB	51.1 KiB
stripe.dev/_next/static/chunks/16cer0h2fduw2.js	51.4 KiB	51.1 KiB
stripe.dev/_next/static/chunks/0b29c3sj~k-mz.js	52.4 KiB	23.3 KiB
stripe.dev/_next/static/chunks/0uvx_1ip89~4x.js	65.8 KiB	23.1 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	795 ms
Other	738 ms
Style & Layout	611 ms
Rendering	156 ms
Script Parsing & Compilation	26 ms
Garbage Collection	19 ms
Parse HTML & CSS	14 ms

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

URL	Time Spent
www.stripe.dev/	210 ms
stripe.dev/	0.0 ms

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Time to Interactive 0.9 s

●Max Potential First Input Delay 50 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 367 KiB

●User Timing marks and measures 7 user timings

●JavaScript execution time 0.8 s

●Avoid long main-thread tasks 1 long task found

●Avoid non-composited animations 3 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 150 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○LCP request discovery

Accessibility

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
Event (5) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(5) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Video (5) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(5) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Blog (10) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(10) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Agentic (2) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(2) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
AI (5) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(5) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Best Practices (2) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(2) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
CLI (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Crypto (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Developer Productivity (2) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(2) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Engineering (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Event Destinations (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
Getting Started (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Infrastructure (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
LLMs (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Meetup (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Partners (2) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(2) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Payments (4) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(4) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Tour (3) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(3) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Workflows (2) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(2) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`
Workshop (1) `ul.Filter-module__oRyX_G__list > li.Filter-module__oRyX_G__listItem > button.text-xs > span`
(1) `li.Filter-module__oRyX_G__listItem > button.text-xs > span > span.Filter-module__oRyX_G__count`

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●`[role]` values are valid

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

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

●Buttons have an accessible name

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

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

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

Link destination	Link Text
stripetour.com/berlin	Go
stripetour.com/paris	Go
stripetour.com/london	Go
www.meetup.com/stripe-london/events/313852834/	Go
www.meetup.com/stripe-paris/events/313537353/	Go
docs.stripe.com/	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

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.stripe.dev

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Best Practices

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Best Practices

SEO

Content Best Practices

Keyboard Shortcuts