Tools & Wizards About Us

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

transpay.com

Cross-Border Services — International payment solutions | Mastercard

Page Load Speed

5.2 sec in total

First Response

442 ms

Resources Loaded

3.8 sec

Page Rendered

997 ms

About Website

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

Key Findings

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

Performance Metrics

transpay.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

crossborder.mastercard.com

442 ms

627 ms

index.css

213 ms

otSDKStub.js

92 ms

launch-10d5801d5aa0.min.js

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 Optimization Overview & Recommendations

Page size can be reduced by 114.3 kB (10%)

Content Size

1.1 MB

After Optimization

988.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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.

HTML Optimization

-84%

Potential reduce by 59.0 kB

  • Original 70.0 kB
  • After minification 50.7 kB
  • After compression 11.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.

Image Optimization

-4%

Potential reduce by 37.4 kB

  • Original 941.6 kB
  • After minification 904.2 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.

JavaScript Optimization

-0%

Potential reduce by 33 B

  • Original 7.2 kB
  • After minification 7.2 kB
  • After compression 7.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-21%

Potential reduce by 17.9 kB

  • Original 83.5 kB
  • After minification 83.5 kB
  • After compression 65.6 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.

Requests Breakdown

Number of requests can be reduced by 5 (12%)

Requests Now

43

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

transpay.com accessibility score

74

Accessibility Issues

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

High

<object> elements do not have alternate text

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

transpay.com best practices score

92

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

SEO Factors

transpay.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

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

Social Sharing Optimization

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: