Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

mastercard.de

Mastercard - Ein globales Technologieunternehmen in der Zahlungsverkehrsbranche

Page Load Speed

651 ms in total

First Response

179 ms

Resources Loaded

472 ms

Page Rendered

0 ms

mastercard.de screenshot

About Website

Welcome to mastercard.de homepage info - get ready to check Mastercard best content for Germany right away, or after learning these important things about mastercard.de

Wir verbinden und fördern eine integrative, digitale Wirtschaft, von der Menschen, Unternehmen und Regierungen weltweit profitieren, indem wir Transaktionen sicher, einfach und zugänglich machen.

Visit mastercard.de

Key Findings

We analyzed Mastercard.de page load time and found that the first response time was 179 ms and then it took 472 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

mastercard.de performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value1.958

0/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

de-de.html

179 ms

skip-to-content-clientlibs.css

27 ms

clientlib-base.js

26 ms

otSDKStub.js

38 ms

launch-EN5f9e0c4944554f7e9f3947196ae7c30f.min.js

30 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 33% of them (3 requests) were addressed to the original Mastercard.de, 33% (3 requests) were made to Cdn.cookielaw.org and 11% (1 request) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (179 ms) belongs to the original domain Mastercard.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 71.2 kB (25%)

Content Size

286.1 kB

After Optimization

214.9 kB

In fact, the total size of Mastercard.de main page is 286.1 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 5% of websites need less resources to load. Javascripts take 203.1 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 71.0 kB

  • Original 82.5 kB
  • After minification 81.0 kB
  • After compression 11.5 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 71.0 kB or 86% of the original size.

JavaScript Optimization

-0%

Potential reduce by 101 B

  • Original 203.1 kB
  • After minification 203.1 kB
  • After compression 203.0 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

-27%

Potential reduce by 131 B

  • Original 484 B
  • After minification 484 B
  • After compression 353 B

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. Mastercard.de needs all CSS files to be minified and compressed as it can save up to 131 B or 27% of the original size.

Requests Breakdown

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

Requests Now

8

After Optimization

3

The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mastercard. 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.

Accessibility Review

mastercard.de accessibility score

99

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

SEO Factors

mastercard.de SEO score

92

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

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mastercard.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Mastercard.de 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 Mastercard. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: