Skip to content
Audit Complete

Results for https://mastercard.us

Visit site
US · USD ($) · Estimated Applicable regulations: CCPA/CPRA · ADA Title III Dev cost: $100/hr How jurisdiction is detected
Netherlands Netherlands · Amsterdam Completed: Apr 22, 2026 23:25 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
D68

Site Health

Score: 68 / 100

Based on 8 categories, 0 sections

Room to improve — your 136.7s load time is above Google's 2.5s 'Good' threshold.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Several regulatory requirements are not yet met.

Missing metadata means poor previews on social media and search.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Facebook · 1367 peers
You 68
·
Avg 72
At average
0 50 100
Better than 4% of Facebook sites See full Facebook benchmark →
HSTS · 2211 peers
You 68
·
Avg 74
-6 below average
0 50 100
Better than 2% of HSTS sites See full HSTS benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
3

Page weighs 78.6 MB (73.5 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
4

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure
5

No favicon or icon links detected

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Favicon & Branding
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fmastercard.us)](https://beavercheck.com/results/321a26d1-23d8-4ce3-85f4-4d1af4a064d5)
<a href="https://beavercheck.com/results/321a26d1-23d8-4ce3-85f4-4d1af4a064d5"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmastercard.us" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fmastercard.us

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 136.7s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.
Your LCP is 136.7s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
2 accessibility issues exclude users who rely on assistive technology.
C
Could reach Estimate based on resolving critical issues

Conversion Barriers

3 critical 6 warning

9 barrier(s) likely increasing bounce by ~38%.

Speed (2)

Page takes 136.7s to load

+12% bounce

Users abandon at ~3s — you're 134.2s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 3.0s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

No viewport meta tag

+15% bounce

Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature

Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">

Content (4)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$600 investment → $18/month returns + USD 157,500 risk avoided

Payback period: > 2 years First-year ROI: -63%

Investment

$600

6h · 5 findings

Monthly returns

$18 /mo

~$222 / year

  • Bandwidth savings $18

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

$100 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$600

6.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$100 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,143 / month at risk

~$157,722 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+4 more

Bandwidth Waste

$18 /mo

231190.4 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~23.1 MB per page load
    Saves $18/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

26
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
99
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
82
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

5.76 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

136.72 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

3.05 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.015

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

52.45 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

137.18 s

Detailed Report

Audit breakdown by category with detailed findings.

26

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/adobe/dynamicmedia/deliver/dm-aid--d46becfe-4262-4e2c-9c...600.0 s23.2 MiB
/adobe/dynamicmedia/deliver/dm-aid--c471b0a1-c241-4d00-ac...600.0 s23.0 MiB
/adobe/dynamicmedia/deliver/dm-aid--01abe707-fcd0-4c1d-a9...600.0 s969.0 KiB
/adobe/dynamicmedia/deliver/dm-aid--c63c505c-a6b9-4cae-9f...600.0 s269.4 KiB
/adobe/dynamicmedia/deliver/dm-aid--bcd71f82-2c43-4641-a3...600.0 s138.8 KiB
www.mastercard.com/rysmLZ/l7F/tV8/4hUmLK2S/iYEYX4r97Oucr2Oz/IhkYIg/ShUxeHpN/GkkB21600.0 s174.9 KiB
/adobe/dynamicmedia/deliver/dm-aid--9c3a3e49-0fb7-4f02-b5...600.0 s113.1 KiB
/adobe/dynamicmedia/deliver/dm-aid--cb42b726-9398-4633-93...600.0 s98.9 KiB
assets.adobedtm.com/acdc00762da2/83bdb98d95f8/launch-05f4b8356cc4.min.js3600.0 s89.2 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99...499771.0 s469.6 KiB
/adobe/dynamicmedia/deliver/dm-aid--d73a04ae-35f0-47ff-97...600.0 s62.3 KiB
cdn.cookielaw.org/scripttemplates/202604.1.0/otBannerSdk.js86400.0 s131.0 KiB
/adobe/dynamicmedia/deliver/dm-aid--31deb226-0992-429e-8f...600.0 s48.7 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site/resources...86400.0 s107.5 KiB
/etc.clientlibs/algolia/clientlibs/clientlib-site.lc-39e1...499771.0 s255.1 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site/resources...86400.0 s36.5 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site/resources...86400.0 s36.0 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site/resources...86400.0 s35.7 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site.lc-bf9c32...499770.0 s100.9 KiB
www.mastercard.com/rysmLZ/l7F/tV8/4hUmLK2S/6SEY/dmUNIg/MiQmMVko/dHIp86400.0 s28.5 KiB
/logos/1df3f1e6-52a6-46c4-b5a1-0e035b09a859/c8f0ae6e-550f...86400.0 s27.2 KiB
www.mastercard.com/akam/13/7ad3fecb21600.0 s9.4 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site/resources...86400.0 s6.6 KiB
/etc.clientlibs/algolia/clientlibs/clientlib-site.lc-9d11...499770.0 s19.1 KiB
/etc.clientlibs/clientlibs/granite/jquery/granite/csrf.lc...0.0 ms1.7 KiB
www.mastercard.com/content/dam/mccom/shared/footer/privacyoptions.svg0.0 ms1.6 KiB
/etc.clientlibs/core/wcm/components/commons/datalayer/acd...499769.0 s11.4 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.7 KiB
/etc.clientlibs/marts/clientlibs/clientlib-base.lc-106cff...499770.0 s7.5 KiB
www.mastercard.com/content/dam/mccom/shared/header/ma_symbol.svg0.0 ms910 B
www.mastercard.com/.rum/@adobe/helix-rum-js@%5E2/dist/micro.js3600.0 s1.0 KiB
/acdc00762da2/83bdb98d95f8/b1ccace159e9/RCe48227830aa142f...3600.0 s763 B
/acdc00762da2/83bdb98d95f8/b1ccace159e9/RC5a41f5bb7320457...3600.0 s676 B
/etc.clientlibs/marts/clientlibs/clientlib-algoliaext.lc-...499770.0 s3.2 KiB
www.mastercard.com/rysmLZ/l7F/tV8/4hUmLK2S/6SEY/dmUNIg/fmgpXH4i/SQJZ86400.0 s1.0 KiB
/etc.clientlibs/marts/clientlibs/clientlib-base.lc-c5165b...499770.0 s2.3 KiB
/etc.clientlibs/core/wcm/components/commons/datalayer/v2/...499771.0 s1.3 KiB
/etc.clientlibs/core/wcm/components/commons/site/clientli...499779.0 s831 B
/etc.clientlibs/core/wcm/components/page/v2/page/clientli...499770.0 s586 B
/etc.clientlibs/marts/clientlibs/clientlib-dependencies.l...499770.0 s358 B
/etc.clientlibs/algolia/clientlibs/clientlib-hooksInitial...499771.0 s357 B
/etc.clientlibs/algolia/clientlibs/clientlib-hooksInitial...499770.0 s348 B
/etc.clientlibs/marts/clientlibs/clientlib-dependencies.l...499770.0 s347 B
/etc.clientlibs/marts/clientlibs/clientlib-algoliaext.lc-...499771.0 s347 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:15.659 source:map[column:29 line:57837 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:131.487 source:map[column:38 line:40857 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]] map[reflowTime:7.937 source:map[column:50 line:39318 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]] map[reflowTime:0.404 source:map[column:39 line:39247 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]] map[reflowTime:0.545 source:map[column:23 line:39048 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]] map[reflowTime:40.551 source:map[column:234606 line:0 type:source-location url:https://www.mastercard.com/rysmLZ/l7F/tV8/4hUmLK2S/iYEYX4r97Oucr2Oz/IhkYIg/ShUxeHpN/GkkB urlProvider:network]] map[reflowTime:37.142 source:map[column:6743 line:1 type:source-location url:https://www.mastercard.com/akam/13/7ad3fecb urlProvider:network]] map[reflowTime:0.507 source:map[column:92 line:38289 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]] map[reflowTime:4.793 source:map[column:43 line:44760 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]] map[reflowTime:2.737 source:map[column:51 line:47788 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]] map[reflowTime:5.031 source:map[column:15 line:45171 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]] map[reflowTime:3.098 source:map[column:69 line:45520 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]] map[reflowTime:2.9 source:map[column:53 line:58646 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Woman typing on mobile device. div.cmp-teaser__image > div#teaser-1e27cad344-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--d46becfe-4262-4e2c-9c...23.2 MiB24.2 MiB
Hand tapping on screen. div.cmp-teaser__image > div#teaser-09bc642aeb-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--c471b0a1-c241-4d00-ac...23.0 MiB23.7 MiB
A woman in a food truck accepts a credit card from a customer. div.cmp-teaser__image > div#teaser2-bc0fb0a6f3-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--01abe707-fcd0-4c1d-a9...968.0 KiB883.7 KiB
Close up of fingerprint. div.cmp-teaser__image > div#teaser2-1ce85d108d-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--c63c505c-a6b9-4cae-9f...268.8 KiB184.5 KiB
poster div.mccom-video-container > div.youtube-player > div#player-video-1259674180 > img
/content/dam/mccom/shared/homepage/images/messi-mastercar...217.9 KiB179.1 KiB
Person wearing a seatbelt in a parked vehicle and looking at a phone. div.cmp-teaser__image > div#teaser-0e402357ce-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--cb42b726-9398-4633-93...98.4 KiB75.1 KiB
Person making a payment with a watch. div.cmp-teaser__image > div#teaser-c8c77cd9a9-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--31deb226-0992-429e-8f...48.2 KiB37.8 KiB
Shamina Singh and Paschal Donohoe at the Global Inclusive Growth Forum div.cmp-teaser__image > div#teaser2-eac192e280-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--9c3a3e49-0fb7-4f02-b5...112.6 KiB21.8 KiB
A business woman with phone. div.cmp-teaser__image > div#teaser2-cdd8d21a71-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--bcd71f82-2c43-4641-a3...138.3 KiB12.4 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:66.43799975585938 label:Time to first byte subpart:timeToFirstByte] map[duration:1567.9660002441406 label:Resource load delay subpart:resourceLoadDelay] map[duration:2294.84 label:Resource load duration subpart:resourceLoadDuration] map[duration:-1208.787 label:Element render delay subpart:elementRenderDelay]]
lhId: page-9-VIDEO
nodeLabel: Experience Priceless Video
path: 1,HTML,1,BODY,4,DIV,0,DIV,0,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,VIDEO
selector: div.video-hero > div.mccom-video-hero-container > div#vjs_video_3 > video#vjs_video_3_html5_api
snippet: <video muted="muted" autoplay="" disablepictureinpicture="" preload="auto" class="vjs-tech" aria-label="Experience Priceless Video" id="vjs_video_3_html5_api" tabindex="-1" playsinline="playsinline" src="/content/dam/mccom/shared/homepage/videos/BR45724_MC_WebUnification_Opt8_9…">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-9-VIDEO
nodeLabel: Experience Priceless Video
path: 1,HTML,1,BODY,4,DIV,0,DIV,0,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,VIDEO
selector: div.video-hero > div.mccom-video-hero-container > div#vjs_video_3 > video#vjs_video_3_html5_api
snippet: <video muted="muted" autoplay="" disablepictureinpicture="" preload="auto" class="vjs-tech" aria-label="Experience Priceless Video" id="vjs_video_3_html5_api" tabindex="-1" playsinline="playsinline" src="/content/dam/mccom/shared/homepage/videos/BR45724_MC_WebUnification_Opt8_9…">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 762 ms

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 100 ms 5.3 KiB
URLTransfer SizeEst Savings
asset.forms.mastercard.com/forms-ui@v2.0.8/theme.css6.0 KiB3.3 KiB
24.8 KiB2.0 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.2 s 228.8 KiB
URLTransfer SizeEst Savings
/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99...469.3 KiB228.8 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 550 ms 139.1 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation5.7 s
Other3.9 s
Style & Layout1.6 s
Script Parsing & Compilation908 ms
Rendering351 ms
Parse HTML & CSS260 ms
Garbage Collection162 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
poster div.mccom-video-container > div.youtube-player > div#player-video-1259674180 > img
/content/dam/mccom/shared/homepage/images/messi-mastercar...
Mastercard brand symbol - a global technology company in the payments industry div.navigation-bar > div.navigation-bar__logo > a > img
www.mastercard.com/content/dam/mccom/shared/header/ma_symbol.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 19 animated elements found
Network Requests
Network Round Trip Times 0 ms
Server Backend Latencies 50 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 20 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
User Timing marks and measures
99

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NEED HELP? div#footer-tools-navigation > div.title > div#title-718a7fc955 > h6.cmp-title__text

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Mastercard Agent pay div#carousel-f8f502e444 > div.cmp-carousel__actions-bottom > ol.cmp-carousel__indicators > li#carousel-f8f502e444-item-eac192e280-tab
Mastercard Agent pay div#carousel-f8f502e444 > div.cmp-carousel__actions-bottom > ol.cmp-carousel__indicators > li#carousel-f8f502e444-item-bc0fb0a6f3-tab
Mastercard Agent pay div#carousel-f8f502e444 > div.cmp-carousel__actions-bottom > ol.cmp-carousel__indicators > li#carousel-f8f502e444-item-cdd8d21a71-tab
Partnering for growth div#carousel-f8f502e444 > div.cmp-carousel__actions-bottom > ol.cmp-carousel__indicators > li#carousel-f8f502e444-item-ca34b2c856-tab
Mastercard Agent pay div#carousel-f8f502e444 > div.cmp-carousel__actions-bottom > ol.cmp-carousel__indicators > li#carousel-f8f502e444-item-1ce85d108d-tab
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
`<video>` elements contain a `<track>` element with `[kind="captions"]`
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
82

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about `hreflang`.

Why this matters

Performance issues directly impact user engagement and conversion rates.

head > link
head > link
head > link
head > link
head > link
head > link
head > link

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links are crawlable
Image elements have `[alt]` attributes
robots.txt is valid
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

46
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
87
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
82
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

951 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

31.20 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

410 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.013

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

10.87 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

32.20 s

Detailed Report

Audit breakdown by category with detailed findings.

46

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/adobe/dynamicmedia/deliver/dm-aid--d46becfe-4262-4e2c-9c...600.0 s23.2 MiB
/adobe/dynamicmedia/deliver/dm-aid--c471b0a1-c241-4d00-ac...600.0 s23.0 MiB
/adobe/dynamicmedia/deliver/dm-aid--01abe707-fcd0-4c1d-a9...600.0 s969.6 KiB
/adobe/dynamicmedia/deliver/dm-aid--c63c505c-a6b9-4cae-9f...600.0 s269.4 KiB
/adobe/dynamicmedia/deliver/dm-aid--bcd71f82-2c43-4641-a3...600.0 s139.3 KiB
www.mastercard.com/rysmLZ/l7F/tV8/4hUmLK2S/iYEYX4r97Oucr2Oz/IhkYIg/ShUxeHpN/GkkB21600.0 s174.9 KiB
/adobe/dynamicmedia/deliver/dm-aid--9c3a3e49-0fb7-4f02-b5...600.0 s113.5 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site/resources...86400.0 s250.5 KiB
/adobe/dynamicmedia/deliver/dm-aid--efc24a51-bf03-4d56-a4...600.0 s83.3 KiB
assets.adobedtm.com/acdc00762da2/83bdb98d95f8/launch-05f4b8356cc4.min.js3600.0 s89.2 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99...499743.0 s469.6 KiB
/adobe/dynamicmedia/deliver/dm-aid--d73a04ae-35f0-47ff-97...600.0 s62.3 KiB
cdn.cookielaw.org/scripttemplates/202604.1.0/otBannerSdk.js86400.0 s131.0 KiB
/adobe/dynamicmedia/deliver/dm-aid--31deb226-0992-429e-8f...600.0 s49.2 KiB
/etc.clientlibs/algolia/clientlibs/clientlib-site.lc-39e1...499743.0 s255.1 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site/resources...86400.0 s37.0 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site/resources...86400.0 s36.5 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site/resources...86400.0 s36.2 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site.lc-bf9c32...499743.0 s100.9 KiB
www.mastercard.com/rysmLZ/l7F/tV8/4hUmLK2S/6SEY/dmUNIg/MiQmMVko/dHIp86400.0 s28.5 KiB
/logos/1df3f1e6-52a6-46c4-b5a1-0e035b09a859/c8f0ae6e-550f...86400.0 s27.2 KiB
www.mastercard.com/akam/13/7ad3fecb21600.0 s9.3 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
/etc.clientlibs/marts/clientlibs/clientlib-site/resources...86400.0 s7.1 KiB
/etc.clientlibs/algolia/clientlibs/clientlib-site.lc-9d11...499743.0 s19.1 KiB
/etc.clientlibs/clientlibs/granite/jquery/granite/csrf.lc...0.0 ms1.7 KiB
/etc.clientlibs/core/wcm/components/commons/datalayer/acd...499741.0 s11.4 KiB
www.mastercard.com/content/dam/mccom/shared/footer/privacyoptions.svg0.0 ms1.1 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.7 KiB
/etc.clientlibs/marts/clientlibs/clientlib-base.lc-106cff...499742.0 s7.5 KiB
www.mastercard.com/content/dam/mccom/shared/header/ma_symbol.svg0.0 ms910 B
www.mastercard.com/.rum/@adobe/helix-rum-js@%5E2/dist/micro.js3600.0 s1.0 KiB
/acdc00762da2/83bdb98d95f8/b1ccace159e9/RCe48227830aa142f...3600.0 s763 B
/acdc00762da2/83bdb98d95f8/b1ccace159e9/RC5a41f5bb7320457...3600.0 s676 B
/etc.clientlibs/marts/clientlibs/clientlib-algoliaext.lc-...499742.0 s3.2 KiB
www.mastercard.com/rysmLZ/l7F/tV8/4hUmLK2S/6SEY/dmUNIg/fmgpXH4i/SQJZ86400.0 s1.0 KiB
/etc.clientlibs/marts/clientlibs/clientlib-base.lc-c5165b...499743.0 s2.3 KiB
/etc.clientlibs/core/wcm/components/commons/datalayer/v2/...499743.0 s1.3 KiB
/etc.clientlibs/core/wcm/components/commons/site/clientli...499751.0 s831 B
/etc.clientlibs/core/wcm/components/page/v2/page/clientli...499743.0 s586 B
/etc.clientlibs/marts/clientlibs/clientlib-dependencies.l...499743.0 s358 B
/etc.clientlibs/algolia/clientlibs/clientlib-hooksInitial...499744.0 s357 B
/etc.clientlibs/algolia/clientlibs/clientlib-hooksInitial...499743.0 s348 B
/etc.clientlibs/marts/clientlibs/clientlib-dependencies.l...499743.0 s347 B
/etc.clientlibs/marts/clientlibs/clientlib-algoliaext.lc-...499744.0 s347 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:27.118 source:map[column:195868 line:31 type:source-location url:https://www.mastercard.com/etc.clientlibs/algolia/clientlibs/clientlib-site.lc-39e1e2e5e7bb50ebf287c0448303b970-lc.min.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:166.476 source:map[type:text value:[unattributed]]] map[reflowTime:27.118 source:map[column:184489 line:30 type:source-location url:https://www.mastercard.com/etc.clientlibs/algolia/clientlibs/clientlib-site.lc-39e1e2e5e7bb50ebf287c0448303b970-lc.min.js urlProvider:network]] map[reflowTime:2.584 source:map[column:38 line:40857 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]] map[reflowTime:0.458 source:map[column:50 line:39318 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]] map[reflowTime:0.455 source:map[column:23 line:39048 type:source-location url:https://www.mastercard.com/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99be5b638982eeb3847c915e0cfa-lc.min.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Woman typing on mobile device. div.cmp-teaser__image > div#teaser-1e27cad344-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--d46becfe-4262-4e2c-9c...23.2 MiB24.0 MiB
Hand tapping on screen. div.cmp-teaser__image > div#teaser-09bc642aeb-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--c471b0a1-c241-4d00-ac...23.0 MiB23.6 MiB
A woman in a food truck accepts a credit card from a customer. div.cmp-teaser__image > div#teaser2-bc0fb0a6f3-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--01abe707-fcd0-4c1d-a9...968.0 KiB846.9 KiB
Close up of fingerprint. div.cmp-teaser__image > div#teaser2-1ce85d108d-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--c63c505c-a6b9-4cae-9f...268.8 KiB147.9 KiB
A business woman with phone. div.cmp-teaser__image > div#teaser2-cdd8d21a71-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--bcd71f82-2c43-4641-a3...138.3 KiB90.0 KiB
Woman adjusting a belt on a customer trying on a dress. div.cmp-teaser__image > div#teaser-64de5e5eb4-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--efc24a51-bf03-4d56-a4...82.2 KiB47.5 KiB
Person making a payment with a watch. div.cmp-teaser__image > div#teaser-c8c77cd9a9-image > picture > img.cmp-image__image
/adobe/dynamicmedia/deliver/dm-aid--31deb226-0992-429e-8f...48.2 KiB39.3 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:80.983 label:Time to first byte subpart:timeToFirstByte] map[duration:1820.619 label:Resource load delay subpart:resourceLoadDelay] map[duration:2313.582 label:Resource load duration subpart:resourceLoadDuration] map[duration:-1199.071 label:Element render delay subpart:elementRenderDelay]]
lhId: page-7-VIDEO
nodeLabel: Experience Priceless Video
path: 1,HTML,1,BODY,4,DIV,0,DIV,0,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,VIDEO
selector: div.video-hero > div.mccom-video-hero-container > div#vjs_video_3 > video#vjs_video_3_html5_api
snippet: <video muted="muted" autoplay="" disablepictureinpicture="" preload="auto" class="vjs-tech" aria-label="Experience Priceless Video" id="vjs_video_3_html5_api" tabindex="-1" playsinline="playsinline" src="/content/dam/mccom/shared/homepage/videos/BR45724_MC_WebUnification_Opt8_1…">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-7-VIDEO
nodeLabel: Experience Priceless Video
path: 1,HTML,1,BODY,4,DIV,0,DIV,0,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,VIDEO
selector: div.video-hero > div.mccom-video-hero-container > div#vjs_video_3 > video#vjs_video_3_html5_api
snippet: <video muted="muted" autoplay="" disablepictureinpicture="" preload="auto" class="vjs-tech" aria-label="Experience Priceless Video" id="vjs_video_3_html5_api" tabindex="-1" playsinline="playsinline" src="/content/dam/mccom/shared/homepage/videos/BR45724_MC_WebUnification_Opt8_1…">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 211 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 160 ms 228.8 KiB
URLTransfer SizeEst Savings
/etc.clientlibs/marts/clientlibs/clientlib-site.lc-ca8f99...469.3 KiB228.8 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 160 ms 142.0 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.5 s
Other937 ms
Style & Layout454 ms
Script Parsing & Compilation230 ms
Rendering79 ms
Parse HTML & CSS56 ms
Garbage Collection50 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.3 KiB
URLTransfer SizeEst Savings
asset.forms.mastercard.com/forms-ui@v2.0.8/theme.css6.0 KiB3.3 KiB
24.8 KiB2.0 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
poster div.mccom-video-container > div.youtube-player > div#player-video-1259674180 > img
/content/dam/mccom/shared/homepage/images/messi-mastercar...
Mastercard brand symbol - a global technology company in the payments industry div.navigation-bar > div.navigation-bar__logo > a > img
www.mastercard.com/content/dam/mccom/shared/header/ma_symbol.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
Avoid long main-thread tasks 10 long tasks found
Avoid non-composited animations 14 animated elements found
Network Requests
Network Round Trip Times 0 ms
Server Backend Latencies 60 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 40 ms
Avoid large layout shifts 9 layout shifts found
INP breakdown
User Timing marks and measures
87

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
For you For business For the world For innovators News and trends div.navigation-bar__main > div.l1-container > div#mobileMenu > ul

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
For you div#mobileMenu > ul > li > button#heading-1f2ad0e473
For business div#mobileMenu > ul > li > button#heading-e51b865f32
For the world div#mobileMenu > ul > li > button#heading-74968c2f23
For innovators div#mobileMenu > ul > li > button#heading-900a6ee2fb
News and trends div#mobileMenu > ul > li > button#heading-bba1fd377f

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NEED HELP? div#footer-tools-navigation > div.title > div#title-718a7fc955 > h6.cmp-title__text

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
For you div.l1-container > div#mobileMenu > ul > li
For business div.l1-container > div#mobileMenu > ul > li
For the world div.l1-container > div#mobileMenu > ul > li
For innovators div.l1-container > div#mobileMenu > ul > li
News and trends div.l1-container > div#mobileMenu > ul > li

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Mastercard Agent pay div#carousel-f8f502e444 > div.cmp-carousel__actions-bottom > ol.cmp-carousel__indicators > li#carousel-f8f502e444-item-eac192e280-tab
Mastercard Agent pay div#carousel-f8f502e444 > div.cmp-carousel__actions-bottom > ol.cmp-carousel__indicators > li#carousel-f8f502e444-item-bc0fb0a6f3-tab
Mastercard Agent pay div#carousel-f8f502e444 > div.cmp-carousel__actions-bottom > ol.cmp-carousel__indicators > li#carousel-f8f502e444-item-cdd8d21a71-tab
Partnering for growth div#carousel-f8f502e444 > div.cmp-carousel__actions-bottom > ol.cmp-carousel__indicators > li#carousel-f8f502e444-item-ca34b2c856-tab
Mastercard Agent pay div#carousel-f8f502e444 > div.cmp-carousel__actions-bottom > ol.cmp-carousel__indicators > li#carousel-f8f502e444-item-1ce85d108d-tab
Priceless.com opens in a new tab div#mastercard-sites > ul#navMenu-2-panel > li > a
Mastercard Business Intelligence opens in a new tab div#mastercard-sites > ul#navMenu-2-panel > li > a
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
`<video>` elements contain a `<track>` element with `[kind="captions"]`
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
82

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about `hreflang`.

Why this matters

Performance issues directly impact user engagement and conversion rates.

head > link
head > link
head > link
head > link
head > link
head > link
head > link

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links are crawlable
Image elements have `[alt]` attributes
robots.txt is valid
Document has a valid `rel=canonical`

Send Feedback