Skip to content
https://toronto.ca

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.

95

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
/wp-content/uploads/2024/04/94a1-Homepage-Golf-Opener-Ite...0.0 ms203.7 KiB
maps.googleapis.com/maps/api/js?client=gme-cityoftoronto&v=31800.0 s100.3 KiB
/wp-content/uploads/2024/11/962d-Homes-in-Fall-Home-Page-...0.0 ms78.0 KiB
www.toronto.ca/resources/event_cal_widget/scripts/main1.0.8.js0.0 ms73.2 KiB
www.toronto.ca/wp-content/themes/cot/js/footer.js?ver=6.8.30.0 ms53.9 KiB
www.toronto.ca/resources/wp-feedback/scripts/main0.1.0.js0.0 ms37.1 KiB
www.toronto.ca/wp-content/themes/cot/js/jquery-3.6.0.min.js0.0 ms30.3 KiB
www.toronto.ca/wp-content/uploads/2025/04/96c2-CED-homepage-2025-C.jpg0.0 ms24.4 KiB
/wp-content/themes/cot/assets/fontawesome/css/all.min.css...0.0 ms22.0 KiB
www.toronto.ca/wp-content/themes/cot/fonts/roboto-medium-webfont.woff20.0 ms20.1 KiB
www.toronto.ca/wp-content/themes/cot/fonts/roboto-bold-webfont.woff20.0 ms20.0 KiB
www.toronto.ca/wp-content/themes/cot/fonts/roboto-regular-webfont.woff20.0 ms19.6 KiB
www.toronto.ca/wp-content/themes/cot/css/bootstrap.3.4.1.min.css?ver=17763625640.0 ms18.2 KiB
www.toronto.ca/wp-content/themes/cot/css/cot.css?ver=17763625640.0 ms16.9 KiB
www.toronto.ca/wp-includes/css/dist/block-library/style.min.css?ver=6.8.30.0 ms14.5 KiB
www.toronto.ca/wp-content/themes/cot/js/bootstrap.3.4.1.min.js0.0 ms10.8 KiB
www.toronto.ca/wp-content/themes/cot/js/scripts.js?ver=6.8.30.0 ms10.6 KiB
/wp-content/themes/cot/js/jquery.ui.autocomplete.1.13.2.m...0.0 ms10.0 KiB
www.toronto.ca/cot/script.js?ver=1.0.0300.0 s9.4 KiB
www.toronto.ca/resources/cdn/cotui/2.4.3/p-973a3c9e.js0.0 ms5.7 KiB
www.toronto.ca/wp-content/themes/cot/js/jquery-migrate-3.4.0.min.js0.0 ms5.1 KiB
www.toronto.ca/scripts/newtorontolinktrack.js600.0 s4.9 KiB
/wp-content/plugins/cot-custom/mediaplayer/dist/ableplaye...0.0 ms4.4 KiB
www.toronto.ca/wp-content/themes/cot/js/homepage.js?ver=1.00.0 ms3.9 KiB
www.toronto.ca/resources/311_widgets/scripts/311_widgets.js?ver=1.00.0 ms2.9 KiB
www.toronto.ca/cot/style.css300.0 s2.4 KiB
www.toronto.ca/resources/wp-feedback/styles/main0.1.0.css0.0 ms2.2 KiB
www.toronto.ca/resources/event_cal_widget/styles/main1.0.8.css0.0 ms2.2 KiB
www.toronto.ca/resources/cdn/cotui/2.4.3/cotui.esm.js0.0 ms2.1 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-iwant-pay.svg0.0 ms2.0 KiB
www.toronto.ca/cot/jquery-additional-custom-js.js300.0 s1.9 KiB
www.toronto.ca/wp-content/themes/cot/js/search.js?ver=201707120.0 ms1.5 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-my-property.svg0.0 ms1.5 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-trending.svg0.0 ms1.4 KiB
www.toronto.ca/resources/cdn/cotui/2.4.3/cotui.css?ver=6.8.30.0 ms1.4 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-iwant-apply.svg0.0 ms1.4 KiB
www.toronto.ca/wp-content/themes/cot/js/navigation.js?ver=201512150.0 ms1.4 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-healthy-living.svg0.0 ms1.4 KiB
www.toronto.ca/resources/311_widgets/styles/311_widgets.css?ver=6.8.30.0 ms1.4 KiB
www.toronto.ca/wp-content/themes/cot/print.css0.0 ms1.3 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-your-city.svg0.0 ms1.3 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-permits-licences.svg0.0 ms1.3 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-getting-around.svg0.0 ms1.3 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-iwant-request.svg0.0 ms1.3 KiB
www.toronto.ca/wp-content/themes/cot/img/icon-twitter.svg0.0 ms1.2 KiB
/wp-content/themes/cot/assets/js-cookie/dist/js.cookie.mi...0.0 ms1.2 KiB
www.toronto.ca/wp-content/themes/cot/img/logo-print.svg0.0 ms1.2 KiB
www.toronto.ca/wp-content/themes/cot/img/logo.svg0.0 ms1.2 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-iwant-report.svg0.0 ms1.2 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-iwant-register.svg0.0 ms1.1 KiB
www.toronto.ca/wp-content/themes/cot/js/skip-link-focus-fix.js?ver=201512150.0 ms1.1 KiB
www.toronto.ca/wp-content/themes/cot/img/icon-youtube.svg0.0 ms1.1 KiB
www.toronto.ca/wp-content/themes/cot/img/icon-blank.svg0.0 ms1.1 KiB
www.toronto.ca/wp-content/themes/cot/img/icon-instagram.svg0.0 ms1005 B
www.toronto.ca/resources/311_widgets/img/311.svg0.0 ms992 B
www.toronto.ca/wp-content/themes/cot/img/icon-linkedin.svg0.0 ms887 B
www.toronto.ca/scripts/webtrends-infinity.load.js?ver=6.8.3600.0 s966 B
www.toronto.ca/wp-content/themes/cot/img/icon-facebook.svg0.0 ms825 B
www.toronto.ca/wp-content/themes/cot/img/clip-white.svg0.0 ms756 B
www.toronto.ca/wp-content/themes/cot/img/icon-search.svg0.0 ms732 B
www.toronto.ca/wp-content/themes/cot/img/back-to-top-arrow.png0.0 ms702 B
www.toronto.ca/wp-content/themes/cot/img/icon-arrow-down.png0.0 ms681 B
www.toronto.ca/resources/wp-feedback/img/icon-plus.svg0.0 ms681 B
www.toronto.ca/wp-content/themes/cot/img/active-tab.svg0.0 ms661 B
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.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.

URLEst Savings
www.toronto.ca/wp-content/themes/cot/fonts/roboto-regular-webfont.woff250 ms
www.toronto.ca/wp-content/themes/cot/fonts/roboto-medium-webfont.woff240 ms
www.toronto.ca/wp-content/themes/cot/fonts/roboto-bold-webfont.woff210 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff25.0 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.

URLResource SizeEst Savings
Three people holding golf clubs and standing on a grassy golf range in the addr… div.row > div.col-sm-3 > a.thumbnail > img
/wp-content/uploads/2024/04/94a1-Homepage-Golf-Opener-Ite...203.2 KiB192.9 KiB
A carbon monoxide alarm on the wall. div.row > div.col-sm-3 > a.thumbnail > img
/wp-content/uploads/2026/01/94b7-carbon-monoxide-alarm-ho...117.9 KiB107.6 KiB
Homes on a street in autumn with bare trees and fallen leaves. div.row > div.col-sm-3 > a.thumbnail > img
/wp-content/uploads/2024/11/962d-Homes-in-Fall-Home-Page-...77.6 KiB67.3 KiB
Toronto skyline from a ferry view across Lake Ontario, showing the downtown wat… section#home-carousel > div.carousel-inner > div.item > img
www.toronto.ca/wp-content/uploads/2026/04/94e4-homeskyline-1500x700.jpg156.8 KiB29.8 KiB
A resident handing a stereo to a City staff member for reuse or recycling at a … div.row > div.col-sm-3 > a.thumbnail > img
www.toronto.ca/wp-content/uploads/2025/04/96c2-CED-homepage-2025-C.jpg23.9 KiB13.6 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-3-IMG
nodeLabel: Toronto skyline from a ferry view across Lake Ontario, showing the downtown wat…
path: 1,HTML,1,BODY,5,SECTION,1,DIV,0,DIV,0,IMG
selector: section#home-carousel > div.carousel-inner > div.item > img
snippet: <img src="https://www.toronto.ca/wp-content/uploads/2026/04/94e4-homeskyline-1500x70…" alt="Toronto skyline from a ferry view across Lake Ontario, showing the downtow…" height="700" width="1500">

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
value: No additional origins are good candidates for preconnecting

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.

URLTransfer SizeDuration
/wp-content/themes/cot/assets/js-cookie/dist/js.cookie.mi...1.2 KiB64 ms
www.toronto.ca/wp-content/themes/cot/css/cot.css?ver=177636256416.9 KiB112 ms
www.toronto.ca/resources/wp-feedback/styles/main0.1.0.css2.2 KiB64 ms
www.toronto.ca/resources/event_cal_widget/styles/main1.0.8.css2.2 KiB64 ms
www.toronto.ca/resources/311_widgets/styles/311_widgets.css?ver=6.8.31.4 KiB160 ms
www.toronto.ca/resources/cdn/cotui/2.4.3/cotui.css?ver=6.8.31.4 KiB64 ms
www.toronto.ca/wp-content/themes/cot/css/bootstrap.3.4.1.min.css?ver=177636256418.2 KiB208 ms
www.toronto.ca/cot/style.css2.4 KiB64 ms
www.toronto.ca/wp-includes/css/dist/block-library/style.min.css?ver=6.8.314.5 KiB208 ms
/wp-content/themes/cot/assets/fontawesome/css/all.min.css...22.0 KiB255 ms
/wp-content/plugins/cot-custom/mediaplayer/dist/ableplaye...4.4 KiB160 ms

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.

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 65.4 KiB
URLTransfer SizeEst Savings
/wp-content/themes/cot/assets/fontawesome/css/all.min.css...21.6 KiB21.5 KiB
www.toronto.ca/wp-content/themes/cot/css/bootstrap.3.4.1.min.css?ver=177636256417.8 KiB16.5 KiB
www.toronto.ca/wp-includes/css/dist/block-library/style.min.css?ver=6.8.314.0 KiB14.0 KiB
www.toronto.ca/wp-content/themes/cot/css/cot.css?ver=177636256416.4 KiB13.5 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: 50 ms 388.4 KiB
URLTransfer SizeEst Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js361.8 KiB177.1 KiB
/_/translate_http/_/js/k=translate_http.tr.nl.2-2JqXXxIUQ...118.2 KiB93.6 KiB
maps.googleapis.com/maps/api/js?client=gme-cityoftoronto&v=399.9 KiB64.4 KiB
www.toronto.ca/wp-content/themes/cot/js/footer.js?ver=6.8.353.4 KiB30.2 KiB
www.toronto.ca/resources/event_cal_widget/scripts/main1.0.8.js64.8 KiB23.1 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 20 ms 17.1 KiB
URLTransfer SizeEst Savings
www.toronto.ca/wp-content/themes/cot/js/footer.js?ver=6.8.353.4 KiB8.6 KiB
www.toronto.ca/wp-content/themes/cot/js/scripts.js?ver=6.8.310.1 KiB5.1 KiB
www.toronto.ca/cot/script.js?ver=1.0.08.9 KiB3.5 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
A resident handing a stereo to a City staff member for reuse or recycling at a … div.row > div.col-sm-3 > a.thumbnail > img
www.toronto.ca/wp-content/uploads/2025/04/96c2-CED-homepage-2025-C.jpg
Homes on a street in autumn with bare trees and fallen leaves. div.row > div.col-sm-3 > a.thumbnail > img
/wp-content/uploads/2024/11/962d-Homes-in-Fall-Home-Page-...
Three people holding golf clubs and standing on a grassy golf range in the addr… div.row > div.col-sm-3 > a.thumbnail > img
/wp-content/uploads/2024/04/94a1-Homepage-Golf-Opener-Ite...
A carbon monoxide alarm on the wall. div.row > div.col-sm-3 > a.thumbnail > img
/wp-content/uploads/2026/01/94b7-carbon-monoxide-alarm-ho...
Twitter nav#social-nav > div#f-icons-1 > a > img
www.toronto.ca/wp-content/themes/cot/img/icon-twitter.svg
Facebook nav#social-nav > div#f-icons-1 > a > img
www.toronto.ca/wp-content/themes/cot/img/icon-facebook.svg
Instagram nav#social-nav > div#f-icons-1 > a > img
www.toronto.ca/wp-content/themes/cot/img/icon-instagram.svg
Youtube nav#social-nav > div#f-icons-2 > a > img
www.toronto.ca/wp-content/themes/cot/img/icon-youtube.svg
LinkedIn nav#social-nav > div#f-icons-2 > a > img
www.toronto.ca/wp-content/themes/cot/img/icon-linkedin.svg
nav#social-nav > div#f-icons-2 > a > img nav#social-nav > div#f-icons-2 > a > img
www.toronto.ca/wp-content/themes/cot/img/icon-blank.svg
Search form#siteSearch > div > button#query-search > img
www.toronto.ca/wp-content/themes/cot/img/icon-search.svg

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

●Max Potential First Input Delay 90 ms
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Avoids enormous network payloads Total size was 2,254 KiB
●User Timing marks and measures 2 user timings
●JavaScript execution time 0.8 s
●Minimizes main-thread work 1.9 s
●Avoid long main-thread tasks 4 long tasks found
●Avoid non-composited animations 2 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 30 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
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
99

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.hydrated html.hydrated

These items highlight common accessibility best practices.

○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
●Form elements have associated labels
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
○`[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 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
○`<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
○Links are distinguishable without relying on color.
○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
○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.
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
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.

Crawling and Indexing

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.

Line #ContentError
3Disallow: readme.htmlPattern should either be empty, start with "/" or "*"
4Disallow: license.txtPattern should either be empty, start with "/" or "*"

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

Send Feedback