B — https://stripe.com | BeaverCheck Audit

Site Health

Score: 80 / 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)

28 link(s) with no accessible text

Accessibility › Link & Button Quality

9 image-only link(s) without alt text

Accessibility › Link & Button Quality

112 HTTP requests — consider bundling or reducing

Performance › Page Weight Budget

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

External link from b.stripecdn.com lacks integrity attribute

Security › Subresource Integrity

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fstripe.com)](https://beavercheck.com/results/833fc927-ecc5-466b-ae1d-0e3f33ca1416)

HTML

<a href="https://beavercheck.com/results/833fc927-ecc5-466b-ae1d-0e3f33ca1416"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fstripe.com" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

100

Accessibility

100

Best Practices

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

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

6.32 s

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

88.31 s

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

0.028

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

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

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

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:39.617 source:map[column:93630 line:1 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/framework-9f89521118404fe7.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:2.019 source:map[column:14555 line:433 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/index-6d8874e6de5710a3.js urlProvider:network]] map[reflowTime:1.51 source:map[column:194818 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-889d57bc5e09f072.js urlProvider:network]] map[reflowTime:10.984 source:map[column:173546 line:387 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/index-6d8874e6de5710a3.js urlProvider:network]] map[reflowTime:13.587 source:map[column:12075 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/48015-dee80f6e96192d69.js urlProvider:network]] map[reflowTime:3.787 source:map[column:7133 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/65223-1423d8e6ad8de9bf.js urlProvider:network]] map[reflowTime:5.145 source:map[column:17295 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/50727-f89548bdd553ee4d.js urlProvider:network]] map[reflowTime:39.617 source:map[column:73494 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/84246.854c27f9d542172f.js urlProvider:network]] map[reflowTime:13.302 source:map[type:text value:[unattributed]]]]

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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

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

	URL	Resource Size	Est Savings
div.dom-graphic__content > div.payments-graphic__terminal > picture.payments-graphic__terminal-image > img `div.dom-graphic__content > div.payments-graphic__terminal > picture.payments-graphic__terminal-image > img`	/fzn2n1nzq965/1Vf8oT9Fm6dEwpnEx5PgK1/055956f38d7fd8b0cc74...	67.9 KiB	24.9 KiB

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

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

TTI

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

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

Estimated savings: 1.2 s

URL	Time Spent
stripe.com/	1.2 s
stripe.com/en-br	0.0 ms

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

URL	Transfer Size	Est Savings
/mkt-ssr-statics/assets/_next/static/chunks/pages/index-6...	217.6 KiB	103.3 KiB
/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-88...	393.5 KiB	79.8 KiB
/mkt-ssr-statics/assets/_next/static/chunks/c67c952e-7f65...	56.7 KiB	43.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 reduce Javascript execution time.

URL	Total CPU Time	Script Evaluation	Script Parse
/mkt-ssr-statics/assets/_next/static/chunks/50582.fb4a3d1...	112.6 s	2.4 s	11 ms
/mkt-ssr-statics/assets/_next/static/chunks/framework-9f8...	3.1 s	2.3 s	57 ms
Unattributable	2.5 s	170 ms	0.0 ms
stripe.com/en-br	2.3 s	11 ms	0.6 ms
/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-88...	949 ms	562 ms	316 ms
/mkt-ssr-statics/assets/_next/static/chunks/pages/index-6...	625 ms	382 ms	129 ms
/mkt-ssr-statics/assets/_next/static/chunks/84246.854c27f...	434 ms	257 ms	17 ms
/mkt-ssr-statics/assets/_next/static/chunks/65223-1423d8e...	384 ms	12 ms	1.2 ms
/mkt-ssr-statics/assets/_next/static/chunks/53261-9c921aa...	262 ms	234 ms	8.4 ms
/mkt-ssr-statics/assets/_next/static/chunks/c67c952e-7f65...	220 ms	189 ms	30 ms
/mkt-ssr-statics/assets/_next/static/chunks/webpack-e1dfb...	161 ms	150 ms	6.4 ms
/mkt-ssr-statics/assets/_next/static/chunks/main-d0d9d441...	155 ms	114 ms	40 ms
/mkt-ssr-statics/assets/_next/static/chunks/32318-fc68996...	81 ms	30 ms	9.1 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	111.7 s
Script Evaluation	7.1 s
Style & Layout	2.3 s
Rendering	2.0 s
Script Parsing & Compilation	779 ms
Garbage Collection	444 ms
Parse HTML & CSS	123 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

●Font display

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 1,900 KiB

●User Timing marks and measures 4 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 42 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 190 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 180 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
Accept and optimize payments globally—online and in person Pay Roastery Cartsy … `div.modular-solutions-bento > div.modular-solutions-bento__content > div.modular-solutions-bento__layout > button.modular-solutions-bento-card`
Enable any billing model Pro Plan Billed monthly Tokens R$0.05 per 1,000 units … `div.modular-solutions-bento > div.modular-solutions-bento__content > div.modular-solutions-bento__layout > button.modular-solutions-bento-card`
Read the story `div#customer-Hertz > div#detail-customer-content-Hertz > div.customer-stories__customer-content--read > a#customer-content-Hertz`
Read the story `div#customer-URBN > div#detail-customer-content-URBN > div.customer-stories__customer-content--read > a#customer-content-URBN`
Read the story `div#customer-Instacart > div#detail-customer-content-Instacart > div.customer-stories__customer-content--read > a#customer-content-Instacart`
Read the story `div#customer-LeMonde > div#detail-customer-content-LeMonde > div.customer-stories__customer-content--read > a#customer-content-LeMonde`

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

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

●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

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

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

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

○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

General

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.

URL
/mkt-ssr-statics/assets/_next/static/chunks/pages/index-6...
/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-88...

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate 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
stripe.com/en-br/blog/introducing-our-agentic-commerce-solutions	Read more
stripe.com/en-br/blog/introducing-our-agentic-commerce-solutions	Read 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

100

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.

1.64 s

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

2.05 s

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

22.18 s

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

0.015

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

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

32.44 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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

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

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:69.098 source:map[column:137948 line:1 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/framework-9f89521118404fe7.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:45.262 source:map[type:text value:[unattributed]]] map[reflowTime:3.461 source:map[column:14555 line:433 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/index-6d8874e6de5710a3.js urlProvider:network]] map[reflowTime:2.27 source:map[column:194818 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-889d57bc5e09f072.js urlProvider:network]] map[reflowTime:10.711 source:map[column:173546 line:387 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/index-6d8874e6de5710a3.js urlProvider:network]] map[reflowTime:7.927 source:map[column:12075 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/48015-dee80f6e96192d69.js urlProvider:network]] map[reflowTime:18.323 source:map[column:7133 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/65223-1423d8e6ad8de9bf.js urlProvider:network]] map[reflowTime:8.303 source:map[column:368675 line:393 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/index-6d8874e6de5710a3.js urlProvider:network]] map[reflowTime:8.794 source:map[column:127701 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/index-6d8874e6de5710a3.js urlProvider:network]] map[reflowTime:0.427 source:map[column:2501 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/48015-dee80f6e96192d69.js urlProvider:network]] map[reflowTime:3.314 source:map[column:3718 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/48015-dee80f6e96192d69.js urlProvider:network]] map[reflowTime:28.057 source:map[column:3868 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/48015-dee80f6e96192d69.js urlProvider:network]] map[reflowTime:5.714 source:map[column:193812 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-889d57bc5e09f072.js urlProvider:network]] map[reflowTime:3.365 source:map[column:1416 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/65223-1423d8e6ad8de9bf.js urlProvider:network]] map[reflowTime:42.371 source:map[column:73494 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/84246.854c27f9d542172f.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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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

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

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

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

Estimated savings: 650 ms

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

Estimated savings: 70 ms 225.0 KiB

URL	Transfer Size	Est Savings
/mkt-ssr-statics/assets/_next/static/chunks/pages/index-6...	217.6 KiB	103.1 KiB
/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-88...	393.5 KiB	79.8 KiB
/mkt-ssr-statics/assets/_next/static/chunks/c67c952e-7f65...	56.7 KiB	42.2 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
/mkt-ssr-statics/assets/_next/static/chunks/50582.fb4a3d1...	30.2 s	438 ms	3.2 ms
/mkt-ssr-statics/assets/_next/static/chunks/framework-9f8...	1.1 s	548 ms	7.7 ms
Unattributable	421 ms	35 ms	0.0 ms
stripe.com/en-br	390 ms	3.0 ms	0.2 ms
/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-88...	241 ms	145 ms	78 ms
/mkt-ssr-statics/assets/_next/static/chunks/pages/index-6...	161 ms	105 ms	34 ms
/mkt-ssr-statics/assets/_next/static/chunks/84246.854c27f...	103 ms	57 ms	3.1 ms
/mkt-ssr-statics/assets/_next/static/chunks/48015-dee80f6...	63 ms	3.3 ms	0.6 ms
/mkt-ssr-statics/assets/_next/static/chunks/53261-9c921aa...	61 ms	56 ms	2.2 ms
/mkt-ssr-statics/assets/_next/static/chunks/c67c952e-7f65...	54 ms	46 ms	7.4 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	30.3 s
Script Evaluation	1.6 s
Style & Layout	540 ms
Rendering	318 ms
Script Parsing & Compilation	195 ms
Garbage Collection	91 ms
Parse HTML & CSS	42 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

●Font display

●Improve image delivery

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 1,830 KiB

●User Timing marks and measures 4 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 59 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 190 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

100

Accessibility

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
Accept and optimize payments globally—online and in person Pay Roastery Cartsy … `div.modular-solutions-bento > div.modular-solutions-bento__content > div.modular-solutions-bento__layout > button.modular-solutions-bento-card`
Enable any billing model Pro Plan Billed monthly Tokens R$0.05 per 1,000 units … `div.modular-solutions-bento > div.modular-solutions-bento__content > div.modular-solutions-bento__layout > button.modular-solutions-bento-card`
Read the story `div#customer-Hertz > div.customer-stories__customer-summary > div.customer-stories__customer-summary-action > a.hds-button`

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

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

●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

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

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

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

○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
stripe.com/en-br	`AbortError: The user aborted a request.`

URL
/mkt-ssr-statics/assets/_next/static/chunks/pages/index-6...
/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-88...

●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

Content Best Practices

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

Link destination	Link Text
stripe.com/en-br/blog/introducing-our-agentic-commerce-solutions	Read more
stripe.com/en-br/blog/introducing-our-agentic-commerce-solutions	Read 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`

Results for https://stripe.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

General

SEO

Content Best Practices

Keyboard Shortcuts