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.

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
assets.ubuntu.com/v1/f1ea362b-Ubuntu%5Bwdth,wght%5D-latin-v0.896a.woff2	570 ms
assets.ubuntu.com/v1/90b59210-Ubuntu-Italic%5Bwdth,wght%5D-latin-v0.896a.woff2	565 ms

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

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
canonical.com/static/css/styles.css?v=990f606	106.0 KiB	437 ms

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.

	URL	Resource Size	Est Savings
div.row > div.col-6 > div.p-image-container--16-9 > img.p-image-container__image `div.row > div.col-6 > div.p-image-container--16-9 > img.p-image-container__image`	/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_900/ht...	93.3 KiB	60.5 KiB
div.p-homepage-carousel--slides > div#start-ubuntu-tab > div.p-image--container > img.p-image--container__image `div.p-homepage-carousel--slides > div#start-ubuntu-tab > div.p-image--container > img.p-image--container__image`	/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_1681/h...	22.6 KiB	15.9 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 190 ms 82.1 KiB

URL	Transfer Size	Est Savings
canonical.com/static/css/styles.css?v=990f606	103.3 KiB	82.1 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
canonical.com/static/js/dist/homepage_animations.js?v=cbbe774	1.2 s	1.2 s	15 ms
canonical.com/	558 ms	11 ms	1.6 ms
Unattributable	221 ms	31 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-5LTL1CNEJM&cx=c&gtm=4e64k1	153 ms	126 ms	19 ms
assets.ubuntu.com/v1/703e23c9-lazysizes+noscript+native-loading.5.1.2.min.js	109 ms	66 ms	0.5 ms
www.googletagmanager.com/gtag/js?id=G-1NSNT4HZ3S&cx=c&gtm=4e64k1	101 ms	74 ms	16 ms
www.googletagmanager.com/gtag/destination?id=AW-608589488&cx=c&gtm=4e64k1	78 ms	64 ms	13 ms
www.googletagmanager.com/gtm.js?id=GTM-M5BPGQ6	73 ms	57 ms	15 ms

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.

Category	Time Spent
Script Evaluation	1.7 s
Other	538 ms
Style & Layout	196 ms
Script Parsing & Compilation	96 ms
Rendering	86 ms
Parse HTML & CSS	51 ms
Garbage Collection	31 ms

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: 0.0 ms 330.9 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-M5BPGQ6	158.1 KiB	69.9 KiB
www.googletagmanager.com/gtag/js?id=G-1NSNT4HZ3S&cx=c&gtm=4e64k1	161.9 KiB	67.7 KiB
www.googletagmanager.com/gtag/destination?id=AW-608589488&cx=c&gtm=4e64k1	144.6 KiB	66.6 KiB
www.googletagmanager.com/gtag/js?id=G-5LTL1CNEJM&cx=c&gtm=4e64k1	174.6 KiB	63.8 KiB
canonical.com/static/js/dist/homepage_animations.js?v=cbbe774	67.0 KiB	63.0 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.scroll-section__tabs > button.scroll-section__tab > div.scroll-section__tab-icon > img `div.scroll-section__tabs > button.scroll-section__tab > div.scroll-section__tab-icon > img`	assets.ubuntu.com/v1/2370a9a8-cloud.svg
div.scroll-section__tabs > button.scroll-section__tab > div.scroll-section__tab-icon > img `div.scroll-section__tabs > button.scroll-section__tab > div.scroll-section__tab-icon > img`	assets.ubuntu.com/v1/9efb4b31-silicon.svg
div.scroll-section__tabs > button.scroll-section__tab > div.scroll-section__tab-icon > img `div.scroll-section__tabs > button.scroll-section__tab > div.scroll-section__tab-icon > img`	assets.ubuntu.com/v1/d036df5d-hardware.svg
div.row > div.col-3 > button.pause-btn > img `div.row > div.col-3 > button.pause-btn > img`	assets.ubuntu.com/v1/398d9c17-pause.svg

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 15 user timings

●Avoid long main-thread tasks 9 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 180 ms

●Server Backend Latencies 220 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 180 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Start with Ubuntu Take control of your infrastructure Build apps at speed and s… `div.p-homepage-carousel > div.row > div.col-3 > ul.p-homepage-carousel-tabs`

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Products `div.p-navigation__row--25-75 > nav.p-navigation__nav > ul.p-navigation__items > li#products-nav`
Solutions `div.p-navigation__row--25-75 > nav.p-navigation__nav > ul.p-navigation__items > li#solutions-nav`
Partners `div.p-navigation__row--25-75 > nav.p-navigation__nav > ul.p-navigation__items > li#partners-nav`
Careers `div.p-navigation__row--25-75 > nav.p-navigation__nav > ul.p-navigation__items > li#careers-nav`
Company `div.p-navigation__row--25-75 > nav.p-navigation__nav > ul.p-navigation__items > li#company-nav`
Start with Ubuntu `div.col-3 > ul.p-homepage-carousel-tabs > li > a#start-ubuntu`
Take control of your infrastructure `div.col-3 > ul.p-homepage-carousel-tabs > li > a#infrastructure-control`
Build apps at speed and stay secure `div.col-3 > ul.p-homepage-carousel-tabs > li > a#stay-secure`
Get an optimized stack for data and AI `div.col-3 > ul.p-homepage-carousel-tabs > li > a#optimized-ai`
Deploy smart things at the edge `div.col-3 > ul.p-homepage-carousel-tabs > li > a#smart-edge`

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Hardening and certifications `div.u-hide--small > div#centre-animation-wrapper > div.centre-animation__zones > div.centre-animation__zone--1`
Reliable security maintenance `div.u-hide--small > div#centre-animation-wrapper > div.centre-animation__zones > div.centre-animation__zone--2`
Simplified compliance `div.u-hide--small > div#centre-animation-wrapper > div.centre-animation__zones > div.centre-animation__zone--3`
Patching automation tools `div.u-hide--small > div#centre-animation-wrapper > div.centre-animation__zones > div.centre-animation__zone--4`
24/7 Support `div.u-hide--small > div#centre-animation-wrapper > div.centre-animation__zones > div.centre-animation__zone--5`
Long-term API stability `div.u-hide--small > div#centre-animation-wrapper > div.centre-animation__zones > div.centre-animation__zone--6`
Device management `div.u-hide--small > div#centre-animation-wrapper > div.centre-animation__zones > div.centre-animation__zone--7`

These are opportunities to improve the usage of ARIA in your application which 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. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
privacy policy `footer.p-footer > div.row > p.p-text--small > a`

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Products Solutions Partners Careers Company `header#navigation > div.p-navigation__row--25-75 > nav.p-navigation__nav > ul.p-navigation__items`

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Start with Ubuntu `div.row > div.col-3 > ul.p-homepage-carousel-tabs > li`
Take control of your infrastructure `div.row > div.col-3 > ul.p-homepage-carousel-tabs > li`
Build apps at speed and stay secure `div.row > div.col-3 > ul.p-homepage-carousel-tabs > li`
Get an optimized stack for data and AI `div.row > div.col-3 > ul.p-homepage-carousel-tabs > li`
Deploy smart things at the edge `div.row > div.col-3 > ul.p-homepage-carousel-tabs > li`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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

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

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

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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

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

●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

●ARIA IDs are unique

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

○Select elements have associated label elements.

○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

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

○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

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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 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
Previous image `div.row > div.col-medium-3 > div > a.p-homepage-carousel__previous`

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

●Links have descriptive text

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`