Tools & Wizards About Us
stripe.net screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

stripe.net

Stripe | Financial Infrastructure to Grow Your Revenue

Page Load Speed

1.5 sec in total

First Response

29 ms

Resources Loaded

1.4 sec

Page Rendered

60 ms

stripe.net screenshot

About Website

Click here to check amazing Stripe content. Otherwise, check out these important facts you probably never knew about stripe.net

Stripe powers online and in-person payment processing and financial solutions for businesses of all sizes. Accept payments, send payouts, and automate financial processes with a suite of APIs and no-c...

Visit stripe.net

Key Findings

We analyzed Stripe.net page load time and found that the first response time was 29 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

stripe.net performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

stripe.net

29 ms

unsupported-browser

24 ms

csp-report

131 ms

imt-321ddd888ed5507e8a7d554c85032bf0.js

489 ms

csp-report

135 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Stripe.net, 88% (28 requests) were made to B.stripecdn.com and 9% (3 requests) were made to Stripe.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source B.stripecdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 50.9 kB (16%)

Content Size

327.7 kB

After Optimization

276.8 kB

  • HTML
  • Images

In fact, the total size of Stripe.net main page is 327.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. HTML takes 186.1 kB which makes up the majority of the site volume.

HTML Optimization

-27%

Potential reduce by 50.9 kB

  • Original 186.1 kB
  • After minification 184.6 kB
  • After compression 135.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 50.9 kB or 27% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 141.5 kB
  • After minification 141.5 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Stripe images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 26 (93%)

Requests Now

28

After Optimization

2

  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stripe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

stripe.net

stripe.net

29 ms

unsupported-browser

unsupported-browser

24 ms

csp-report

csp-report

131 ms

imt-321ddd888ed5507e8a7d554c85032bf0.js

imt-321ddd888ed5507e8a7d554c85032bf0.js

489 ms

csp-report

csp-report

135 ms

UnsupportedBrowserPage-73ff6ec94c0bfe11e4a1.css

UnsupportedBrowserPage-73ff6ec94c0bfe11e4a1.css

49 ms

UserLogo-db4fd9efb1cd1e6216f8.css

UserLogo-db4fd9efb1cd1e6216f8.css

44 ms

Initializer-7facc0b5de1e73f92137.css

Initializer-7facc0b5de1e73f92137.css

45 ms

fonts-a70ed7590dd21c01585a.css

fonts-a70ed7590dd21c01585a.css

45 ms

global-8ca0a9592606523e1cb7.css

global-8ca0a9592606523e1cb7.css

412 ms

White-df12e51ea0a7d9b2eb34.css

White-df12e51ea0a7d9b2eb34.css

401 ms

Light-9368a9539c96fea619c8.css

Light-9368a9539c96fea619c8.css

522 ms

Dark-fddc492b8e662fca734e.css

Dark-fddc492b8e662fca734e.css

397 ms

SemiDark-c360011f6a51855455a7.css

SemiDark-c360011f6a51855455a7.css

430 ms

Transparent-bdd8e13604d56721da9e.css

Transparent-bdd8e13604d56721da9e.css

400 ms

Hub-7c3578182c0f91dde4a1.css

Hub-7c3578182c0f91dde4a1.css

404 ms

Legacy-ffa4f24cd3ca18798c6a.css

Legacy-ffa4f24cd3ca18798c6a.css

838 ms

LegacyLight-c4964a08822288e5ca89.css

LegacyLight-c4964a08822288e5ca89.css

407 ms

LegacyDark-d19fb27941422687f6e0.css

LegacyDark-d19fb27941422687f6e0.css

411 ms

Chroma-87787f8a17a7694cc56b.css

Chroma-87787f8a17a7694cc56b.css

792 ms

CottonCandy-34902095724678b38c34.css

CottonCandy-34902095724678b38c34.css

737 ms

LemonLime-13ff3a38b624e377a552.css

LemonLime-13ff3a38b624e377a552.css

758 ms

Overcast-81fe349430811fb7e7a0.css

Overcast-81fe349430811fb7e7a0.css

879 ms

Perennial-854f0de6b75daa0af865.css

Perennial-854f0de6b75daa0af865.css

523 ms

Pomegranate-41bf31c2ab13e3303495.css

Pomegranate-41bf31c2ab13e3303495.css

894 ms

Slate-bc2bc8abf6c1a4bdaaf9.css

Slate-bc2bc8abf6c1a4bdaaf9.css

740 ms

Sunburst-a883cb3d33b1332bbc9a.css

Sunburst-a883cb3d33b1332bbc9a.css

743 ms

Sunset-852ef64feef5cc52c82c.css

Sunset-852ef64feef5cc52c82c.css

746 ms

Tropical-4894817f3839a23051cc.css

Tropical-4894817f3839a23051cc.css

1113 ms

Twilight-4cf03cc2b6b49192800f.css

Twilight-4cf03cc2b6b49192800f.css

1163 ms

Wintergreen-2a184b526d0f98be2716.css

Wintergreen-2a184b526d0f98be2716.css

1161 ms

Layout-2fe3591ea951e6ccab8e.css

Layout-2fe3591ea951e6ccab8e.css

1179 ms

Accessibility Review

stripe.net accessibility score

95

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

stripe.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

stripe.net SEO score

99

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stripe.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Stripe.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

stripe.net

Open Graph description is not detected on the main page of Stripe. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: