Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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.

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.

Request	Cache TTL	Transfer Size
ustreamssl-a.akamaihd.net/videos/home.mp4	844.0 s	9.0 MiB
ustvstaticcdn2-a.akamaihd.net/packed/webpack/1f849ec0d7eaa6058096.jpg	900.0 s	193.2 KiB
/common/carbon/plex/sans-jp.css?family=IBM+Plex+Sans+JP:w...	12730.0 s	158.8 KiB
tags.tiqcdn.com/utag/ibm/web/prod/utag.js	300.0 s	89.8 KiB
www.ibm.com/common/dc/0f2de1d5b89a/fd2dbb0e058e/launch-d91723c9d1ad.min.js	3600.0 s	81.5 KiB
/common/carbon/plex/sans-kr.css?family=IBM+Plex+Sans+KR:w...	85471.0 s	86.6 KiB
ustvstaticcdn2-a.akamaihd.net/packed/webpack/react:17750371421.js	1526910.0 s	202.7 KiB
/common/carbon/plex/fonts/IBM-Plex-Sans/fonts/complete/wo...	190417.0 s	65.1 KiB
ustvstaticcdn2-a.akamaihd.net/packed/webpack/home:17750371421.js	1531650.0 s	170.0 KiB
/packed/webpack/dashboard_organization_select:17750371421.js	1531650.0 s	156.3 KiB
/notice?c=teconsent&domain=ibm.com&country=ES&language=fr...	3600.0 s	15.8 KiB
/common/carbon/plex/fonts/IBM-Plex-Sans/fonts/complete/wo...	282437.0 s	61.9 KiB
/common/carbon/plex/fonts/IBM-Plex-Sans/fonts/complete/wo...	343226.0 s	65.8 KiB
/common/carbon/plex/fonts/IBM-Plex-Sans/fonts/split/woff2...	63991.0 s	22.0 KiB
1.www.s81c.com/common/stats/ibm-common.js	588604.0 s	83.0 KiB
/common/carbon/plex/fonts/IBM-Plex-Sans/fonts/split/woff2...	187190.0 s	20.8 KiB
/common/carbon/plex/fonts/IBM-Plex-Sans/fonts/split/woff2...	228688.0 s	22.0 KiB
/common/carbon/plex/fonts/IBM-Plex-Sans/fonts/split/woff2...	376953.0 s	19.9 KiB
/dle/ibm/web/p_1679e42ad32df9d247067251e0f3001a87f13d9bf9...	300.0 s	928 B
/0f2de1d5b89a/fd2dbb0e058e/94861a24ddd7/RCa01675387b8541c...	3600.0 s	599 B
ustvstaticcdn2-a.akamaihd.net/packed/webpack/5786-cb95904dc2ce49f10033.js	418235.0 s	2.9 KiB
/utag/ibm/web/prod/utag.v.js?a=ibm/web/202604201714&cb=17...	300.0 s	432 B
/common/carbon/plex/sans-arabic.css?family=IBM+Plex+Sans+...	26327.0 s	659 B
ustvstaticcdn2-a.akamaihd.net/packed/webpack/keepalive_app:17750371421.js	1531649.0 s	3.4 KiB
/common/carbon/plex/sans-hebrew.css?family=IBM+Plex+Sans+...	85518.0 s	658 B

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.

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-0-VIDEO

nodeLabel: div#root > main#main-content > div.homehero > video.homehero__video

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

selector: div#root > main#main-content > div.homehero > video.homehero__video

snippet: <video autoplay="" class="homehero__video" loop="" playsinline="" preload="auto">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
ustvstaticcdn2-a.akamaihd.net/packed/webpack/carbon:1776802215.css	http/1.1
ustvstaticcdn2-a.akamaihd.net/packed/webpack/home:1776802215.css	http/1.1
ustvstaticcdn2-a.akamaihd.net/packed/webpack/common:1776802215.css	http/1.1
ustvstaticcdn2-a.akamaihd.net/packed/webpack/ie11:1776802215.css	http/1.1
ustvstaticcdn2-a.akamaihd.net/packed/l10n/fr_fr/webpack/react:17750372001.js	http/1.1
/packed/l10n/fr_fr/webpack/dashboard_organization_select:...	http/1.1
ustvstaticcdn2-a.akamaihd.net/packed/l10n/fr_fr/webpack/home:17750372001.js	http/1.1
ustvstaticcdn2-a.akamaihd.net/packed/webpack/react:17750371421.js	http/1.1
ustvstaticcdn2-a.akamaihd.net/packed/webpack/keepalive_app:17750371421.js	http/1.1
/packed/webpack/dashboard_organization_select:17750371421.js	http/1.1
ustvstaticcdn2-a.akamaihd.net/packed/webpack/home:17750371421.js	http/1.1
ustvstaticcdn2-a.akamaihd.net/packed/webpack/5786-cb95904dc2ce49f10033.js	http/1.1
ustvstaticcdn2-a.akamaihd.net/packed/webpack/1f849ec0d7eaa6058096.jpg	http/1.1
ustvstaticcdn2-a.akamaihd.net/favicon.ico	http/1.1

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
ustvstaticcdn2-a.akamaihd.net/packed/webpack/carbon:1776802215.css	900.4 KiB	979 ms
ustvstaticcdn2-a.akamaihd.net/packed/webpack/common:1776802215.css	21.7 KiB	253 ms
ustvstaticcdn2-a.akamaihd.net/packed/webpack/ie11:1776802215.css	673 B	213 ms
ustvstaticcdn2-a.akamaihd.net/packed/webpack/home:1776802215.css	506 B	213 ms

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.

URL	Est Savings
consent.trustarc.com/get?name=IBM_PlexSans-SemiBold.ttf	10 ms
consent.trustarc.com/get?name=IBM_PlexSans-Regular.ttf	10 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 773 ms

URL	Time Spent
ustream.tv/	487 ms
www.ustream.tv/	286 ms
video.ibm.com/	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.

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.

Estimated savings: 680 ms 1.1 MiB

URL	Transfer Size	Est Savings
ustvstaticcdn2-a.akamaihd.net/packed/webpack/carbon:1776802215.css	900.0 KiB	848.5 KiB
/common/carbon/plex/sans-jp.css?family=IBM+Plex+Sans+JP:w...	158.5 KiB	158.5 KiB
/common/carbon/plex/sans-kr.css?family=IBM+Plex+Sans+KR:w...	86.3 KiB	86.3 KiB
ustvstaticcdn2-a.akamaihd.net/packed/webpack/common:1776802215.css	21.3 KiB	21.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 320 ms 456.4 KiB

URL	Transfer Size	Est Savings
ustvstaticcdn2-a.akamaihd.net/packed/webpack/react:17750371421.js	202.2 KiB	126.4 KiB
/packed/webpack/dashboard_organization_select:17750371421.js	155.9 KiB	112.4 KiB
ustvstaticcdn2-a.akamaihd.net/packed/webpack/home:17750371421.js	169.5 KiB	81.6 KiB
tags.tiqcdn.com/utag/ibm/web/prod/utag.js	89.2 KiB	47.4 KiB
1.www.s81c.com/common/stats/ibm-common.js	82.7 KiB	34.4 KiB
www.ibm.com/common/dc/0f2de1d5b89a/fd2dbb0e058e/launch-d91723c9d1ad.min.js	81.1 KiB	31.3 KiB
consent.trustarc.com/asset/notice.js/v/v1.7-1729	36.0 KiB	22.9 KiB

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

URL	Transfer Size	Est Savings
/common/carbon/plex/sans-jp.css?family=IBM+Plex+Sans+JP:w...	158.8 KiB	11.6 KiB
/common/carbon/plex/sans-kr.css?family=IBM+Plex+Sans+KR:w...	86.6 KiB	4.7 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.

URL	Transfer Size
ustreamssl-a.akamaihd.net/videos/home.mp4	9.0 MiB
ustvstaticcdn2-a.akamaihd.net/packed/webpack/carbon:1776802215.css	900.4 KiB
ustvstaticcdn2-a.akamaihd.net/packed/webpack/react:17750371421.js	202.7 KiB
ustvstaticcdn2-a.akamaihd.net/packed/webpack/1f849ec0d7eaa6058096.jpg	193.2 KiB
ustvstaticcdn1-a.akamaihd.net/v6/images/home/hero.jpg	186.2 KiB
ustvstaticcdn2-a.akamaihd.net/packed/webpack/home:17750371421.js	170.0 KiB
/common/carbon/plex/sans-jp.css?family=IBM+Plex+Sans+JP:w...	158.8 KiB
/packed/webpack/dashboard_organization_select:17750371421.js	156.3 KiB
tags.tiqcdn.com/utag/ibm/web/prod/utag.js	89.8 KiB
/common/carbon/plex/sans-kr.css?family=IBM+Plex+Sans+KR:w...	86.6 KiB

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Optimize viewport for mobile

●Max Potential First Input Delay 40 ms

●Minify JavaScript

●User Timing marks and measures 18 user timings

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.9 s

●Avoid non-composited animations 8 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 160 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid long main-thread tasks

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.

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Mondial `div.homecontent__row > div.homecontent__rightrow > div.homecontent__row > h3.homecontent__title`
Dimensionnez vos vidéos d'après quasiment n’importe quel public, à l’échelle mo… `div.homecontent__row > div.homecontent__rightrow > div.homecontent__row > p.homecontent__subtitle`
Utile `div.homecontent__row > div.homecontent__rightrow > div.homecontent__row > h3.homecontent__title`
Professional one-to-one support from video experts `div.homecontent__row > div.homecontent__rightrow > div.homecontent__row > p.homecontent__subtitle`

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Log in `nav.cds--header__nav > ul.cds--header__menu-bar > li > a.cds--header__menu-item`

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

●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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

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

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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

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

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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

Crawling and Indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`head > meta`

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

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○Structured data is valid

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`