Tools & Wizards About Us
stripe.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

stripe.com

Stripe | Financial Infrastructure to Grow Your Revenue

Page Load Speed

2.5 sec in total

First Response

209 ms

Resources Loaded

2.1 sec

Page Rendered

142 ms

stripe.com screenshot

About Website

Welcome to stripe.com homepage info - get ready to check Stripe best content for United States right away, or after learning these important things about stripe.com

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

Key Findings

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

Performance Metrics

stripe.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value1,680 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

stripe.com

209 ms

stripe.com

408 ms

fonts.css

33 ms

shared-site-5cf0b4bc08a2cfbfaa38a170187fb3d7.css

86 ms

home-32bbd448df17f656d8b9eccad4307b56.css

170 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 68% of them (48 requests) were addressed to the original Stripe.com, 11% (8 requests) were made to and 6% (4 requests) were made to Api.mixpanel.com. The less responsive or slowest element that took the longest time to load (697 ms) belongs to the original domain Stripe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 232.0 kB (36%)

Content Size

638.3 kB

After Optimization

406.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stripe.com main page is 638.3 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. 30% of websites need less resources to load. CSS take 292.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 22.9 kB

  • Original 27.6 kB
  • After minification 21.9 kB
  • After compression 4.7 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. This page needs HTML code to be minified as it can gain 5.6 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.9 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 603 B

  • Original 143.3 kB
  • After minification 142.7 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.

JavaScript Optimization

-50%

Potential reduce by 87.5 kB

  • Original 175.1 kB
  • After minification 175.1 kB
  • After compression 87.6 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 87.5 kB or 50% of the original size.

CSS Optimization

-41%

Potential reduce by 120.9 kB

  • Original 292.3 kB
  • After minification 290.7 kB
  • After compression 171.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Stripe.com needs all CSS files to be minified and compressed as it can save up to 120.9 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (68%)

Requests Now

60

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 60 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 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

stripe.com

stripe.com

209 ms

stripe.com

stripe.com

408 ms

fonts.css

fonts.css

33 ms

shared-site-5cf0b4bc08a2cfbfaa38a170187fb3d7.css

shared-site-5cf0b4bc08a2cfbfaa38a170187fb3d7.css

86 ms

home-32bbd448df17f656d8b9eccad4307b56.css

home-32bbd448df17f656d8b9eccad4307b56.css

170 ms

shared-site-68b6ee96f2b06c9ee69778bf0979b5fb.js

shared-site-68b6ee96f2b06c9ee69778bf0979b5fb.js

338 ms

home-d26b1e66477edf3e7fb7f4f4d80540ee.js

home-d26b1e66477edf3e7fb7f4f4d80540ee.js

348 ms

analytics.min.js

analytics.min.js

108 ms

switcheroo.js

switcheroo.js

126 ms

analytics.js

analytics.js

146 ms

C672BF92C8D3E5E02.css

C672BF92C8D3E5E02.css

697 ms

logo-white.png

logo-white.png

97 ms

arrow.png

arrow.png

108 ms

phones.png

phones.png

347 ms

phone.png

phone.png

107 ms

blue.png

blue.png

108 ms

card.png

card.png

177 ms

tag.png

tag.png

190 ms

web_mobile.png

web_mobile.png

188 ms

kickstarter.png

kickstarter.png

190 ms

twitter.png

twitter.png

260 ms

instacart.png

instacart.png

277 ms

shopify.png

shopify.png

282 ms

pinterest.png

pinterest.png

283 ms

lyft.png

lyft.png

342 ms

us.png

us.png

366 ms

au.png

au.png

374 ms

ca.png

ca.png

373 ms

dk.png

dk.png

380 ms

fi.png

fi.png

425 ms

gb.png

gb.png

429 ms

ie.png

ie.png

454 ms

no.png

no.png

466 ms

se.png

se.png

466 ms

at.png

at.png

473 ms

be.png

be.png

507 ms

br.png

br.png

512 ms

fr.png

fr.png

544 ms

de.png

de.png

555 ms

it.png

it.png

556 ms

jp.png

jp.png

563 ms

lu.png

lu.png

590 ms

mx.png

mx.png

596 ms

nl.png

nl.png

631 ms

pt.png

pt.png

646 ms

sg.png

sg.png

645 ms

mixpanel-2.2.min.js

mixpanel-2.2.min.js

48 ms

analytics.js

analytics.js

102 ms

q.stripe.com

q.stripe.com

334 ms

t.stripe.com

t.stripe.com

321 ms

es.png

es.png

593 ms

q.stripe.com

q.stripe.com

355 ms

pfwFtqxCCQ==

pfwFtqxCCQ==

7 ms

xtMLT43+l+A1lB0H1

xtMLT43+l+A1lB0H1

6 ms

5XyF0RdQe0=

5XyF0RdQe0=

6 ms

h+BwTyOhxUwrXgMnKTM671onvZB8oOPTInvMetzK+PyKpxWeHf8r5S+FsUH9

h+BwTyOhxUwrXgMnKTM671onvZB8oOPTInvMetzK+PyKpxWeHf8r5S+FsUH9

5 ms

pfgNZQdB9Q==

pfgNZQdB9Q==

5 ms

AW2rEIJ

AW2rEIJ

4 ms

5XyF0RdQe0=

5XyF0RdQe0=

4 ms

yvlL4WxQf0=

yvlL4WxQf0=

4 ms

91 ms

87 ms

86 ms

86 ms

ch.png

ch.png

576 ms

nav-white.png

nav-white.png

582 ms

arrow_bottom.png

arrow_bottom.png

620 ms

check.png

check.png

638 ms

collect

collect

29 ms

collect

collect

61 ms

arrow.png

arrow.png

571 ms

Accessibility Review

stripe.com accessibility score

97

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.

Best Practices

stripe.com 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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

stripe.com SEO score

98

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

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: