3.2 sec in total
180 ms
2.7 sec
349 ms
Click here to check amazing Status Braintree Pay Ments content for United States. Otherwise, check out these important facts you probably never knew about status.braintreepayments.com
Welcome to Braintree's home for real-time and historical data on system performance.
Visit status.braintreepayments.comWe analyzed Status.braintreepayments.com page load time and found that the first response time was 180 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
status.braintreepayments.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value7.9 s
3/100
25%
Value8.9 s
15/100
10%
Value360 ms
72/100
30%
Value0.003
100/100
15%
Value8.1 s
41/100
10%
180 ms
504 ms
87 ms
103 ms
122 ms
Our browser made a total of 20 requests to load all elements on the main page. We found that 10% of them (2 requests) were addressed to the original Status.braintreepayments.com, 50% (10 requests) were made to Dka575ofm4ao0.cloudfront.net and 25% (5 requests) were made to Braintreepayments.com. The less responsive or slowest element that took the longest time to load (644 ms) relates to the external source Braintreepayments.com.
Page size can be reduced by 588.2 kB (73%)
801.7 kB
213.5 kB
In fact, the total size of Status.braintreepayments.com main page is 801.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. 45% of websites need less resources to load. Javascripts take 523.2 kB which makes up the majority of the site volume.
Potential reduce by 66.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. 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 66.7 kB or 84% of the original size.
Potential reduce by 488 B
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. Status Braintree Pay Ments images are well optimized though.
Potential reduce by 377.7 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 377.7 kB or 72% of the original size.
Potential reduce by 143.2 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. Status.braintreepayments.com needs all CSS files to be minified and compressed as it can save up to 143.2 kB or 85% of the original size.
Number of requests can be reduced by 5 (50%)
10
5
The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Status Braintree Pay Ments. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
status.braintreepayments.com
180 ms
status.braintreepayments.com
504 ms
status_manifest-1c3325ccf30b57a90dca94da7927ab51.css
87 ms
jquery.min.js
103 ms
external20151021-13919-7slizn.css
122 ms
status_manifest-6d96635085126aa58b54a332c3f414ca.js
125 ms
status_common-1f5b86558b21e255b433fe238f5a2217.js
123 ms
register_subscription_form-272b117f6e1a62978a041a8a105d1746.js
123 ms
status_idle-3871f6744d77f95a26f818e4264c70b3.js
116 ms
idf46IirS9iUNKDEPmCB
196 ms
bt_mono-Regular.svg
644 ms
ProximaNovaRegular.woff
28 ms
ProximaNovaSemibold.woff
42 ms
ProximaNovaLight.woff
26 ms
ProximaNovaBold.woff
20 ms
939cba03-5b40-4d01-9bc5-7589eca863db.woff
546 ms
849bc5b9-a2ff-4343-977b-26ba8bd24a60.ttf
571 ms
bt_mono-Regular.woff
628 ms
f67fa3b5-c1d1-488f-8e60-a828b9ad56a4.svg
485 ms
nr-885.min.js
99 ms
status.braintreepayments.com accessibility score
status.braintreepayments.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
status.braintreepayments.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
Document uses legible font sizes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Status.braintreepayments.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Status.braintreepayments.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.
status.braintreepayments.com
Open Graph description is not detected on the main page of Status Braintree Pay Ments. 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: