5.2 sec in total
442 ms
3.8 sec
997 ms
Click here to check amazing Transpay content for United States. Otherwise, check out these important facts you probably never knew about transpay.com
Mastercard Cross-Border Services enable seamless, secure and certain international payments for people and businesses through a single connection with global reach.
Visit transpay.comWe analyzed Transpay.com page load time and found that the first response time was 442 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
transpay.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value12.4 s
0/100
25%
Value10.6 s
7/100
10%
Value610 ms
49/100
30%
Value0
100/100
15%
Value10.2 s
25/100
10%
442 ms
627 ms
213 ms
92 ms
134 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Transpay.com, 5% (3 requests) were made to Cdn.cookielaw.org and 3% (2 requests) were made to I.vimeocdn.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source B2b.mastercard.com.
Page size can be reduced by 114.3 kB (10%)
1.1 MB
988.0 kB
In fact, the total size of Transpay.com main page is 1.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 941.6 kB which makes up the majority of the site volume.
Potential reduce by 59.0 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 19.3 kB, which is 28% 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 59.0 kB or 84% of the original size.
Potential reduce by 37.4 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. Transpay images are well optimized though.
Potential reduce by 33 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 17.9 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. Transpay.com needs all CSS files to be minified and compressed as it can save up to 17.9 kB or 21% of the original size.
Number of requests can be reduced by 5 (12%)
43
38
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Transpay. 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.
crossborder.mastercard.com
442 ms
627 ms
index.css
213 ms
otSDKStub.js
92 ms
launch-10d5801d5aa0.min.js
134 ms
index.js
905 ms
c343750e-331b-4b6b-b16f-d6665c9644ab.json
426 ms
718220608
1008 ms
04de697c539b4b2c7e48c2d882a5a5cd.svg
503 ms
5226ebb5f1ea444a8d99277bd4cb1217.svg
1070 ms
1280x720_cross_border.jpg
1170 ms
hero_cross_border.jpg
1596 ms
33e427025b3bcb89cc753c23c9c0131b.svg
1073 ms
1280x720_xbs_homesend.jpg
1120 ms
xbs_reach.png
1072 ms
xbs_revenue.png
1118 ms
xbs_simplify.png
1117 ms
1280x720_women_with_whiteboard.jpg
1123 ms
1920x1080_family_at_home.jpg
1120 ms
1920x1080_video_call.jpg
1125 ms
1920x1080_woman_in_office.jpg
1299 ms
xbs_consumers-2x.png
1164 ms
xbs_businesses-2x.png
1296 ms
xbs_governments-2x.png
1297 ms
tile_xbs_factsheet.jpg
1297 ms
tile_xbs_infographic.jpg
1297 ms
tile_xbs_infographic_b2b.jpg
1520 ms
tile_xbs_infographic_b2p.jpg
1518 ms
tile_xbs_infographic_p2p.jpg
1517 ms
1280x720_mockup_borderless_report.jpg
1515 ms
1920x1080_woman_holding_phone.jpg
1516 ms
1920x1080_man_with_laptop.jpg
1546 ms
mc_symbol-is.svg
1543 ms
f97629b920204e6393712010af281c43.svg
1539 ms
4f3c62840d2685bdc3a92efc0e389ffa.svg
1541 ms
8f24818099c6ba1a32b694039deb3fc6.svg
1525 ms
ca37b7ecf5bafc4f3fb7fa68d35bfcb7.svg
2132 ms
839396d6c409e1b68f445af5a1466014.svg
2134 ms
mc_symbol-is.svg
2114 ms
location
65 ms
eaa74dbd55ef440ab4fbaab43797f25a.woff
1819 ms
470b6539438983dc78934b0d92283ad0.woff
1817 ms
5e6a1aaa993af0afeb6e82a025d16989.woff
1818 ms
ad9269d6c3bc1adb3d1f9f18182ba7a5.woff
1818 ms
otBannerSdk.js
29 ms
07881392d47c49afff72519abc78a70c.woff
1658 ms
1447075161-4ef1a1d6c3ac2c22cfc9f8a783e865799455c1137b2afd7860ded9e548345e20-d.jpg
379 ms
player.js
656 ms
player.css
581 ms
cff07fbbd29551a22412af8fda248902.woff
1188 ms
f454f4e5dcf998a87edc599efc598996.woff
1093 ms
b419c2f98c55dd1f5c618c6bd917cb03.woff
1088 ms
f9bd46cb29b1dd0926086296179e4546.woff
1047 ms
63cce5e823a773d607b4cb1345adfd2e.woff
1049 ms
0a840b32b597e66d3783cc3828aeea7b.woff
1045 ms
46bcb867c73d353836fdc443f0a656ca.woff
1045 ms
dd431996246699aef84383537c50d40a.woff
1045 ms
48a82cb58989a99125694d0e343860d4.woff
1044 ms
62ac0f109d41d77d8ebb9aabdd871ed1.woff
1002 ms
48fce7776ce5f9d6b574e8d569e36527.woff
1000 ms
7bfd58808f9d3025fd6b3b8749c38f51.woff
872 ms
3cb7050ba25c42d8fa176c4f65dbd2c1.woff
872 ms
1447075161-4ef1a1d6c3ac2c22cfc9f8a783e865799455c1137b2afd7860ded9e548345e20-d
181 ms
transpay.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
<object> elements do not have alternate text
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
transpay.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
transpay.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Transpay.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 Transpay.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.
transpay.com
Open Graph data is detected on the main page of Transpay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: