B — https://www.cncf.io | BeaverCheck Audit

Site Health

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

1 control(s) without accessible label

Accessibility › Form Accessibility

3 image-only link(s) without alt text

Accessibility › Link & Button Quality

No <main> landmark found

Accessibility › Landmark Structure

110 HTTP requests — consider bundling or reducing

Performance › Page Weight Budget

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.cncf.io)](https://beavercheck.com/results/ce52a069-b107-d68d-0ddb-02fdd75dd461)

HTML

<a href="https://beavercheck.com/results/ce52a069-b107-d68d-0ddb-02fdd75dd461"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.cncf.io" alt="BeaverCheck Score"></a>

Image URL

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

Accessibility

100

Best Practices

100

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.

2.67 s

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

4.26 s

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

94 ms

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

5.99 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
lfx-segment.platform.linuxfoundation.org/latest/lfx-segment-analytics.min.js	0.0 ms	82.8 KiB
browser-update.org/update.min.js	86400.0 s	4.6 KiB

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
www.cncf.io/wp-content/themes/cncf-twenty-two/source/fonts/ClarityCity-800.woff2	55 ms
www.cncf.io/wp-content/themes/cncf-twenty-two/source/fonts/ClarityCity-400.woff2	15 ms
www.cncf.io/wp-content/themes/cncf-twenty-two/source/fonts/ClarityCity-700.woff2	10 ms
www.cncf.io/wp-content/themes/cncf-twenty-two/source/fonts/ClarityCity-600.woff2	10 ms

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
Make cloud native ubiquitous `body.home > section.home-hero > picture > img.home-hero__poster`	www.cncf.io/wp-content/themes/cncf-twenty-two/images/home-hero-poster2.webp	63.7 KiB	27.3 KiB
Goldie `div.home-intro-boxes > div.home-intro-box > picture > img.home-intro-box__goldie`	www.cncf.io/wp-content/themes/cncf-twenty-two/images/home-goldie.webp	13.5 KiB	12.7 KiB

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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
lfx-segment.platform.linuxfoundation.org/latest/lfx-segment-analytics.min.js	82.8 KiB	1.5 s
/wp-content/themes/cncf-twenty-two/build/styles.min.css?v...	32.4 KiB	451 ms
www.cncf.io/wp-content/themes/cncf-twenty-two/build/slick.min.css?ver=1775551542	1.3 KiB

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 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: 150 ms 26.4 KiB

URL	Transfer Size	Est Savings
/wp-content/themes/cncf-twenty-two/build/styles.min.css?v...	32.2 KiB	26.4 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: 150 ms 27.5 KiB

URL	Transfer Size	Est Savings
lfx-segment.platform.linuxfoundation.org/latest/lfx-segment-analytics.min.js	81.9 KiB	27.5 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
Other	1.5 s
Script Evaluation	636 ms
Style & Layout	597 ms
Rendering	235 ms
Parse HTML & CSS	65 ms
Script Parsing & Compilation	53 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
www.cncf.io/wp-content/themes/cncf-twenty-two/source/videos/hero.mp4	2.9 MiB
lfx-segment.platform.linuxfoundation.org/latest/lfx-segment-analytics.min.js	82.8 KiB
www.cncf.io/wp-content/themes/cncf-twenty-two/images/home-hero-poster2.webp	64.2 KiB
www.cncf.io/	54.1 KiB
www.cncf.io/wp-content/uploads/2024/11/CNCF-Website-Mobile-1.png	43.2 KiB
www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Mobile-1.png	35.7 KiB
www.cncf.io/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	35.1 KiB
/wp-content/themes/cncf-twenty-two/build/styles.min.css?v...	32.4 KiB
www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Mobile.png	32.3 KiB
www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Mobile-Clouds.png	29.5 KiB

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

	URL
KubeCon + CloudNativeCon India 2026 `div > a > picture > img`	www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Mobile-Clouds.png
KubeCon + CloudNativeCon Japan 2026 `div > a > picture > img`	www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Mobile.png
KubeCon + CloudNativeCon + OpenInfra Summit + PyTorch Conference China 2026 `div > a > picture > img`	www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Mobile-1.png
KubeCon + CloudNativeCon North America 2026 `div > a > picture > img`	www.cncf.io/wp-content/uploads/2024/11/CNCF-Website-Mobile-1.png
Goldie `div.home-intro-boxes > div.home-intro-box > picture > img.home-intro-box__goldie`	www.cncf.io/wp-content/themes/cncf-twenty-two/images/home-goldie.webp

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

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●JavaScript execution time 0.6 s

●Avoid long main-thread tasks 9 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 220 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

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

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Failing Elements
Logo of KubeEdge `div.slider > div.slick-list > div.slick-track > div.slick-slide`
Logo of Istio `div.slider > div.slick-list > div.slick-track > div.slick-slide`

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html.no-focus-outline `html.no-focus-outline`

These items highlight common accessibility best practices.

○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

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

●ARIA attributes are used as specified for the element's role

●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 are distinguishable without relying on color.

●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

●Deprecated ARIA roles were not used

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

●Identical links have the same purpose.

○`[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 type="image">` elements have `[alt]` text

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

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

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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

100

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.

○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 have descriptive text

●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

100

Best Practices

100

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.

845 ms

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

1.62 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.001

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

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

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
lfx-segment.platform.linuxfoundation.org/latest/lfx-segment-analytics.min.js	0.0 ms	82.8 KiB
browser-update.org/update.min.js	86400.0 s	4.6 KiB

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
www.cncf.io/wp-content/themes/cncf-twenty-two/source/fonts/ClarityCity-400.woff2	155 ms
www.cncf.io/wp-content/themes/cncf-twenty-two/source/fonts/ClarityCity-700.woff2	105 ms
www.cncf.io/wp-content/themes/cncf-twenty-two/source/fonts/ClarityCity-600.woff2	100 ms
www.cncf.io/wp-content/themes/cncf-twenty-two/source/fonts/ClarityCity-800.woff2	35 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:39.021 source:map[column:27323 line:2 type:source-location url:https://www.cncf.io/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 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:4.522 source:map[column:50335 line:1 type:source-location url:https://www.cncf.io/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.277 source:map[column:50393 line:1 type:source-location url:https://www.cncf.io/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.233 source:map[column:50457 line:1 type:source-location url:https://www.cncf.io/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:33.782 source:map[column:49615 line:1 type:source-location url:https://www.cncf.io/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.541 source:map[column:51395 line:1 type:source-location url:https://www.cncf.io/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.451 source:map[column:49637 line:1 type:source-location url:https://www.cncf.io/wp/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.805 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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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
lfx-segment.platform.linuxfoundation.org/latest/lfx-segment-analytics.min.js	82.8 KiB	491 ms
www.cncf.io/wp-content/themes/cncf-twenty-two/build/slick.min.css?ver=1775551542	1.2 KiB
/wp-content/themes/cncf-twenty-two/build/styles.min.css?v...	32.4 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
Make cloud native ubiquitous `body.home > section.home-hero > picture > img.home-hero__poster`	www.cncf.io/wp-content/themes/cncf-twenty-two/images/home-hero-poster2.webp	63.7 KiB	46.3 KiB
Dmitri Telinov – Kubestronaut in Orbit `div.home-ambassadors > div.home-ambassadors-heptagons > a.home-ambassadors-heptagons__link > img.home-ambassadors-heptagons__image`	www.cncf.io/wp-content/uploads/2022/07/Nikhita-Raghynath-900x1032.jpg	44.3 KiB	40.9 KiB
Mitch Connors – From Biblical Studies to programming at Google & Amazon `div.home-ambassadors > div.home-ambassadors-heptagons > a.home-ambassadors-heptagons__link > img.home-ambassadors-heptagons__image`	www.cncf.io/wp-content/uploads/2023/03/Queeny-Jin.jpg	12.0 KiB	10.7 KiB

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

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: 60 ms 27.5 KiB

URL	Transfer Size	Est Savings
lfx-segment.platform.linuxfoundation.org/latest/lfx-segment-analytics.min.js	81.9 KiB	27.5 KiB

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

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 21.7 KiB

URL	Transfer Size	Est Savings
/wp-content/themes/cncf-twenty-two/build/styles.min.css?v...	32.1 KiB	21.7 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
www.cncf.io/wp-content/themes/cncf-twenty-two/source/videos/hero.mp4	2.9 MiB
www.cncf.io/wp-content/uploads/2023/06/mercedes-logo.svg	100.9 KiB
www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Desktop-Clouds.png	96.3 KiB
www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Desktop.png	88.8 KiB
www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Desktop-2.jpg	84.1 KiB
lfx-segment.platform.linuxfoundation.org/latest/lfx-segment-analytics.min.js	82.8 KiB
www.cncf.io/wp-content/themes/cncf-twenty-two/images/home-hero-poster2.webp	64.3 KiB
www.cncf.io/	54.1 KiB
www.cncf.io/wp-content/uploads/2022/07/Nikhita-Raghynath-900x1032.jpg	44.8 KiB
www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Desktop-1.png	42.5 KiB

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

	URL
KubeCon + CloudNativeCon India 2026 `div > a > picture > img`	www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Desktop-Clouds.png
KubeCon + CloudNativeCon Japan 2026 `div > a > picture > img`	www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Desktop.png
KubeCon + CloudNativeCon + OpenInfra Summit + PyTorch Conference China 2026 `div > a > picture > img`	www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Desktop-1.png
KubeCon + CloudNativeCon North America 2026 `div > a > picture > img`	www.cncf.io/wp-content/uploads/2026/02/CNCF-Website-Desktop-2.jpg
Goldie `div.home-intro-boxes > div.home-intro-box > picture > img.home-intro-box__goldie`	www.cncf.io/wp-content/themes/cncf-twenty-two/images/home-goldie.webp

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

●Time to Interactive 1.7 s

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 50 ms

●Minify CSS

●Minify JavaScript

●JavaScript execution time 0.2 s

●Minimizes main-thread work 1.1 s

●Avoid long main-thread tasks 1 long task found

●Avoid non-composited animations 1 animated element found

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 110 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 0 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

Accessibility

ARIA

Failing Elements
Logo of KubeEdge `div.slider > div.slick-list > div.slick-track > div.slick-slide`
Logo of Istio `div.slider > div.slick-list > div.slick-track > div.slick-slide`

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html.no-focus-outline `html.no-focus-outline`

These items highlight common accessibility best practices.

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

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

●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 are distinguishable without relying on color.

●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

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

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

○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

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

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

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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

100

SEO

○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 have descriptive text

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

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Best practices

Best Practices

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Best practices

Best Practices

SEO

Keyboard Shortcuts