C — https://www.adyen.com | BeaverCheck Audit

Site Health

Score: 78 / 100

Based on 8 categories, 0 sections

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.

Top Priorities (5)

Page weighs 11.9 MB (5.1 MB transferred)

Performance › Page Weight Budget

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Cross-Origin-Opener-Policy header is missing

Security › Security Headers

External script from cdn.cookielaw.org lacks integrity attribute

Security › Subresource Integrity

External script from unpkg.com lacks integrity attribute

Security › Subresource Integrity

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.adyen.com)](https://beavercheck.com/results/308b1f48-2fc7-d671-0ca0-278ed0f4ddb7)

HTML

<a href="https://beavercheck.com/results/308b1f48-2fc7-d671-0ca0-278ed0f4ddb7"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.adyen.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.adyen.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

100

Accessibility

Best Practices

SEO

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

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

12.78 s

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

1.09 s

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

0.001

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

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

13.39 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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

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

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.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:47.912 source:map[type:text value:[unattributed]]]]

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.

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

value: no origins were preconnected

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

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

URL	Transfer Size	Duration
www.adyen.com/main_nuxt/entry.Z00byx7a.css	44.9 KiB	353 ms
www.adyen.com/main_nuxt/index.8laD0HR7.css	668 B

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

	URL	Resource Size	Est Savings
div.flex-col > div.relative > div.relative > img.object-cover `div.flex-col > div.relative > div.relative > img.object-cover`	media.ffycdn.net/eu/adyen/2PXpBe6QXczKBVtYdF1z.jpg?format=webp&width=1920	108.6 KiB	92.0 KiB
li.snap-start > div#2iBqAX2w3jAoz7Cbgz7qyW > div.absolute > video#video-bg-value-prop-section-0 `li.snap-start > div#2iBqAX2w3jAoz7Cbgz7qyW > div.absolute > video#video-bg-value-prop-section-0`	media.ffycdn.net/eu/adyen/CHfJ1ZrPActbUGbksYwX.mp4?format=webp&width=1280	75.4 KiB	23.3 KiB
li.snap-start > div#6dA4N0wK3SjzI9SzG2VrWO > div.absolute > video#video-bg-value-prop-section-3 `li.snap-start > div#6dA4N0wK3SjzI9SzG2VrWO > div.absolute > video#video-bg-value-prop-section-3`	media.ffycdn.net/eu/adyen/mxyacqUbxeeh4egB3H2B.mp4?format=webp&width=1280	33.8 KiB	5.0 KiB
li.snap-start > div#6U79s0fRsC4ttDiVo33Fku > div.absolute > video#video-bg-value-prop-section-1 `li.snap-start > div#6U79s0fRsC4ttDiVo33Fku > div.absolute > video#video-bg-value-prop-section-1`	media.ffycdn.net/eu/adyen/7kzhDSBL8gs4JXXyuGwz.mp4?format=webp&width=1280	32.0 KiB	4.7 KiB

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

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.

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.

TTI

Diagnostics

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

Estimated savings: 2.0 s 397.7 KiB

URL	Transfer Size	Est Savings
www.adyen.com/main_nuxt/BqNvtlgv.js	186.7 KiB	105.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-T4QN7PF3&gtm=4e6460	179.2 KiB	73.5 KiB
www.googletagmanager.com/gtag/js?id=G-TRCPE14CWT&cx=c&gtm=4e6460	176.1 KiB	66.5 KiB
www.googletagmanager.com/gtag/destination?id=DC-9189202&cx=c&gtm=4e6460	129.3 KiB	64.7 KiB
/gtm.js?id=GTM-575TF4H&gtm_auth=afdbAXrh3-yNk9m3Wq79uw&gt...	174.6 KiB	64.0 KiB
www.adyen.com/main_nuxt/B63nptKw.js	60.4 KiB	23.4 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.adyen.com/main_nuxt/B63nptKw.js	3.0 s	2.8 s	0.9 ms
www.adyen.com/main_nuxt/BqNvtlgv.js	1.9 s	213 ms	3.6 ms
Unattributable	1.1 s	250 ms	0.0 ms
www.adyen.com/	1.0 s	195 ms	3.0 ms
/gtm.js?id=GTM-575TF4H&gtm_auth=afdbAXrh3-yNk9m3Wq79uw&gt...	370 ms	266 ms	54 ms
www.googletagmanager.com/gtag/js?id=G-TRCPE14CWT&cx=c&gtm=4e6460	353 ms	270 ms	39 ms
www.googletagmanager.com/gtm.js?id=GTM-T4QN7PF3&gtm=4e6460	255 ms	213 ms	40 ms
www.googletagmanager.com/gtag/destination?id=DC-9189202&cx=c&gtm=4e6460	151 ms	111 ms	32 ms
www.adyen.com/.netlify/scripts/rum	87 ms	84 ms	1.0 ms

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

Category	Time Spent
Script Evaluation	4.4 s
Other	2.6 s
Style & Layout	577 ms
Rendering	278 ms
Script Parsing & Compilation	177 ms
Garbage Collection	172 ms
Parse HTML & CSS	109 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

Failure reason	Failure type
Internal error.	Not actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
media.ffycdn.net/eu/adyen/tWdz1QtnMpB2yi7BNLam.mp4?format=mp4	3.1 MiB
www.adyen.com/	188.1 KiB
www.adyen.com/main_nuxt/BqNvtlgv.js	186.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-T4QN7PF3&gtm=4e6460	179.3 KiB
www.googletagmanager.com/gtag/js?id=G-TRCPE14CWT&cx=c&gtm=4e6460	176.2 KiB
/gtm.js?id=GTM-575TF4H&gtm_auth=afdbAXrh3-yNk9m3Wq79uw&gt...	175.0 KiB
www.adyen.com/_payload.json?0dad88c1-96f2-47fe-9459-7cfc838d1ed4	174.4 KiB
www.adyen.com/main_nuxt/Adyen-Variable.s-8vvc6Q.woff2	145.3 KiB
www.googletagmanager.com/gtag/destination?id=DC-9189202&cx=c&gtm=4e6460	129.4 KiB
media.ffycdn.net/eu/adyen/2PXpBe6QXczKBVtYdF1z.jpg?format=webp&width=1920	109.2 KiB

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 9 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 24 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 40 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 70 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

100

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.

○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

●`[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

●`[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.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

○ARIA IDs are unique

○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

○Form elements have associated labels

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

○Skip links are focusable.

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

○`[lang]` attributes have a valid value

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

○Elements with visible text labels have matching accessible names.

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

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Source	Description
www.adyen.com/.netlify/functions/__csp-violations	`Failed to load resource: the server responded with a status of 404 ()`
www.adyen.com/main_nuxt/BqNvtlgv.js line 1, col 30846	`Hydration completed but contains mismatches.`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type
Content security policy

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.

URL
www.adyen.com/main_nuxt/BqNvtlgv.js

●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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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.

Link destination	Link Text
www.adyen.com/industries/retail	See more

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

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.

1.02 s

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

1.83 s

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

135 ms

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

0.000

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

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

2.63 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

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

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:132.861 source:map[type:text value:[unattributed]]]]

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.

title: Preconnected origins

value: no origins were preconnected

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

value: No additional origins are good candidates for preconnecting

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

	URL	Resource Size	Est Savings
li.snap-start > div#2iBqAX2w3jAoz7Cbgz7qyW > div.absolute > video#video-bg-value-prop-section-0 `li.snap-start > div#2iBqAX2w3jAoz7Cbgz7qyW > div.absolute > video#video-bg-value-prop-section-0`	media.ffycdn.net/eu/adyen/CHfJ1ZrPActbUGbksYwX.mp4?format=webp&width=1280	75.4 KiB	43.6 KiB
li.snap-start > div#6dA4N0wK3SjzI9SzG2VrWO > div.absolute > video#video-bg-value-prop-section-3 `li.snap-start > div#6dA4N0wK3SjzI9SzG2VrWO > div.absolute > video#video-bg-value-prop-section-3`	media.ffycdn.net/eu/adyen/mxyacqUbxeeh4egB3H2B.mp4?format=webp&width=1280	33.8 KiB	13.6 KiB
li.snap-start > div#6U79s0fRsC4ttDiVo33Fku > div.absolute > video#video-bg-value-prop-section-1 `li.snap-start > div#6U79s0fRsC4ttDiVo33Fku > div.absolute > video#video-bg-value-prop-section-1`	media.ffycdn.net/eu/adyen/7kzhDSBL8gs4JXXyuGwz.mp4?format=webp&width=1280	32.0 KiB	12.9 KiB
li.snap-start > div#564gCSIM1bAhBACFYcgdpx > div.absolute > video#video-bg-value-prop-section-2 `li.snap-start > div#564gCSIM1bAhBACFYcgdpx > div.absolute > video#video-bg-value-prop-section-2`	media.ffycdn.net/eu/adyen/qo8UsrxXDKZ1kJFpUMPi.mp4?format=webp&width=1280	18.8 KiB	7.6 KiB
div.absolute > span.absolute > span.size-full > video.object-cover `div.absolute > span.absolute > span.size-full > video.object-cover`	media.ffycdn.net/eu/adyen/tWdz1QtnMpB2yi7BNLam.mp4?format=webp	86.2 KiB	5.3 KiB

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

URL	Transfer Size
www.adyen.com/main_nuxt/entry.Z00byx7a.css	44.9 KiB
www.adyen.com/main_nuxt/index.8laD0HR7.css	669 B

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

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.

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.

TTI

Diagnostics

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

Estimated savings: 140 ms 397.9 KiB

URL	Transfer Size	Est Savings
www.adyen.com/main_nuxt/BqNvtlgv.js	186.7 KiB	105.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-T4QN7PF3&gtm=4e6460	179.2 KiB	73.5 KiB
www.googletagmanager.com/gtag/js?id=G-TRCPE14CWT&cx=c&gtm=4e6460	176.1 KiB	66.6 KiB
www.googletagmanager.com/gtag/destination?id=DC-9189202&cx=c&gtm=4e6460	129.3 KiB	64.7 KiB
/gtm.js?id=GTM-575TF4H&gtm_auth=afdbAXrh3-yNk9m3Wq79uw&gt...	174.6 KiB	64.0 KiB
www.adyen.com/main_nuxt/B63nptKw.js	60.4 KiB	23.4 KiB

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

Category	Time Spent
Script Evaluation	1.1 s
Other	602 ms
Style & Layout	242 ms
Garbage Collection	71 ms
Rendering	62 ms
Script Parsing & Compilation	57 ms
Parse HTML & CSS	36 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

Failure reason	Failure type
Navigation was cancelled before the page could be restored from back/forward cache.	Not actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
media.ffycdn.net/eu/adyen/tWdz1QtnMpB2yi7BNLam.mp4?format=mp4	3.2 MiB
www.adyen.com/	188.1 KiB
www.adyen.com/main_nuxt/BqNvtlgv.js	186.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-T4QN7PF3&gtm=4e6460	179.3 KiB
www.googletagmanager.com/gtag/js?id=G-TRCPE14CWT&cx=c&gtm=4e6460	176.2 KiB
/gtm.js?id=GTM-575TF4H&gtm_auth=afdbAXrh3-yNk9m3Wq79uw&gt...	175.0 KiB
www.adyen.com/_payload.json?0dad88c1-96f2-47fe-9459-7cfc838d1ed4	174.6 KiB
www.adyen.com/main_nuxt/Adyen-Variable.s-8vvc6Q.woff2	145.3 KiB
www.googletagmanager.com/gtag/destination?id=DC-9189202&cx=c&gtm=4e6460	129.4 KiB
media.ffycdn.net/eu/adyen/tWdz1QtnMpB2yi7BNLam.mp4?format=webp	87.1 KiB

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 9 user timings

●JavaScript execution time 1.1 s

●Avoid long main-thread tasks 6 long tasks found

●Avoid non-composited animations 24 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 60 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 80 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

Accessibility

ARIA

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.

Failing Elements
PRIVACY `div.hidden > ul.m-0 > li.group > a.ds-focusable`
COOKIES `div.hidden > ul.m-0 > li.group > a.ds-focusable`
DISCLAIMER `div.hidden > ul.m-0 > li.group > a.ds-focusable`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Failing Elements
PRIVACY COOKIES DISCLAIMER `div.mx-auto > div.relative > div.hidden > ul.m-0`

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

○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

●`[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

●`[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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○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

○ARIA IDs are unique

○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

○Form elements have associated labels

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

○Skip links are focusable.

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

○`[lang]` attributes have a valid value

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

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Source	Description
www.adyen.com/.netlify/functions/__csp-violations	`Failed to load resource: the server responded with a status of 404 ()`
www.adyen.com/main_nuxt/BqNvtlgv.js line 1, col 30846	`Hydration completed but contains mismatches.`

Issue type
Content security policy

URL
www.adyen.com/main_nuxt/BqNvtlgv.js

●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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

SEO

Content Best Practices

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

Link destination	Link Text
www.adyen.com/industries/retail	See more

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.adyen.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Tables and lists

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts