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
assets.adobedtm.com/be5dfd287373/abb618326704/launch-3eac5e076135.min.js	3600.0 s	161.3 KiB
www.canada.ca/etc/designs/canada/wet-boew/css/theme.min.css	0.0 ms	83.9 KiB
www.canada.ca/etc/designs/canada/wet-boew/js/wet-boew.min.js	0.0 ms	78.2 KiB
www.canada.ca/content/dam/canada/splash/sp-bg-1.jpg	0.0 ms	46.5 KiB
www.canada.ca/content/dam/canada/splash/sp-bg-5.jpg	0.0 ms	44.4 KiB
www.canada.ca/content/dam/canada/splash/sp-bg-2.jpg	0.0 ms	38.8 KiB
www.canada.ca/content/dam/canada/splash/sp-bg-4.jpg	0.0 ms	37.8 KiB
www.canada.ca/content/dam/canada/splash/sp-bg-3.jpg	0.0 ms	31.4 KiB
/etc/designs/canada/wet-boew/fonts/glyphicons-halflings-r...	0.0 ms	18.0 KiB
www.canada.ca/etc/designs/canada/wet-boew/js/theme.min.js	0.0 ms	17.0 KiB
www.canada.ca/etc/designs/canada/wet-boew/js/i18n/en.min.js	0.0 ms	7.3 KiB
s.go-mpulse.net/boomerang/KBFUZ-C9D7G-RB8SX-GRGEN-HGMC9	604800.0 s	57.6 KiB
www.canada.ca/etc/designs/canada/wet-boew/assets/sig-blk-en.svg	0.0 ms	3.2 KiB
www.canada.ca/etc/designs/canada/wet-boew/assets/wmms-blk.svg	0.0 ms	2.1 KiB
www.canada.ca/etc/designs/canada/wet-boew/css/messages.min.css	0.0 ms	1.3 KiB
www.canada.ca/etc/designs/canada/wet-boew/js/i18n/en.min.js	0.0 ms	0 B

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-IMG

nodeLabel: Government of Canada

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

selector: div.sp-bx > div.row > div.col-xs-11 > img

snippet: <img src="/etc/designs/canada/wet-boew/assets/sig-blk-en.svg" alt="Government of Canada" property="logo" width="283">

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
assets.adobedtm.com/be5dfd287373/abb618326704/launch-3eac5e076135.min.js	161.3 KiB	653 ms
www.canada.ca/etc/designs/canada/wet-boew/css/theme.min.css	83.9 KiB	207 ms
www.canada.ca/etc/designs/canada/wet-boew/css/messages.min.css	1.3 KiB

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
/etc/designs/canada/wet-boew/fonts/glyphicons-halflings-r...	15 ms
fonts.gstatic.com/s/lato/v22/S6u9w4BMUTPHh6UVSwiPGQ.woff2	10 ms
fonts.gstatic.com/s/notosans/v25/o-0IIpQlx3QUlC5A4PNr5TRA.woff2	10 ms
fonts.gstatic.com/s/lato/v22/S6uyw4BMUTPHjx4wXg.woff2	10 ms

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

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: 40 ms 82.6 KiB

URL	Transfer Size	Est Savings
www.canada.ca/etc/designs/canada/wet-boew/css/theme.min.css	83.6 KiB	82.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 90 ms 142.5 KiB

URL	Transfer Size	Est Savings
www.canada.ca/etc/designs/canada/wet-boew/js/wet-boew.min.js	77.3 KiB	59.4 KiB
assets.adobedtm.com/be5dfd287373/abb618326704/launch-3eac5e076135.min.js	161.0 KiB	45.0 KiB
s.go-mpulse.net/boomerang/KBFUZ-C9D7G-RB8SX-GRGEN-HGMC9	57.4 KiB	38.1 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 reason	Failure type
The page has an unload handler in a sub frame.	Actionable

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
Symbol of the Government of Canada `div.sp-bx-bt > div.row > div.col-xs-5 > img`	www.canada.ca/etc/designs/canada/wet-boew/assets/wmms-blk.svg
Government of Canada `div.sp-bx > div.row > div.col-xs-11 > img`	www.canada.ca/etc/designs/canada/wet-boew/assets/sig-blk-en.svg

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

●Time to Interactive 1.7 s

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 763 KiB

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.5 s

●Avoid long main-thread tasks 1 long task found

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 40 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 10 ms

○INP breakdown

○User Timing marks and measures

○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-hidden="true"]` is not present on the document `<body>`

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

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

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

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

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

○Deprecated ARIA roles were not used

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○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

○`[role]` values are valid

○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

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

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

○Buttons have an accessible name

○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

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

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

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

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 / Warning	Source
Unload event listeners are deprecated and will be removed.	s.go-mpulse.net/boomerang/KBFUZ-C9D7G-RB8SX-GRGEN-HGMC9 line 10, col 10530
chrome.loadTimes() is deprecated, instead use standardized API: nextHopProtocol in Navigation Timing 2.	s.go-mpulse.net/boomerang/KBFUZ-C9D7G-RB8SX-GRGEN-HGMC9 line 14, col 22215
chrome.loadTimes() is deprecated, instead use standardized API: Navigation Timing 2.	s.go-mpulse.net/boomerang/KBFUZ-C9D7G-RB8SX-GRGEN-HGMC9 line 14, col 22249
chrome.loadTimes() is deprecated, instead use standardized API: Paint Timing.	s.go-mpulse.net/boomerang/KBFUZ-C9D7G-RB8SX-GRGEN-HGMC9 line 14, col 22283

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.

Source	Description
/id?d_visid_ver=5.5.0&d_fieldgroup=A&mcorgid=A90F2A0D5542...	`Failed to load resource: net::ERR_NAME_NOT_RESOLVED`

●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

●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.at-element-marker > meta`

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○Structured data is valid

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`