www.mastercard.com/us/en.html speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 13:07 UTC. Grade B (80/100), with the screenshots, the timings and the fixes that matter.

https://www.mastercard.com/us/en.html

20 October 2026 at 13:07 UTC · Free test · report pt_ece9b9c6c783

Re-test this page Test your own site

Grade

80/100

Performance79/100

Structure82/100

13 audit(s) passed, 3 need work

First byte (TTFB)308 msmeasured from this server

Fully loaded6.23 sfirst byte + slowest asset

Requests26document + assets

Page weight50.8 KBcompressed transfer

HTML document25.3 KBgzip

ProtocolHTTP/3server not sent

Where the first byte went

DNS lookup 70 ms 23%
TCP connect 45 ms 15%
Server wait 194 ms 63%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 73% of 4,999 pages tested here308 ms against a median of 449 ms

Page weightlighter than 91% of 4,999 pages tested here50.8 KB against a median of 650.5 KB

Fully loadedslower than 96% of 4,999 pages tested here6.23 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

The first byte arrived in 308 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 50.8 KB over 26 request(s). Html files are 50% of it, so that one type is worth a look on its own.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 372 ms, inside the 2.5 s Google calls good.

Fix first: Render-blocking resources - Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint372 msgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking timenone over 50 mslong tasks during load

First contentful paint372 msfirst content on screen

Browser page weight541 B1 request(s), scripts included

Largest contentful paint372 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking timenone over 50 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Html 25 requests

25.4 KB 50%

Transfer size, compressed as sent. 26 request(s) in total, 50.8 KB across all of them.

Top issues

Render-blocking resources

high impact

13 render-blocking resource(s) in the document head (5 script(s), 8 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Cache static assets

medium impact

25 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Avoid extra redirects

medium impact

2 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.