Skip to content
https://web.skype.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.

26

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
wcpstatic.microsoft.com/mscc/lib/v2/wcp-consent.js300.0 s273.7 KiB
/evergreen-assets/gather/images/insider-blog/insider-blog...390932.0 s1.2 MiB
/evergreen-assets/gather/videos/hero-video-placeholder.webp119767.0 s207.6 KiB
/evergreen-assets/gather/images/bento/share-meeting-fr.webp119767.0 s30.2 KiB
/evergreen-assets/gather/images/bento/background-bg.webp88039.0 s26.4 KiB
/evergreen-assets/gather/images/bento/background-fr.webp528983.0 s35.8 KiB
statics.teams.cdn.live.net/evergreen-assets/gather/images/bento/meeting-fr.webp296210.0 s20.0 KiB
statics.teams.cdn.live.net/evergreen-assets/gather/images/bento/emoji-fr.webp296210.0 s13.1 KiB
statics.teams.cdn.live.net/evergreen-assets/gather/images/bento/share-fr.webp249202.0 s9.5 KiB
/evergreen-assets/gather/images/bento/share-meeting-bg.webp390932.0 s11.6 KiB
statics.teams.cdn.live.net/evergreen-assets/icons/Teams_Logo_v2025_80x80.png217007.0 s7.0 KiB
statics.teams.cdn.live.net/evergreen-assets/gather/images/bento/caption-fr.webp523186.0 s13.2 KiB
/evergreen-assets/gather/images/icons/from_skype/teams-lo...134212.0 s1.3 KiB
/evergreen-assets/gather/images/icons/link-filled-32.svg70543.0 s809 B
/evergreen-assets/gather/images/icons/closed-caption-fill...119766.0 s862 B
/evergreen-assets/gather/images/icons/screen-share-start-...99732.0 s790 B
/evergreen-assets/gather/images/icons/question-circle-fil...114141.0 s810 B
statics.teams.cdn.live.net/evergreen-assets/gather/images/icons/video-28.svg134212.0 s826 B
statics.teams.cdn.live.net/evergreen-assets/gather/images/icons/play-24.svg134213.0 s775 B
/evergreen-assets/gather/images/icons/from_skype/arrow-do...240572.0 s1.0 KiB
statics.teams.cdn.live.net/evergreen-assets/gather/images/icons/person-20.svg217008.0 s867 B
/evergreen-assets/gather/images/icons/number-symbol-squar...240572.0 s886 B
/evergreen-assets/gather/images/icons/video-filled-32.svg214108.0 s769 B
statics.teams.cdn.live.net/evergreen-assets/gather/images/privacy-options.svg260188.0 s944 B
/evergreen-assets/gather/images/icons/arrow-download-fill...297188.0 s849 B
/evergreen-assets/gather/images/insider-blog/update.svg378483.0 s938 B
statics.teams.cdn.live.net/evergreen-assets/gather/images/icons/video-20.svg281425.0 s786 B
/evergreen-assets/gather/images/icons/video-background-ef...478360.0 s1.0 KiB
/evergreen-assets/gather/images/icons/emoj-laugh-filled-3...528982.0 s870 B
statics.teams.cdn.live.net/evergreen-assets/gather/images/icons/pause-24.svg482415.0 s763 B

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:80.023 source:map[type:text value:[unattributed]]]]

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
See what's new! Read about new features and improvements in Teams Updates div.gather-layout > main.gather-layout__main > div.gather-layout__main__inner > div.gather-whats-new-section
/evergreen-assets/gather/images/insider-blog/insider-blog...1.2 MiB1.0 MiB
div.gather-hero__media > div.gather-hero__media__inner > picture#GATHER-HERO-VIDEO-PLACEHOLDER > img.gather-hero-placeholder-img div.gather-hero__media > div.gather-hero__media__inner > picture#GATHER-HERO-VIDEO-PLACEHOLDER > img.gather-hero-placeholder-img
/evergreen-assets/gather/videos/hero-video-placeholder.webp208.0 KiB185.5 KiB
Family using Teams for event video chat div.gather-bento-grid > div.gather-bento-grid__item > p.gather-hide-when-media-mobile > img.gather-bento-image
/evergreen-assets/gather/images/bento/background-fr.webp35.3 KiB28.6 KiB
Collaborate together on Teams video calls div.gather-bento-grid > div.gather-bento-grid__item > p > img.gather-bento-image
/evergreen-assets/gather/images/bento/share-meeting-fr.webp29.6 KiB20.1 KiB
div.gather-bento-grid > div.gather-bento-grid__item > p.gather-hide-when-media-mobile > img.gather-bento-image div.gather-bento-grid > div.gather-bento-grid__item > p.gather-hide-when-media-mobile > img.gather-bento-image
statics.teams.cdn.live.net/evergreen-assets/gather/images/bento/meeting-fr.webp19.4 KiB14.4 KiB
Free Teams meeting for your own personal business div.gather-bento-grid > div.gather-bento-grid__item > p.gather-hide-when-media-mobile > img.gather-bento-image
statics.teams.cdn.live.net/evergreen-assets/gather/images/bento/emoji-fr.webp12.6 KiB10.6 KiB
Communicating in different languages div.gather-bento-grid > div.gather-bento-grid__item > p.gather-hide-when-media-mobile > img.gather-bento-image
statics.teams.cdn.live.net/evergreen-assets/gather/images/bento/caption-fr.webp12.7 KiB10.2 KiB
Collaborate together on Teams video calls div.gather-bento-grid > div.gather-bento-grid__item > p.gather-hide-when-media-mobile > img.gather-bento-image
statics.teams.cdn.live.net/evergreen-assets/gather/images/bento/share-fr.webp8.9 KiB6.6 KiB
header#GATHER_LAYOUT_HEADER > div.gather-layout__header__inner > a.gather-layout__header__title > img.gather-layout__header__title__image header#GATHER_LAYOUT_HEADER > div.gather-layout__header__inner > a.gather-layout__header__title > img.gather-layout__header__title__image
statics.teams.cdn.live.net/evergreen-assets/icons/Teams_Logo_v2025_80x80.png6.5 KiB6.4 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-1-IMG
nodeLabel: div.gather-hero__media > div.gather-hero__media__inner > picture#GATHER-HERO-VIDEO-PLACEHOLDER > img.gather-hero-placeholder-img
path: 1,HTML,1,BODY,0,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,4,IMG
selector: div.gather-hero__media > div.gather-hero__media__inner > picture#GATHER-HERO-VIDEO-PLACEHOLDER > img.gather-hero-placeholder-img
snippet: <img alt="" aria-hidden="true" loading="lazy" src="https://statics.teams.cdn.live.net/evergreen-assets/gather/videos/hero-vid…" class="gather-hero-placeholder-img">

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.

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

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.

Lists the toplevel main thread tasks that executed during page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Collection of useful page vitals.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 5.1 s
URLTime Spent
web.skype.com/248 ms
teams.live.com/v2323 ms
teams.live.com/v2/4.6 s
teams.live.com/gather?source=RWCNotSignedIn0.0 ms
teams.live.com/free/?source=RWCNotSignedIn0.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

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: 40 ms 23.5 KiB
URLTransfer SizeEst Savings
/teams-modular-packages/hashed-assets/688-aefeb25c1246ebc...32.2 KiB23.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

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
Pages with cache-control:no-store header cannot enter back/forward cache.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.5 KiB
URLTransfer SizeEst Savings
/* ========== Variables. ========== */ :root { --gather-layout-inner-max-width: 2000px; … } …7.3 KiB2.5 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
/teams-modular-packages/hashed-assets/async-entry-a734f97...2.5 MiB
/evergreen-assets/gather/images/insider-blog/insider-blog...1.2 MiB
/teams-modular-packages/hashed-assets/precompiled-web-wor...1016.1 KiB
/teams-modular-packages/hashed-assets/precompiled-web-wor...866.9 KiB
/teams-modular-packages/hashed-assets/989649-18356b8a2fc2...790.3 KiB
/teams-modular-packages/hashed-assets/precompiled-web-wor...724.4 KiB
/teams-modular-packages/hashed-assets/precompiled-web-wor...718.4 KiB
/teams-modular-packages/hashed-assets/precompiled-web-wor...669.4 KiB
/teams-modular-packages/hashed-assets/868593-04718eb3f10d...598.6 KiB
/teams-modular-packages/hashed-assets/griffel-087dd68bc70...346.5 KiB

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

●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 434 user timings
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 110 ms
●Server Backend Latencies 220 ms
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 120 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
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
●`[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 have a discernible name
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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
○Form elements have associated labels
○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
○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
○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.
○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.
81

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.
/teams-modular-packages/hashed-assets/251003-251f3ab248db... line 4, col 24393
Unload event listeners are deprecated and will be removed.
/teams-modular-packages/hashed-assets/661-edceffffc912794...
●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
●Ensure proper origin isolation with COOP
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
○Mitigate DOM-based XSS with Trusted Types
○Detected JavaScript libraries
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
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○Image elements have `[alt]` attributes

Send Feedback