C — https://www.snyk.io | BeaverCheck Audit

Site Health

Score: 76 / 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)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

Page weighs 8.3 MB (4.1 MB transferred)

Performance › Page Weight Budget

1 button(s) with no accessible text

Accessibility › Link & Button Quality

106 HTTP requests — consider bundling or reducing

Performance › Page Weight Budget

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.snyk.io)](https://beavercheck.com/results/513adcc9-c5c8-f5d2-be58-7682e9106764)

HTML

<a href="https://beavercheck.com/results/513adcc9-c5c8-f5d2-be58-7682e9106764"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.snyk.io" alt="BeaverCheck Score"></a>

Image URL

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

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.

4.95 s

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

13.56 s

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

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

6.86 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.69 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 long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
/analytics.js/v1/UspolAZH46ZIH3mN3bdf7rx63q24gitb/analyti...	120.0 s	28.8 KiB
web.cmp.usercentrics.eu/ui/TvGdprCmpView.b6de9c89.js	3600.0 s	35.3 KiB
web.cmp.usercentrics.eu/ui/loader.js	3600.0 s	20.3 KiB
app.usercentrics.eu/session/1px.png?settingsId=HJ-Jgu0__ikv-k	1800.0 s	1.0 KiB

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

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:75.424 source:map[type:text value:[unattributed]]]]

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

lhId: page-0-DIV

nodeLabel: main#main-content > section.hero > div.decorations-wrapper > div.decoration-bg

path: 1,HTML,1,BODY,2,DIV,0,DIV,2,MAIN,0,SECTION,0,DIV,0,DIV

selector: main#main-content > section.hero > div.decorations-wrapper > div.decoration-bg

snippet: <div class="decoration-bg dot-wave dot-wave-1 dot-wave-top-left-high">

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

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
article.card > div.card-banner > div.w-full > img.object-fit-cover `article.card > div.card-banner > div.w-full > img.object-fit-cover`	/_next/image/?url=https%3A%2F%2Fres.cloudinary.com%2Fsnyk...	41.9 KiB	36.4 KiB
article.card > div.card-banner > div.w-full > img.object-fit-cover `article.card > div.card-banner > div.w-full > img.object-fit-cover`	/_next/image/?url=https%3A%2F%2Fres.cloudinary.com%2Fsnyk...	26.4 KiB	23.0 KiB
article.card > div.card-banner > div.w-full > img.object-fit-cover `article.card > div.card-banner > div.w-full > img.object-fit-cover`	/_next/image/?url=https%3A%2F%2Fres.cloudinary.com%2Fsnyk...	24.2 KiB	21.1 KiB
div.brandui-container > div.w-full > div.aspect-ratio-video > img.object-fit-cover `div.brandui-container > div.w-full > div.aspect-ratio-video > img.object-fit-cover`	/_next/image/?url=https%3A%2F%2Fres.cloudinary.com%2Fsnyk...	21.4 KiB	8.1 KiB

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

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

Estimated savings: 758 ms

URL	Time Spent
www.snyk.io/	758 ms
snyk.io/	0.0 ms

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

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.

Diagnostics

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

Estimated savings: 150 ms 48.3 KiB

URL	Transfer Size	Est Savings
web.cmp.usercentrics.eu/ui/v/3.111.0/WebSdk.lib.f9924d53.js	73.2 KiB	22.8 KiB
web.cmp.usercentrics.eu/ui/TvGdprCmpView.b6de9c89.js	35.3 KiB	11.6 KiB
web.cmp.usercentrics.eu/ui/loader.js	19.7 KiB	6.8 KiB
web.cmp.usercentrics.eu/ui/v/3.111.0/GdprCmpController.51b3e85e.js	12.7 KiB	4.5 KiB
web.cmp.usercentrics.eu/ui/v/3.111.0/UcGdprCmpView.c071ab9b.js	21.4 KiB	2.6 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.

Estimated savings: 330 ms 83.7 KiB

URL	Transfer Size	Est Savings
snyk.io/_next/static/css/0757390cfe034cb1.css	76.6 KiB	73.6 KiB
.overlay { --color-cmp-overlay: #21214C; --feature-overlay-opacity: 0.6; } …	11.8 KiB	10.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.

Estimated savings: 1.4 s 281.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/destination?id=G-X9SH3KP7B4&cx=c&gtm=4e6460	163.4 KiB	68.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-W4LKKNL&gtm=4e6460	148.1 KiB	68.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-T8QMQW9	122.2 KiB	59.0 KiB
web.cmp.usercentrics.eu/ui/v/3.111.0/WebSdk.lib.f9924d53.js	73.2 KiB	43.3 KiB
snyk.io/_next/static/chunks/framework-2ec761b5af9ac788.js	58.9 KiB	21.9 KiB
web.cmp.usercentrics.eu/ui/TvGdprCmpView.b6de9c89.js	35.3 KiB	20.0 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
Unattributable	595 ms	49 ms	0.0 ms
snyk.io/	579 ms	15 ms	1.9 ms
snyk.io/_next/static/chunks/7909-3e366bfa7531aa22.js	447 ms	72 ms	3.0 ms
snyk.io/_next/static/chunks/framework-2ec761b5af9ac788.js	270 ms	249 ms	13 ms
www.googletagmanager.com/gtag/destination?id=G-X9SH3KP7B4&cx=c&gtm=4e6460	230 ms	190 ms	37 ms
web.cmp.usercentrics.eu/ui/v/3.111.0/WebSdk.lib.f9924d53.js	159 ms	110 ms	44 ms
www.googletagmanager.com/gtm.js?id=GTM-T8QMQW9	142 ms	105 ms	31 ms
snyk.io/_next/static/chunks/main-adfdb9879c87958c.js	127 ms	113 ms	10 ms
www.googletagmanager.com/gtm.js?id=GTM-W4LKKNL&gtm=4e6460	115 ms	76 ms	36 ms
web.cmp.usercentrics.eu/ui/v/3.111.0/UcGdprCmpView.c071ab9b.js	108 ms	36 ms	11 ms
j.6sc.co/6si.min.js	100 ms	78 ms	4.6 ms
snyk.io/_next/static/css/0757390cfe034cb1.css	64 ms	0.0 ms	0.0 ms
snyk.io/_next/static/chunks/pages/index-854fab16c73732f4.js	58 ms	57 ms	0.7 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	1.4 s
Other	915 ms
Style & Layout	509 ms
Script Parsing & Compilation	260 ms
Rendering	142 ms
Parse HTML & CSS	88 ms
Garbage Collection	23 ms

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

URL	Transfer Size
/snyk/video/upload/q_auto/v1742994981/Snyk_Homepage_Recor...	2.1 MiB
/snyk/image/upload/snyk-mktg-brandui/decorations/decorati...	291.4 KiB
/snyk/image/upload/snyk-mktg-brandui/decorations/decorati...	278.7 KiB
www.googletagmanager.com/gtag/destination?id=G-X9SH3KP7B4&cx=c&gtm=4e6460	163.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-W4LKKNL&gtm=4e6460	148.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-T8QMQW9	122.5 KiB
snyk.io/_next/static/css/0757390cfe034cb1.css	77.0 KiB
web.cmp.usercentrics.eu/ui/v/3.111.0/WebSdk.lib.f9924d53.js	73.5 KiB
snyk.io/_next/static/chunks/framework-2ec761b5af9ac788.js	59.3 KiB
snyk.io/_next/static/media/fb407b189f36a608.p.woff2	57.3 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 11 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 160 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

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

●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

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

●Select elements have associated label elements.

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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○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

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

○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
snyk.io/	`Access to XMLHttpRequest at 'https://secure.adnxs.com/getuidj' from origin 'https://snyk.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
secure.adnxs.com/getuidj	`Failed to load resource: net::ERR_FAILED`

●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 issues in the `Issues` panel in Chrome Devtools

●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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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
snyk.io/platform/	Learn 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

100

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.

924 ms

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

1.55 s

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

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

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

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

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

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

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

lhId: page-0-DIV

nodeLabel: main#main-content > section.hero > div.decorations-wrapper > div.decoration-bg

path: 1,HTML,1,BODY,2,DIV,0,DIV,2,MAIN,0,SECTION,0,DIV,1,DIV

selector: main#main-content > section.hero > div.decorations-wrapper > div.decoration-bg

snippet: <div class="decoration-bg dot-wave dot-wave-1 dot-wave-center-middle mobile:d-none">

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

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

Request	Cache TTL	Transfer Size
/analytics.js/v1/UspolAZH46ZIH3mN3bdf7rx63q24gitb/analyti...	120.0 s	28.8 KiB
web.cmp.usercentrics.eu/ui/TvGdprCmpView.b6de9c89.js	3600.0 s	35.3 KiB
web.cmp.usercentrics.eu/ui/loader.js	3600.0 s	20.3 KiB
app.usercentrics.eu/session/1px.png?settingsId=HJ-Jgu0__ikv-k	1800.0 s	1.0 KiB

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
article.card > div.card-banner > div.w-full > img.object-fit-cover `article.card > div.card-banner > div.w-full > img.object-fit-cover`	/_next/image/?url=https%3A%2F%2Fres.cloudinary.com%2Fsnyk...	41.9 KiB	35.4 KiB
article.card > div.card-banner > div.w-full > img.object-fit-cover `article.card > div.card-banner > div.w-full > img.object-fit-cover`	/_next/image/?url=https%3A%2F%2Fres.cloudinary.com%2Fsnyk...	26.4 KiB	22.3 KiB
article.card > div.card-banner > div.w-full > img.object-fit-cover `article.card > div.card-banner > div.w-full > img.object-fit-cover`	/_next/image/?url=https%3A%2F%2Fres.cloudinary.com%2Fsnyk...	24.2 KiB	20.5 KiB

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

Diagnostics

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.

Estimated savings: 30 ms 85.1 KiB

URL	Transfer Size	Est Savings
snyk.io/_next/static/css/0757390cfe034cb1.css	76.6 KiB	72.6 KiB
.overlay { --color-cmp-overlay: #21214C; --feature-overlay-opacity: 0.6; } …	14.3 KiB	12.5 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.

Estimated savings: 40 ms 281.0 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-W4LKKNL&gtm=4e6460	148.1 KiB	68.4 KiB
www.googletagmanager.com/gtag/destination?id=G-X9SH3KP7B4&cx=c&gtm=4e6460	163.4 KiB	68.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-T8QMQW9	122.2 KiB	59.0 KiB
web.cmp.usercentrics.eu/ui/v/3.111.0/WebSdk.lib.f9924d53.js	73.2 KiB	43.3 KiB
snyk.io/_next/static/chunks/framework-2ec761b5af9ac788.js	58.9 KiB	21.9 KiB
web.cmp.usercentrics.eu/ui/TvGdprCmpView.b6de9c89.js	35.3 KiB	20.1 KiB

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

Estimated savings: 0.0 ms 48.3 KiB

URL	Transfer Size	Est Savings
web.cmp.usercentrics.eu/ui/v/3.111.0/WebSdk.lib.f9924d53.js	73.2 KiB	22.8 KiB
web.cmp.usercentrics.eu/ui/TvGdprCmpView.b6de9c89.js	35.3 KiB	11.6 KiB
web.cmp.usercentrics.eu/ui/loader.js	19.7 KiB	6.8 KiB
web.cmp.usercentrics.eu/ui/v/3.111.0/GdprCmpController.51b3e85e.js	12.7 KiB	4.5 KiB
web.cmp.usercentrics.eu/ui/v/3.111.0/UcGdprCmpView.c071ab9b.js	21.4 KiB	2.6 KiB

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

URL	Transfer Size
/snyk/video/upload/q_auto/v1742994981/Snyk_Homepage_Recor...	2.1 MiB
/snyk/image/upload/snyk-mktg-brandui/decorations/decorati...	291.4 KiB
/snyk/image/upload/snyk-mktg-brandui/decorations/decorati...	278.7 KiB
www.googletagmanager.com/gtag/destination?id=G-X9SH3KP7B4&cx=c&gtm=4e6460	163.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-W4LKKNL&gtm=4e6460	148.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-T8QMQW9	122.5 KiB
snyk.io/_next/static/css/0757390cfe034cb1.css	77.0 KiB
web.cmp.usercentrics.eu/ui/v/3.111.0/WebSdk.lib.f9924d53.js	73.5 KiB
/_next/image/?url=https%3A%2F%2Fres.cloudinary.com%2Fsnyk...	66.0 KiB
snyk.io/_next/static/chunks/framework-2ec761b5af9ac788.js	59.3 KiB

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

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

Estimated savings: 212 ms

URL	Time Spent
www.snyk.io/	212 ms
snyk.io/	0.0 ms

●Time to Interactive 1.6 s

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Max Potential First Input Delay 40 ms

●Minify CSS

●User Timing marks and measures 10 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 1.1 s

●Avoid long main-thread tasks 1 long task found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 110 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

100

Accessibility

○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

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

●Select elements have associated label elements.

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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○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

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

○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
snyk.io/	`Access to XMLHttpRequest at 'https://secure.adnxs.com/getuidj' from origin 'https://snyk.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
secure.adnxs.com/getuidj	`Failed to load resource: net::ERR_FAILED`

●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 issues in the `Issues` panel in Chrome Devtools

●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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

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

Link destination	Link Text
snyk.io/platform/	Learn 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.snyk.io

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

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts