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

79

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
otpp.com/etc.clientlibs/otpp/clientlibs/clientlib-site.css?v=2026-05-140.0 ms121.7 KiB
assets.adobedtm.com/927e36c8b22c/aa2c0d1a831e/launch-6fa03c805008.min.js3600.0 s112.1 KiB
/is/image/otpp/GettyImages-2217211138:FullBleed?wid=1232&...35950.0 s140.7 KiB
/is/image/otpp/GettyImages-1426180813-v3:FullBleed?wid=12...35950.0 s140.0 KiB
/is/image/otpp/header-image-downtown-toronto:Freeform_v2?...27131.0 s119.4 KiB
/is/image/otpp/2025+AR+Web+Header+Image+for+Landing+Page+...27131.0 s95.0 KiB
/is/image/otpp/PC_L1_OurTeam_Main01_v2:FullBleed?wid=1232...35950.0 s69.2 KiB
/etc.clientlibs/otpp/clientlibs/clientlib-site/resources/...86400.0 s92.1 KiB
/etc.clientlibs/otpp/clientlibs/clientlib-site/resources/...86400.0 s91.8 KiB
/etc.clientlibs/otpp/clientlibs/clientlib-site/resources/...86400.0 s91.2 KiB
/etc.clientlibs/otpp/clientlibs/clientlib-site/resources/...86400.0 s91.2 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
s7d1.scene7.com/is/image/otpp/ISTS-solar_field:CBio?wid=315&hei=211&fmt=webp27131.0 s23.9 KiB
/notice?domain=otpp.com&js=nj&c=teconsent&noticeType=bb&t...3600.0 s12.9 KiB
snap.licdn.com/li.lms-analytics/insight.old.min.js86400.0 s18.7 KiB
s7d1.scene7.com/is/image/otpp/dale-burgess-1:CBio?wid=315&hei=211&fmt=webp14080.0 s6.0 KiB
/WRSiteInterceptEngine/?Q_ZID=ZN_5BWA9l5GPGX6V2l3600.0 s4.6 KiB
/dxjsmodule/12.983a0ab7709ff967fde9.chunk.js?Q_CLIENTVERS...604800.0 s35.1 KiB
/dxjsmodule/37.71bfffaee7e2796d824d.chunk.js?Q_CLIENTVERS...604800.0 s18.6 KiB
otpp.com/.rum/@adobe/helix-rum-js@%5E2/dist/micro.js3600.0 s1.3 KiB
/927e36c8b22c/aa2c0d1a831e/d9a8774ae949/RC87dcb137726a484...3600.0 s769 B
/etc.clientlibs/otpp/clientlibs/clientlib-site/resources/...86400.0 s1.3 KiB
/927e36c8b22c/aa2c0d1a831e/d9a8774ae949/RC612e3213521149b...3600.0 s623 B
/etc.clientlibs/otpp/clientlibs/clientlib-site/resources/...86400.0 s1.0 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s997 B
/etc.clientlibs/otpp/clientlibs/clientlib-site/resources/...86400.0 s949 B
/collect?v=2&fmt=js&pid=2981537&time=1779202007544&li_ads...0.0 ms273 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.

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:30.797 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
div.mainInfoPanel > div.videoImagePanel > picture > img.mw-100 div.mainInfoPanel > div.videoImagePanel > picture > img.mw-100
/is/image/otpp/header-image-downtown-toronto:Freeform_v2?...119.0 KiB81.7 KiB
City div.fullbleedimagecallout__wrapper > div.fullbleedimagecallout__media > picture > img.mw-100
/is/image/otpp/GettyImages-2217211138:FullBleed?wid=1232&...140.3 KiB64.2 KiB
div.fullbleedimagecallout__wrapper > div.fullbleedimagecallout__media > picture > img.mw-100 div.fullbleedimagecallout__wrapper > div.fullbleedimagecallout__media > picture > img.mw-100
/is/image/otpp/GettyImages-1426180813-v3:FullBleed?wid=12...139.6 KiB63.4 KiB
solar fields li.col-12 > a#_content_otpp_en_CA_about_us_news_and_insights_global_perspectives_a_pragmatic_real_world_approach_to_advancing_climate_action > picture > img.mw-100
s7d1.scene7.com/is/image/otpp/ISTS-solar_field:CBio?wid=315&hei=211&fmt=webp23.6 KiB12.8 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-4-IMG
nodeLabel: div#carousel-main > div.op-carousel-banner__bgimage > picture > img.mw-100
path: 1,HTML,1,BODY,2,MAIN,1,DIV,0,DIV,0,PICTURE,5,IMG
selector: div#carousel-main > div.op-carousel-banner__bgimage > picture > img.mw-100
snippet: <img src="https://s7d1.scene7.com/is/image/otpp/2025+AR+Web+Header+Image+for+Landing…" height="528" width="1900" role="presentation" class="mw-100">

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.

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.

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: 269 ms
URLTime Spent
otpp.com/269 ms
otpp.com/en-ca/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: 60 ms 114.8 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.

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

●Max Potential First Input Delay 100 ms
●Layout shift culprits
●Optimize DOM size
●LCP breakdown
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●JavaScript execution time 0.9 s
●Minimizes main-thread work 1.8 s
●Avoid long main-thread tasks 6 long tasks found
●Avoid non-composited animations 1 animated element found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 110 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 30 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○User Timing marks and measures
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
●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
●`[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
●`[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
●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
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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 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.
○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.
○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
AttributionReporting

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
Failed to load resource: net::ERR_NAME_NOT_RESOLVED

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

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

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

Send Feedback