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

Site Health

Score: 75 / 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

3 control(s) without accessible label

Accessibility › Form Accessibility

5 button(s) with no accessible text

Accessibility › Link & Button Quality

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.netlify.com)](https://beavercheck.com/results/df14a956-6a44-4277-a5c7-88c2a836b5a8)

HTML

<a href="https://beavercheck.com/results/df14a956-6a44-4277-a5c7-88c2a836b5a8"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.netlify.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.netlify.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

Accessibility

100

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.

3.10 s

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

11.39 s

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

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

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

11.66 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
js.hsforms.net/forms/v2.js	300.0 s	193.7 KiB
js.hs-analytics.net/analytics/1775319600000/7477936.js	300.0 s	43.1 KiB
cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.js	86400.0 s	103.0 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
js.hsadspixel.net/pixels.js	600.0 s	3.9 KiB
cdn.cookielaw.org/logos/static/ot_company_logo.png	86400.0 s	8.6 KiB
cdn.cookielaw.org/consent/5dec0507-5e89-4bb4-8f2d-0872be7dd9dd/OtAutoBlock.js	86400.0 s	7.0 KiB
js.hs-scripts.com/7477936.js	90.0 s	1.1 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.3 KiB
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB
www.gstatic.com/recaptcha/api2/info_2x.png	604800.0 s	689 B
www.gstatic.com/recaptcha/api2/refresh_2x.png	604800.0 s	624 B
www.gstatic.com/recaptcha/api2/audio_2x.png	604800.0 s	554 B
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	0 B

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.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	35 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	10 ms

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:2.422 source:map[column:108332 line:45 type:source-location url:https://js.hs-analytics.net/analytics/1775319600000/7477936.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:118.813 source:map[type:text value:[unattributed]]] map[reflowTime:1.807 source:map[column:81 line:177 type:source-location url:https://www.netlify.com/ urlProvider:network]] map[reflowTime:0.855 source:map[column:86058 line:44 type:source-location url:https://js.hs-analytics.net/analytics/1775319600000/7477936.js urlProvider:network]] map[reflowTime:4.921 source:map[column:153 line:534 type:source-location url:https://www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js urlProvider:network]] map[reflowTime:2.422 source:map[column:17869 line:44 type:source-location url:https://js.hs-analytics.net/analytics/1775319600000/7477936.js urlProvider:network]]]

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
cdn.cookielaw.org/consent/5dec0507-5e89-4bb4-8f2d-0872be7dd9dd/OtAutoBlock.js	7.0 KiB	770 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js	9.1 KiB	151 ms
www.netlify.com/_astro/index.DEYu2GN_.css	1.5 KiB
www.netlify.com/_astro/convince-your-boss.Bd6jOyPR.css	26.3 KiB	319 ms
www.netlify.com/_astro/index._tGI3oyO.css	1.3 KiB
www.netlify.com/_astro/index.CswAyQBw.css	7.9 KiB	160 ms

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.

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

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.9 s 584.1 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	362.6 KiB	247.0 KiB
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	362.6 KiB	167.1 KiB
js.hsforms.net/forms/v2.js	186.4 KiB	71.9 KiB
cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.js	102.8 KiB	53.4 KiB
www.netlify.com/_astro/preact.DVUxKnXA.js	96.0 KiB	44.7 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.netlify.com/	4.2 s	84 ms	21 ms
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	4.0 s	3.0 s	726 ms
Unattributable	1.6 s	401 ms	0.0 ms
js.hs-analytics.net/analytics/1775319600000/7477936.js	1.3 s	848 ms	25 ms
js.hsforms.net/forms/v2.js	670 ms	503 ms	100 ms
cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.js	530 ms	312 ms	76 ms
www.netlify.com/_astro/preact.module.CoPo3ckA.js	211 ms	153 ms	0.2 ms
cdn.cookielaw.org/consent/5dec0507-5e89-4bb4-8f2d-0872be7dd9dd/OtAutoBlock.js	148 ms	125 ms	14 ms
www.netlify.com/_astro/preact.DVUxKnXA.js	114 ms	24 ms	2.4 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js	58 ms	43 ms	4.6 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	5.8 s
Other	3.0 s
Style & Layout	2.0 s
Script Parsing & Compilation	976 ms
Rendering	923 ms
Parse HTML & CSS	242 ms
Garbage Collection	221 ms

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: 0.0 ms 16.8 KiB

URL	Transfer Size	Est Savings
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} …	19.7 KiB	16.8 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,870 KiB

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 5 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 130 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 10 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
KUBERNETES CONTRIBUTOR, HEAD OF PROJECTS AT CNCF `figure > figcaption > div.n-blockquote-author-info > span.n-blockquote-title`

These are opportunities to improve the legibility of your content.

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.

Failing Elements
Read our Privacy Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

●Input buttons have discernible text.

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

●Select elements have associated label elements.

●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

●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

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

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

○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

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

○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

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

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
cookiepedia.co.uk/giving-consent-to-cookies	More information

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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

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.

664 ms

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

941 ms

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

134 ms

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

0.004

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

958 ms

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.01 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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:24.371 source:map[column:69646 line:7 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.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:152.028 source:map[type:text value:[unattributed]]] map[reflowTime:18.645 source:map[column:81 line:177 type:source-location url:https://www.netlify.com/ urlProvider:network]] map[reflowTime:14.456 source:map[column:349419 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.js urlProvider:network]] map[reflowTime:9.915 source:map[column:161470 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.js urlProvider:network]] map[reflowTime:4.311 source:map[column:181 line:458 type:source-location url:https://www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js urlProvider:network]] map[reflowTime:1.756 source:map[column:303 line:104 type:source-location url:https://www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js urlProvider:network]] map[reflowTime:1.339 source:map[column:86058 line:44 type:source-location url:https://js.hs-analytics.net/analytics/1775319600000/7477936.js urlProvider:network]] map[reflowTime:0.702 source:map[column:101328 line:44 type:source-location url:https://js.hs-analytics.net/analytics/1775319600000/7477936.js urlProvider:network]] map[reflowTime:7.433 source:map[column:153 line:534 type:source-location url:https://www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js urlProvider:network]] map[reflowTime:1.526 source:map[column:17869 line:44 type:source-location url:https://js.hs-analytics.net/analytics/1775319600000/7477936.js urlProvider:network]] map[reflowTime:1.217 source:map[column:141 line:319 type:source-location url:https://www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js urlProvider:network]]]

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

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
cdn.cookielaw.org/consent/5dec0507-5e89-4bb4-8f2d-0872be7dd9dd/OtAutoBlock.js	7.0 KiB	233 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js	9.1 KiB
www.netlify.com/_astro/convince-your-boss.Bd6jOyPR.css	26.3 KiB
www.netlify.com/_astro/index._tGI3oyO.css	1.3 KiB	50 ms
www.netlify.com/_astro/index.CswAyQBw.css	7.9 KiB
www.netlify.com/_astro/index.DEYu2GN_.css	1.5 KiB

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

Request	Cache TTL	Transfer Size
js.hsforms.net/forms/v2.js	300.0 s	193.8 KiB
js.hs-analytics.net/analytics/1775319600000/7477936.js	300.0 s	43.1 KiB
cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.js	86400.0 s	103.0 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
js.hsadspixel.net/pixels.js	600.0 s	3.9 KiB
cdn.cookielaw.org/logos/static/ot_company_logo.png	86400.0 s	8.8 KiB
cdn.cookielaw.org/consent/5dec0507-5e89-4bb4-8f2d-0872be7dd9dd/OtAutoBlock.js	86400.0 s	7.0 KiB
js.hs-scripts.com/7477936.js	90.0 s	1.1 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.1 KiB
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB
www.gstatic.com/recaptcha/api2/info_2x.png	604800.0 s	689 B
www.gstatic.com/recaptcha/api2/refresh_2x.png	604800.0 s	624 B
www.gstatic.com/recaptcha/api2/audio_2x.png	604800.0 s	554 B
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	0 B

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.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	10 ms

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

Diagnostics

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.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	1.1 s	870 ms	152 ms
www.netlify.com/	849 ms	22 ms	4.8 ms
Unattributable	503 ms	96 ms	0.0 ms
js.hs-analytics.net/analytics/1775319600000/7477936.js	337 ms	216 ms	4.8 ms
js.hsforms.net/forms/v2.js	165 ms	128 ms	24 ms
cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.js	131 ms	79 ms	19 ms
www.netlify.com/_astro/preact.module.CoPo3ckA.js	55 ms	42 ms	0.1 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.6 s
Other	679 ms
Style & Layout	539 ms
Script Parsing & Compilation	212 ms
Rendering	146 ms
Garbage Collection	63 ms
Parse HTML & CSS	60 ms

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: 0.0 ms 17.0 KiB

URL	Transfer Size	Est Savings
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} …	19.7 KiB	17.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.

Estimated savings: 0.0 ms 584.3 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	362.6 KiB	247.0 KiB
www.gstatic.com/recaptcha/releases/kUYUkUlSyqkjTSMaN2w3RaOh/recaptcha__en.js	362.6 KiB	167.3 KiB
js.hsforms.net/forms/v2.js	186.4 KiB	71.9 KiB
cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.js	102.8 KiB	53.4 KiB
www.netlify.com/_astro/preact.DVUxKnXA.js	96.0 KiB	44.7 KiB

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

●Time to Interactive 2.0 s

●Max Potential First Input Delay 100 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,961 KiB

●Avoid long main-thread tasks 9 long tasks found

●Avoid non-composited animations 4 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 130 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 10 ms

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

Accessibility

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
KUBERNETES CONTRIBUTOR, HEAD OF PROJECTS AT CNCF `figure > figcaption > div.n-blockquote-author-info > span.n-blockquote-title`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Failing Elements
Toggle resources submenu `ul.menu > li.has-submenu > submenu-utils > button.submenu-toggle`

These items highlight common accessibility best practices.

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.

Failing Elements
Read our Privacy Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

●Input buttons have discernible text.

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

●Select elements have associated label elements.

●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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

○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

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

○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

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

SEO

Content Best Practices

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

Link destination	Link Text
cookiepedia.co.uk/giving-consent-to-cookies	More information

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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid

Results for https://www.netlify.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Best Practices

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Best practices

Best Practices

SEO

Content Best Practices

Keyboard Shortcuts