Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:108.335 source:map[column:137980 line:1 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/framework-bfbcaa5a2903bc7d.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:73.613 source:map[type:text value:[unattributed]]] map[reflowTime:12.56 source:map[column:21574 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/38484-72a8319f943b4083.js urlProvider:network]] map[reflowTime:3.357 source:map[column:570689 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-d55238dd7cc28aa2.js urlProvider:network]] map[reflowTime:13.962 source:map[column:220485 line:387 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/index-b09b2ca44f5e5ddc.js urlProvider:network]] map[reflowTime:5.523 source:map[column:16493 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/38484-72a8319f943b4083.js urlProvider:network]] map[reflowTime:5.167 source:map[column:15635 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/38484-72a8319f943b4083.js urlProvider:network]] map[reflowTime:31.185 source:map[column:124944 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/index-b09b2ca44f5e5ddc.js urlProvider:network]] map[reflowTime:12.328 source:map[column:368623 line:393 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/index-b09b2ca44f5e5ddc.js urlProvider:network]] map[reflowTime:12.979 source:map[column:124556 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/pages/index-b09b2ca44f5e5ddc.js urlProvider:network]] map[reflowTime:0.665 source:map[column:6022 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/38484-72a8319f943b4083.js urlProvider:network]] map[reflowTime:2.992 source:map[column:2834 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/38484-72a8319f943b4083.js urlProvider:network]] map[reflowTime:4.459 source:map[column:3707 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/38484-72a8319f943b4083.js urlProvider:network]] map[reflowTime:4.704 source:map[column:46833 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/81888-44c041869848e4ee.js urlProvider:network]] map[reflowTime:67.557 source:map[column:22406 line:0 type:source-location url:https://b.stripecdn.com/mkt-ssr-statics/assets/_next/static/chunks/46687.21608bbbc5586ea3.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 398 ms

URL	Time Spent
stripe.com/	398 ms
stripe.com/en-nl	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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 217.8 KiB

URL	Transfer Size	Est Savings
/mkt-ssr-statics/assets/_next/static/chunks/pages/index-b...	233.5 KiB	105.8 KiB
/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-d5...	337.2 KiB	70.5 KiB
/mkt-ssr-statics/assets/_next/static/chunks/c67c952e-7f65...	55.8 KiB	41.5 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
/mkt-ssr-statics/assets/_next/static/chunks/50582.fb4a3d1...	28.7 s	427 ms	3.3 ms
/mkt-ssr-statics/assets/_next/static/chunks/framework-bfb...	1.5 s	755 ms	7.0 ms
Unattributable	558 ms	50 ms	0.0 ms
stripe.com/en-nl	556 ms	4.7 ms	0.3 ms
/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-d5...	343 ms	205 ms	106 ms
/mkt-ssr-statics/assets/_next/static/chunks/pages/index-b...	238 ms	155 ms	53 ms
/mkt-ssr-statics/assets/_next/static/chunks/46687.21608bb...	159 ms	88 ms	2.6 ms
/mkt-ssr-statics/assets/_next/static/chunks/38484-72a8319...	92 ms	3.3 ms	1.5 ms
/mkt-ssr-statics/assets/_next/static/chunks/81888-44c0418...	89 ms	78 ms	4.1 ms
/mkt-ssr-statics/assets/_next/static/chunks/webpack-504c4...	80 ms	76 ms	2.1 ms
/mkt-ssr-statics/assets/_next/static/chunks/main-df8f4439...	75 ms	64 ms	9.7 ms
/mkt-ssr-statics/assets/_next/static/chunks/c67c952e-7f65...	72 ms	62 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Other	29.1 s
Script Evaluation	2.1 s
Style & Layout	680 ms
Rendering	403 ms
Script Parsing & Compilation	251 ms
Garbage Collection	137 ms
Parse HTML & CSS	55 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,775 KiB

●User Timing marks and measures 4 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 51 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 160 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 40 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Accept and optimise payments globally – online and in person Pay Roastery Carts… `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 €0.01 per 1,000 units U… `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

●All heading elements contain content.

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

○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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
stripe.com/en-nl	`AbortError: The user aborted a request.`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
/mkt-ssr-statics/assets/_next/static/chunks/pages/index-b...
/mkt-ssr-statics/assets/_next/static/chunks/pages/_app-d5...

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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