B — https://learn.microsoft.com

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)

'unsafe-eval' found in script source

Security › Content Security Policy

'unsafe-inline' found in script source

Security › Content Security Policy

2 button(s) with no accessible text

Accessibility › Link & Button Quality

3 control(s) without accessible label

Accessibility › Form Accessibility

Cross-Origin-Embedder-Policy header is missing

Security › Security Headers

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Flearn.microsoft.com)](https://beavercheck.com/results/2153356a-9df1-4cf5-86ac-633e528180b5)

HTML

<a href="https://beavercheck.com/results/2153356a-9df1-4cf5-86ac-633e528180b5"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Flearn.microsoft.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Flearn.microsoft.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

100

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

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

10.81 s

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

12.28 s

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

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

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

12.34 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.monitor.azure.com/scripts/c/ms.jsll-4.min.js	1800.0 s	73.6 KiB
learn.microsoft.com/en-us/media/event-banners/banner-build-2026.png	1244.0 s	62.0 KiB
wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js	300.0 s	52.2 KiB
learn.microsoft.com/en-us/media/home-and-directory/icon-azure-cloud.svg	336.0 s	37.3 KiB
learn.microsoft.com/en-us/media/common/ai-microchip.svg	682.0 s	7.1 KiB
learn.microsoft.com/akam/13/7e45086d	21600.0 s	9.6 KiB
learn.microsoft.com/en-us/media/learn/instructor-led-badge.svg	246.0 s	5.9 KiB
learn.microsoft.com/en-us/training/achievements/generic-badge.svg	1057.0 s	5.8 KiB
learn.microsoft.com/en-us/media/logos/logo_copilot.svg	682.0 s	2.9 KiB
learn.microsoft.com/en-us/media/logos/logo_azure.svg	1407.0 s	2.8 KiB

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

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
learn.microsoft.com/static/third-party/SegoeUIVariable/SegoeUI-VF.ttf	145 ms
/static/assets/0.4.03377.7675-f5f342ae/styles/docons.f5f3...	50 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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:39.486 source:map[column:6750 line:1 type:source-location url:https://learn.microsoft.com/akam/13/7e45086d urlProvider:network]] map[reflowTime:0.647 source:map[column:179964 line:60 type:source-location url:https://learn.microsoft.com/static/assets/0.4.03377.7675-f5f342ae/scripts/en-us/index-docs.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:380.56299999809266 label:Time to first byte subpart:timeToFirstByte] map[duration:1083.2790000019074 label:Resource load delay subpart:resourceLoadDelay] map[duration:47.475 label:Resource load duration subpart:resourceLoadDuration] map[duration:1051.203 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-SECTION

nodeLabel: Microsoft Build 2026 June 2-3, 2026 Learn more Dismiss alert

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

selector: header.layout-body-header > div.header-holder > div#banner-holder > section.tier1-event-banner

snippet: <section data-bi-name="tier1-event-banner" data-dismissable="disappearing" class="tier1-event-banner position-relative padding-block-md build-banner display…">

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

lhId: page-0-SECTION

nodeLabel: Microsoft Build 2026 June 2-3, 2026 Learn more Dismiss alert

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

selector: header.layout-body-header > div.header-holder > div#banner-holder > section.tier1-event-banner

snippet: <section data-bi-name="tier1-event-banner" data-dismissable="disappearing" class="tier1-event-banner position-relative padding-block-md build-banner display…">

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

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
js.monitor.azure.com/scripts/c/ms.jsll-4.min.js	73.6 KiB	1.8 s
wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js	52.2 KiB	1.7 s
/static/assets/0.4.03377.7675-f5f342ae/scripts/en-us/inde...	530.0 KiB	3.5 s
/_themes/docs.theme/master/en-us/_themes/global/deprecati...	2.5 KiB	150 ms
learn.microsoft.com/static/assets/0.4.03377.7675-f5f342ae/styles/site-ltr.css	69.2 KiB	751 ms

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

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

Estimated savings: 874 ms

URL	Time Spent
learn.microsoft.com/	874 ms
learn.microsoft.com/en-us/	0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

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: 180 ms 62.6 KiB

URL	Transfer Size	Est Savings
learn.microsoft.com/static/assets/0.4.03377.7675-f5f342ae/styles/site-ltr.css	68.2 KiB	62.6 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: 2.0 s 420.8 KiB

URL	Transfer Size	Est Savings
/static/assets/0.4.03377.7675-f5f342ae/scripts/en-us/inde...	529.0 KiB	362.6 KiB
wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js	51.5 KiB	29.1 KiB
js.monitor.azure.com/scripts/c/ms.jsll-4.min.js	72.6 KiB	29.0 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
The page has an unload handler in the main frame.	Actionable

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

●Layout shift culprits

●Optimize DOM size

●Improve image delivery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●JavaScript execution time 1.1 s

●Minimizes main-thread work 2.0 s

●Avoid long main-thread tasks 6 long tasks found

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

●Network Requests

●Network Round Trip Times 200 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●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

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

○Image elements have `[alt]` attributes

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

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	js.monitor.azure.com/scripts/c/ms.jsll-4.min.js line 5, col 58842

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

URL	Map URL
/static/assets/0.4.03377.7675-f5f342ae/scripts/en-us/inde...
js.monitor.azure.com/scripts/c/ms.jsll-4.min.js	js.monitor.azure.com/scripts/c/ms.jsll-4.3.12.min.js.map

●Uses HTTPS

●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

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

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

Link destination	Link Text
aka.ms/MSBuild_FY26_BN_MSLearn_Hero	Learn more

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

100

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

1.30 s

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

2.45 s

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

42 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.83 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.70 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
learn.microsoft.com/en-us/media/home-and-directory/home-hero_light.png	226.0 s	318.4 KiB
js.monitor.azure.com/scripts/c/ms.jsll-4.min.js	1800.0 s	73.6 KiB
learn.microsoft.com/en-us/media/event-banners/banner-build-2026.png	1223.0 s	62.0 KiB
wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js	300.0 s	52.2 KiB
learn.microsoft.com/en-us/media/home-and-directory/icon-azure-cloud.svg	316.0 s	37.3 KiB
learn.microsoft.com/en-us/media/home-and-directory/hero_mcp.png	662.0 s	20.9 KiB
learn.microsoft.com/en-us/media/common/ai-microchip.svg	662.0 s	7.0 KiB
learn.microsoft.com/akam/13/7e45086d	21600.0 s	9.6 KiB
learn.microsoft.com/en-us/media/learn/instructor-led-badge.svg	226.0 s	5.9 KiB
learn.microsoft.com/en-us/training/achievements/generic-badge.svg	1037.0 s	5.8 KiB
learn.microsoft.com/en-us/media/logos/logo_copilot.svg	662.0 s	2.9 KiB
learn.microsoft.com/en-us/media/logos/logo_azure.svg	1387.0 s	2.8 KiB

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

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
learn.microsoft.com/static/third-party/SegoeUIVariable/SegoeUI-VF.ttf	130 ms
/static/assets/0.4.03377.7675-f5f342ae/styles/docons.f5f3...	105 ms

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

items: [map[reflowTime:47.442 source:map[column:6786 line:1 type:source-location url:https://learn.microsoft.com/akam/13/7e45086d urlProvider:network]] map[reflowTime:0.531 source:map[column:179964 line:60 type:source-location url:https://learn.microsoft.com/static/assets/0.4.03377.7675-f5f342ae/scripts/en-us/index-docs.js urlProvider:network]]]

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

lhId: page-0-SECTION

nodeLabel: Learning for everyone, everywhere Explore Microsoft product documentation, tra…

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

selector: body#body > main#main > div#ms--homepage-container > section#ms--welcome-hero

snippet: <section id="ms--welcome-hero" data-bi-name="hero" class="hero hero-image gradient-border-right gradient-border-body-accent backgrou…" style="--hero-background-image-light: url("/media/home-and-directory/home-hero_li…;">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

title: Preconnected origins

value: no origins were preconnected

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

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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
wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js	52.2 KiB	455 ms
/_themes/docs.theme/master/en-us/_themes/global/deprecati...	2.5 KiB
/static/assets/0.4.03377.7675-f5f342ae/scripts/en-us/inde...	530.0 KiB	642 ms
learn.microsoft.com/static/assets/0.4.03377.7675-f5f342ae/styles/site-ltr.css	69.2 KiB	120 ms
js.monitor.azure.com/scripts/c/ms.jsll-4.min.js	73.6 KiB	367 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
main#main > div#ms--homepage-container > section#ms--welcome-hero > ::before `main#main > div#ms--homepage-container > section#ms--welcome-hero > ::before`	learn.microsoft.com/en-us/media/home-and-directory/home-hero_light.png	316.4 KiB	251.3 KiB

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

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

Estimated savings: 308 ms

URL	Time Spent
learn.microsoft.com/	308 ms
learn.microsoft.com/en-us/	0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

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: 70 ms 62.1 KiB

URL	Transfer Size	Est Savings
learn.microsoft.com/static/assets/0.4.03377.7675-f5f342ae/styles/site-ltr.css	68.2 KiB	62.1 KiB

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

Estimated savings: 280 ms 420.8 KiB

URL	Transfer Size	Est Savings
/static/assets/0.4.03377.7675-f5f342ae/scripts/en-us/inde...	529.0 KiB	362.6 KiB
wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js	51.5 KiB	29.1 KiB
js.monitor.azure.com/scripts/c/ms.jsll-4.min.js	72.6 KiB	29.0 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
The page has an unload handler in the main frame.	Actionable

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

●Max Potential First Input Delay 80 ms

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.5 s

●Avoid long main-thread tasks 2 long tasks found

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

●Network Requests

●Network Round Trip Times 200 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

100

Accessibility

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●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

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

○Image elements have `[alt]` attributes

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

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	js.monitor.azure.com/scripts/c/ms.jsll-4.min.js line 5, col 58842

URL	Map URL
/static/assets/0.4.03377.7675-f5f342ae/scripts/en-us/inde...
js.monitor.azure.com/scripts/c/ms.jsll-4.min.js	js.monitor.azure.com/scripts/c/ms.jsll-4.3.12.min.js.map

●Uses HTTPS

●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

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

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

Link destination	Link Text
aka.ms/MSBuild_FY26_BN_MSLearn_Hero	Learn more

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`

Results for https://learn.microsoft.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts