C — https://kubernetes.io | BeaverCheck Audit

Site Health

Score: 77 / 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 button(s) with no accessible text

Accessibility › Link & Button Quality

5 link(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%2Fkubernetes.io)](https://beavercheck.com/results/6b370530-f1bb-4b86-b8a7-28ed882c4baf)

HTML

<a href="https://beavercheck.com/results/6b370530-f1bb-4b86-b8a7-28ed882c4baf"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fkubernetes.io" alt="BeaverCheck Score"></a>

Image URL

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

SEO

Core Web Vitals

Key metrics that affect user experience.

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

5.08 s

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

13.99 s

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

193 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.92 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.

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

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

lhId: page-0-SECTION

nodeLabel: Production-Grade Container Orchestration

path: 1,HTML,1,BODY,0,HEADER,1,SECTION

selector: body.td-home > header > section.header-hero

snippet: <section class="header-hero text-white pb-4 light-text bot-bar">

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
fonts.googleapis.com/css2?family=Tajawal:wght@300;400;500;700&display=swap	737 B
/css?family=Open+Sans:300,300i,400,400i,700,700i&display=...	2.2 KiB	811 ms
fonts.googleapis.com/css2?family=Rubik:wght@300;400;500;600;700&display=swap	1.4 KiB	150 ms
code.jquery.com/jquery-3.6.0.min.js	30.5 KiB	1.2 s
cdn.jsdelivr.net/gh/rastikerdar/vazir-font@v27.0.1/dist/font-face.css	759 B	752 ms
kubernetes.io/js/legacy-script.js	3.5 KiB	150 ms

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

Request	Cache TTL	Transfer Size
cse.google.com/cse.js?cx=013288817511911618469:elfqqbqldzg	0.0 ms	3.5 KiB
www.google.com/cse/static/style/look/v6/default.css	3000.0 s	1.2 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
kubernetes.io/webfonts/fa-solid-900.woff2	10 ms
kubernetes.io/webfonts/fa-brands-400.woff2	10 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 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: 300 ms 65.7 KiB

URL	Transfer Size	Est Savings
/scss/main.min.8ed3ebfd8c53cb1132bfb692d556bed40d26703d3d...	68.0 KiB	65.7 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: 700 ms 133.8 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-JPP6RFM2BP	170.3 KiB	67.0 KiB
/cse/static/element/b33cba5881f68fbf/cse_element__en.js?u...	98.5 KiB	66.8 KiB

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

Category	Time Spent
Script Evaluation	827 ms
Other	638 ms
Style & Layout	468 ms
Script Parsing & Compilation	148 ms
Parse HTML & CSS	144 ms
Rendering	28 ms
Garbage Collection	27 ms

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

Estimated savings: 0.0 ms 2.8 KiB

URL	Transfer Size	Est Savings
www.google.com/cse/static/element/b33cba5881f68fbf/default_v6+en.css	9.7 KiB	2.8 KiB

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

	URL
section#td-block-0-section > div.main-section > div.image-wrapper > img `section#td-block-0-section > div.main-section > div.image-wrapper > img`	kubernetes.io/_common-resources/images/flower.svg
section#td-block-0-section > div.main-section > div.image-wrapper > img `section#td-block-0-section > div.main-section > div.image-wrapper > img`	kubernetes.io/_common-resources/images/suitcase.svg
Cloud Native Computing Foundation logo `div.main-section > div.cncf-logo-details > picture > img.cncf-img`	kubernetes.io/images/cncf-logo-white.svg
section#td-block-0-section > div.main-section > div.image-wrapper > img `section#td-block-0-section > div.main-section > div.image-wrapper > img`	kubernetes.io/_common-resources/images/scalable.svg
section#td-block-0-section > div.main-section > div.image-wrapper > img `section#td-block-0-section > div.main-section > div.image-wrapper > img`	kubernetes.io/_common-resources/images/blocks.svg
Booz Allen Case Study `div.case-study-list > div.case-study-item > picture > img`	kubernetes.io/case-studies/booz-allen/booz-allen_featured_logo.svg
Booking.com Case Study `div.case-study-list > div.case-study-item > picture > img`	kubernetes.io/case-studies/booking-com/booking.com_featured_logo.svg
Babylon Case Study `div.case-study-list > div.case-study-item > picture > img`	kubernetes.io/case-studies/babylon/babylon_featured_logo.svg
AppDirect Case Study `div.case-study-list > div.case-study-item > picture > img`	kubernetes.io/case-studies/appdirect/appdirect_featured_logo.svg

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

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,047 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.9 s

●Avoid long main-thread tasks 9 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 50 ms

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

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Failing Elements
body.td-home > header > nav.js-navbar-scroll > button#hamburger `body.td-home > header > nav.js-navbar-scroll > button#hamburger`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
body.td-home > header > nav.js-navbar-scroll > a.navbar-brand `body.td-home > header > nav.js-navbar-scroll > a.navbar-brand`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

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

Failing Elements
Automated rollouts and rollbacks `div > div.feature-box > h3 > a`
Service discovery and load balancing `div > div.feature-box > h3 > a`
Storage orchestration `div > div.feature-box > h3 > a`
Secret and configuration management `div > div.feature-box > h3 > a`
Automatic bin packing `div > div.feature-box > h3 > a`
Batch execution `div > div.feature-box > h3 > a`
Self-healing `div > div.feature-box > h3 > a`
Horizontal scaling `div > div.feature-box > h3 > a`
Vertical scaling `div > div.feature-box > h3 > a`
IPv4/IPv6 dual-stack `div > div.feature-box > h3 > a`
Designed for extensibility `div > div.feature-box > h3 > a`

These are opportunities to improve the legibility of your content.

Navigation

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

Failing Elements
Planet scale `section#td-block-0-section > div.main-section > div.content > h4#planet-scale`

These are opportunities to improve keyboard navigation in your application.

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
Learn Kubernetes Basics `div.td-outer > main.td-main > section.row > a`

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

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

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

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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 buttons have discernible text.

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

○No element has a `[tabindex]` value greater than 0

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

○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

●Use a strong HSTS policy

●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

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
kubernetes.io/case-studies/babylon/	Read more
kubernetes.io/case-studies/booz-allen/	Read more
kubernetes.io/case-studies/booking-com/	Read more
kubernetes.io/case-studies/appdirect/	Read more

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

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.

879 ms

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

2.05 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.006

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

912 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.05 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.

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

lhId: page-0-SECTION

nodeLabel: Production-Grade Container Orchestration

path: 1,HTML,1,BODY,0,HEADER,1,SECTION

selector: body.td-home > header > section.header-hero

snippet: <section class="header-hero text-white pb-4 light-text bot-bar">

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
fonts.googleapis.com/css2?family=Tajawal:wght@300;400;500;700&display=swap	714 B
/css?family=Open+Sans:300,300i,400,400i,700,700i&display=...	2.2 KiB	261 ms
fonts.googleapis.com/css2?family=Rubik:wght@300;400;500;600;700&display=swap	1.4 KiB
cdn.jsdelivr.net/gh/rastikerdar/vazir-font@v27.0.1/dist/font-face.css	1.0 KiB	210 ms
code.jquery.com/jquery-3.6.0.min.js	30.5 KiB	287 ms
kubernetes.io/js/legacy-script.js	3.5 KiB

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

Request	Cache TTL	Transfer Size
cse.google.com/cse.js?cx=013288817511911618469:elfqqbqldzg	0.0 ms	3.8 KiB
www.google.com/cse/static/style/look/v6/default.css	3000.0 s	1.2 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
kubernetes.io/webfonts/fa-brands-400.woff2	15 ms
kubernetes.io/webfonts/fa-solid-900.woff2	10 ms

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: 80 ms 65.0 KiB

URL	Transfer Size	Est Savings
/scss/main.min.8ed3ebfd8c53cb1132bfb692d556bed40d26703d3d...	68.0 KiB	65.0 KiB

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

Estimated savings: 0.0 ms 2.8 KiB

URL	Transfer Size	Est Savings
www.google.com/cse/static/element/b33cba5881f68fbf/default_v6+en.css	9.7 KiB	2.8 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 134.1 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-JPP6RFM2BP	170.3 KiB	67.3 KiB
/cse/static/element/b33cba5881f68fbf/cse_element__en.js?u...	98.5 KiB	66.8 KiB

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

	URL
section#td-block-0-section > div.main-section > div.image-wrapper > img `section#td-block-0-section > div.main-section > div.image-wrapper > img`	kubernetes.io/_common-resources/images/flower.svg
section#td-block-0-section > div.main-section > div.image-wrapper > img `section#td-block-0-section > div.main-section > div.image-wrapper > img`	kubernetes.io/_common-resources/images/suitcase.svg
Cloud Native Computing Foundation logo `div.main-section > div.cncf-logo-details > picture > img.cncf-img`	kubernetes.io/images/cncf-logo-white.svg
section#td-block-0-section > div.main-section > div.image-wrapper > img `section#td-block-0-section > div.main-section > div.image-wrapper > img`	kubernetes.io/_common-resources/images/scalable.svg
section#td-block-0-section > div.main-section > div.image-wrapper > img `section#td-block-0-section > div.main-section > div.image-wrapper > img`	kubernetes.io/_common-resources/images/blocks.svg
Booz Allen Case Study `div.case-study-list > div.case-study-item > picture > img`	kubernetes.io/case-studies/booz-allen/booz-allen_featured_logo.svg
Booking.com Case Study `div.case-study-list > div.case-study-item > picture > img`	kubernetes.io/case-studies/booking-com/booking.com_featured_logo.svg
Babylon Case Study `div.case-study-list > div.case-study-item > picture > img`	kubernetes.io/case-studies/babylon/babylon_featured_logo.svg
AppDirect Case Study `div.case-study-list > div.case-study-item > picture > img`	kubernetes.io/case-studies/appdirect/appdirect_featured_logo.svg

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

●Time to Interactive 2.1 s

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 40 ms

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,194 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.6 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 70 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 1 layout shift found

○INP breakdown

○Avoid long main-thread tasks

○Avoid non-composited animations

Accessibility

Contrast

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

Failing Elements
Automated rollouts and rollbacks `div > div.feature-box > h3 > a`
Service discovery and load balancing `div > div.feature-box > h3 > a`
Storage orchestration `div > div.feature-box > h3 > a`
Secret and configuration management `div > div.feature-box > h3 > a`
Automatic bin packing `div > div.feature-box > h3 > a`
Batch execution `div > div.feature-box > h3 > a`
Self-healing `div > div.feature-box > h3 > a`
Horizontal scaling `div > div.feature-box > h3 > a`
Vertical scaling `div > div.feature-box > h3 > a`
IPv4/IPv6 dual-stack `div > div.feature-box > h3 > a`
Designed for extensibility `div > div.feature-box > h3 > a`

These are opportunities to improve the legibility of your content.

Navigation

Failing Elements
Planet scale `section#td-block-0-section > div.main-section > div.content > h4#planet-scale`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Failing Elements
body.td-home > header > nav.js-navbar-scroll > a.navbar-brand `body.td-home > header > nav.js-navbar-scroll > a.navbar-brand`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
Learn Kubernetes Basics `div.td-outer > main.td-main > section.row > a`

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

●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

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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 buttons have discernible text.

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

○No element has a `[tabindex]` value greater than 0

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

○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

●Use a strong HSTS policy

●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

SEO

Content Best Practices

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

Link destination	Link Text
kubernetes.io/case-studies/babylon/	Read more
kubernetes.io/case-studies/booz-allen/	Read more
kubernetes.io/case-studies/booking-com/	Read more
kubernetes.io/case-studies/appdirect/	Read 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`

Results for https://kubernetes.io

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Contrast

Navigation

Best practices

Best Practices

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Navigation

Names and labels

Best practices

Best Practices

SEO

Content Best Practices

Keyboard Shortcuts