Skip to content
https://www.visualstudio.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

74

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:16.748 source:map[column:436 line:179 type:source-location url:https://visualstudio.microsoft.com/wp-content/uploads/fusion-scripts/c75bede5d1d99a50d805f72c5e34a73e.min.js?ver=3.14.2 urlProvider:network]] map[reflowTime:1.677 source:map[column:461 line:179 type:source-location url:https://visualstudio.microsoft.com/wp-content/uploads/fusion-scripts/c75bede5d1d99a50d805f72c5e34a73e.min.js?ver=3.14.2 urlProvider:network]] map[reflowTime:3.293 source:map[column:131 line:350 type:source-location url:https://visualstudio.microsoft.com/wp-content/uploads/fusion-scripts/c75bede5d1d99a50d805f72c5e34a73e.min.js?ver=3.14.2 urlProvider:network]] map[reflowTime:17.165 source:map[column:24649 line:607 type:source-location url:https://visualstudio.microsoft.com/wp-content/uploads/fusion-scripts/c75bede5d1d99a50d805f72c5e34a73e.min.js?ver=3.14.2 urlProvider:network]] map[reflowTime:0.291 source:map[column:5467 line:607 type:source-location url:https://visualstudio.microsoft.com/wp-content/uploads/fusion-scripts/c75bede5d1d99a50d805f72c5e34a73e.min.js?ver=3.14.2 urlProvider:network]] map[reflowTime:0.341 source:map[column:1968 line:607 type:source-location url:https://visualstudio.microsoft.com/wp-content/uploads/fusion-scripts/c75bede5d1d99a50d805f72c5e34a73e.min.js?ver=3.14.2 urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div.fusion-column-wrapper > div.fusion-video > div.video-wrapper > video div.fusion-column-wrapper > div.fusion-video > div.video-wrapper > video
visualstudio.microsoft.com/wp-content/uploads/2025/11/Dev18_Thumbnail_V1.webp2.4 MiB2.4 MiB
div.fusion-layout-column > div.fusion-column-wrapper > span.fusion-imageframe > img.img-responsive div.fusion-layout-column > div.fusion-column-wrapper > span.fusion-imageframe > img.img-responsive
visualstudio.microsoft.com/wp-content/uploads/2025/12/realmadrid-400x172.webp21.1 KiB9.9 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 205 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 80 ms 161.4 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.2 KiB
URLTransfer SizeEst Savings
/wp-content/themes/Avada-Child-Theme/vscom-reimagine.css?...7.4 KiB2.2 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 4.8 KiB
URLTransfer SizeEst Savings
inline: //load newrelic if user has consent …13.6 KiB4.8 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.theme-light > div.c-uhfh-gcontainer-st > a#uhfLogo > img.c-image div.theme-light > div.c-uhfh-gcontainer-st > a#uhfLogo > img.c-image
uhf.microsoft.com/images/microsoft/RE1Mu3b.png
Visual Studio on Twitter div.vscom-social-media-inner > div.vscom-social-media-column > a > img
visualstudio.microsoft.com/wp-content/uploads/2024/01/X-logo.svg
Visual Studio on Facebook div.vscom-social-media-inner > div.vscom-social-media-column > a > img
visualstudio.microsoft.com/wp-content/uploads/2024/01/Facebook.svg
Visual Studio on Linkedin div.vscom-social-media-inner > div.vscom-social-media-column > a > img
visualstudio.microsoft.com/wp-content/uploads/2024/01/Linkedin.svg
Visual Studio on Youtube div.vscom-social-media-inner > div.vscom-social-media-column > a > img
visualstudio.microsoft.com/wp-content/uploads/2024/01/Youtube.svg
Visual Studio on TikTok div.vscom-social-media-inner > div.vscom-social-media-column > a > img
visualstudio.microsoft.com/wp-content/uploads/2024/10/Tiktok.svg
Visual Studio on Bluesky div.vscom-social-media-inner > div.vscom-social-media-column > a > img
visualstudio.microsoft.com/wp-content/uploads/2025/03/footer-social-bluesky.svg

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

Layout shift culprits
Optimize DOM size
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 50 ms
User Timing marks and measures 4 user timings
JavaScript execution time 0.4 s
Minimizes main-thread work 1.3 s
Avoid long main-thread tasks 2 long tasks found
Network Requests
Network Round Trip Times 150 ms
Server Backend Latencies 190 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 10 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
Avoid non-composited animations
96

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Your Privacy Choices div#footerUniversalFooter > footer#uhf-footer > div.c-uhff-base > a.c-uhff-link

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
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Select elements have associated label elements.
ARIA attributes are used as specified for the element's role
`[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
No element has a `[tabindex]` value greater than 0
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`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
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Access to XMLHttpRequest at 'https://spsprodsbr1.vssps.visualstudio.com/_signin?realm=app.vssps.visualstudio.com&reply_to=https%3A%2F%2Fapp.vssps.visualstudio.com%2F_apis%2Fprofile%2Fprofiles%2Fme%3F_%3D1775327314601&redirect=1&context=eyJodCI6MywiaGlkIjoiYzIyMTEzN2EtNGMzOC00NGE2LWFhMDEtNDYwYjk3MWNmMTFmIiwicXMiOnt9LCJyciI6IiIsInZoIjoiIiwiY3YiOiIiLCJjcyI6IiJ90&lltid=bc9ce7e0-91fc-42b3-98f0-87c2cb9ce523#ctx=eyJTaWduSW5Db29raWVEb21haW5zIjpbImh0dHBzOi8vbG9naW4ubWljcm9zb2Z0b25saW5lLmNvbSIsImh0dHBzOi8vbG9naW4ubWljcm9zb2Z0b25saW5lLmNvbSJdfQ2' (redirected from 'https://app.vssps.visualstudio.com/_apis/profile/profiles/me?_=1775327314601') from origin 'https://visualstudio.microsoft.com' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
Failed to load resource: net::ERR_FAILED
Uncaught NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
Uncaught NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
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 issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
85

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
aka.ms/MSBuildFY26_BN_VisualStudio_RegLearn more

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
body.home > footer > section > a.fusion-one-page-text-link body.home > footer > section > a.fusion-one-page-text-link

To appear in search results, crawlers need access to your app.

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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback