stripe.com website review

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

Your mobile performance score is 46 (desktop: 67). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.7 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, reddit and Bing Ads and others), adding 983 KiB and 688 ms of main-thread time.

About 610 KiB of JavaScript is downloaded but never used on this page.

12 long tasks block the main thread while loading, the longest for 431 ms. During a long task the page ignores taps.

Your homepage downloads 3.3 MB in 178 requests on a phone: scripts 2.2 MB (110), images 703 KiB (26) and HTML 200 KiB (5). Under 2 MB keeps phones on slow connections fast.

The page has 2,698 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

5 images could be 208 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

14 files are served with short cache lifetimes, so returning visitors download them again (78 KiB).

Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report). Google uses this in ranking.

The page becomes fully interactive after 23.0 s. Good is under 3.8 s.

Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s.

Scripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.

Real visitors wait 221 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

The first text or image appears after 2.9 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.

34 visible links have no text or label, so screen readers cannot say where they go.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Elements with visible text labels do not have matching accessible names. (6 elements).

There are 2 <h1> headlines (“Financial infrastructure to grow your revenue. Ac…” and “Financial infrastructure to grow your revenue. Ac…”). One clear main headline is easier for people and search engines.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 161 pages on stripe.com and 29 external pages.

9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Minified React error #425; visit https://reactjs.org/docs/error-decoder.html?invariant=425 for the full…”.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,685 words of visible text.