Lighthouse Mobile

· 0 checks — Mobile 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
/wp-content/uploads/2024/04/94a1-Homepage-Golf-Opener-Ite...	0.0 ms	203.7 KiB
maps.googleapis.com/maps/api/js?client=gme-cityoftoronto&v=3	1800.0 s	100.3 KiB
/wp-content/uploads/2024/11/962d-Homes-in-Fall-Home-Page-...	0.0 ms	78.0 KiB
www.toronto.ca/resources/event_cal_widget/scripts/main1.0.8.js	0.0 ms	73.2 KiB
www.toronto.ca/wp-content/themes/cot/js/footer.js?ver=6.8.3	0.0 ms	53.9 KiB
www.toronto.ca/resources/wp-feedback/scripts/main0.1.0.js	0.0 ms	37.1 KiB
www.toronto.ca/wp-content/themes/cot/js/jquery-3.6.0.min.js	0.0 ms	30.3 KiB
www.toronto.ca/wp-content/uploads/2025/04/96c2-CED-homepage-2025-C.jpg	0.0 ms	24.4 KiB
/wp-content/themes/cot/assets/fontawesome/css/all.min.css...	0.0 ms	22.0 KiB
www.toronto.ca/wp-content/themes/cot/fonts/roboto-medium-webfont.woff2	0.0 ms	20.1 KiB
www.toronto.ca/wp-content/themes/cot/fonts/roboto-bold-webfont.woff2	0.0 ms	20.0 KiB
www.toronto.ca/wp-content/themes/cot/fonts/roboto-regular-webfont.woff2	0.0 ms	19.6 KiB
www.toronto.ca/wp-content/themes/cot/css/bootstrap.3.4.1.min.css?ver=1776362564	0.0 ms	18.2 KiB
www.toronto.ca/wp-content/themes/cot/css/cot.css?ver=1776362564	0.0 ms	16.9 KiB
www.toronto.ca/wp-includes/css/dist/block-library/style.min.css?ver=6.8.3	0.0 ms	14.5 KiB
www.toronto.ca/wp-content/themes/cot/js/bootstrap.3.4.1.min.js	0.0 ms	10.8 KiB
www.toronto.ca/wp-content/themes/cot/js/scripts.js?ver=6.8.3	0.0 ms	10.6 KiB
/wp-content/themes/cot/js/jquery.ui.autocomplete.1.13.2.m...	0.0 ms	10.0 KiB
www.toronto.ca/cot/script.js?ver=1.0.0	300.0 s	9.4 KiB
www.toronto.ca/resources/cdn/cotui/2.4.3/p-973a3c9e.js	0.0 ms	5.7 KiB
www.toronto.ca/wp-content/themes/cot/js/jquery-migrate-3.4.0.min.js	0.0 ms	5.1 KiB
www.toronto.ca/scripts/newtorontolinktrack.js	600.0 s	4.9 KiB
/wp-content/plugins/cot-custom/mediaplayer/dist/ableplaye...	0.0 ms	4.4 KiB
www.toronto.ca/wp-content/themes/cot/js/homepage.js?ver=1.0	0.0 ms	3.9 KiB
www.toronto.ca/resources/311_widgets/scripts/311_widgets.js?ver=1.0	0.0 ms	2.9 KiB
www.toronto.ca/cot/style.css	300.0 s	2.4 KiB
www.toronto.ca/resources/wp-feedback/styles/main0.1.0.css	0.0 ms	2.2 KiB
www.toronto.ca/wp-content/themes/cot/img/icon-arrow-down-white.png	0.0 ms	2.2 KiB
www.toronto.ca/resources/event_cal_widget/styles/main1.0.8.css	0.0 ms	2.2 KiB
www.toronto.ca/resources/cdn/cotui/2.4.3/cotui.esm.js	0.0 ms	2.1 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-iwant-pay.svg	0.0 ms	2.0 KiB
www.toronto.ca/cot/jquery-additional-custom-js.js	300.0 s	1.9 KiB
www.toronto.ca/wp-content/themes/cot/js/search.js?ver=20170712	0.0 ms	1.5 KiB
www.toronto.ca/resources/cdn/cotui/2.4.3/cotui.css?ver=6.8.3	0.0 ms	1.4 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-iwant-apply.svg	0.0 ms	1.4 KiB
www.toronto.ca/wp-content/themes/cot/js/navigation.js?ver=20151215	0.0 ms	1.4 KiB
www.toronto.ca/resources/311_widgets/styles/311_widgets.css?ver=6.8.3	0.0 ms	1.4 KiB
www.toronto.ca/wp-content/themes/cot/print.css	0.0 ms	1.3 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-iwant-request.svg	0.0 ms	1.3 KiB
www.toronto.ca/wp-content/themes/cot/img/icon-twitter.svg	0.0 ms	1.2 KiB
/wp-content/themes/cot/assets/js-cookie/dist/js.cookie.mi...	0.0 ms	1.2 KiB
www.toronto.ca/wp-content/themes/cot/img/logo-print.svg	0.0 ms	1.2 KiB
www.toronto.ca/wp-content/themes/cot/img/logo.svg	0.0 ms	1.2 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-iwant-report.svg	0.0 ms	1.2 KiB
www.toronto.ca/wp-content/themes/cot/img/ico-iwant-register.svg	0.0 ms	1.1 KiB
www.toronto.ca/wp-content/themes/cot/js/skip-link-focus-fix.js?ver=20151215	0.0 ms	1.1 KiB
www.toronto.ca/wp-content/themes/cot/img/icon-youtube.svg	0.0 ms	1.1 KiB
www.toronto.ca/wp-content/themes/cot/img/icon-blank.svg	0.0 ms	1.1 KiB
www.toronto.ca/wp-content/themes/cot/img/icon-instagram.svg	0.0 ms	1005 B
www.toronto.ca/resources/311_widgets/img/311.svg	0.0 ms	993 B
www.toronto.ca/wp-content/themes/cot/img/icon-linkedin.svg	0.0 ms	888 B
www.toronto.ca/scripts/webtrends-infinity.load.js?ver=6.8.3	600.0 s	965 B
www.toronto.ca/wp-content/themes/cot/img/icon-facebook.svg	0.0 ms	824 B
www.toronto.ca/wp-content/themes/cot/img/clip-white.svg	0.0 ms	758 B
www.toronto.ca/wp-content/themes/cot/img/icon-search.svg	0.0 ms	732 B
www.toronto.ca/wp-content/themes/cot/img/back-to-top-arrow.png	0.0 ms	702 B
www.toronto.ca/resources/wp-feedback/img/icon-plus.svg	0.0 ms	681 B
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:33.02 source:map[column:24 line:1383 type:source-location url:https://www.toronto.ca/wp-content/themes/cot/js/footer.js?ver=6.8.3 urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:33.02 source:map[column:81524 line:1 type:source-location url:https://www.toronto.ca/wp-content/themes/cot/js/jquery-3.6.0.min.js urlProvider:network]]]

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
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 KiB	189.1 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.jpg	156.8 KiB	145.0 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 KiB	103.8 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 KiB	63.5 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.jpg	23.9 KiB	9.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: A resident handing a stereo to a City staff member for reuse or recycling at a …

path: 1,HTML,1,BODY,6,SECTION,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,A,0,IMG

selector: div.row > div.col-sm-3 > a.thumbnail > img

snippet: <img src="https://www.toronto.ca/wp-content/uploads/2025/04/96c2-CED-homepage-2025-C…" alt="A resident handing a stereo to a City staff member for reuse or recycling …">

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
www.toronto.ca/resources/event_cal_widget/styles/main1.0.8.css	2.2 KiB	166 ms
www.toronto.ca/resources/311_widgets/styles/311_widgets.css?ver=6.8.3	1.4 KiB	482 ms
www.toronto.ca/resources/wp-feedback/styles/main0.1.0.css	2.2 KiB	166 ms
/wp-content/themes/cot/assets/js-cookie/dist/js.cookie.mi...	1.2 KiB	166 ms
www.toronto.ca/resources/cdn/cotui/2.4.3/cotui.css?ver=6.8.3	1.4 KiB	166 ms
/wp-content/plugins/cot-custom/mediaplayer/dist/ableplaye...	4.4 KiB	640 ms
www.toronto.ca/cot/style.css	2.4 KiB	166 ms
/wp-content/themes/cot/assets/fontawesome/css/all.min.css...	22.0 KiB	1.3 s
www.toronto.ca/wp-content/themes/cot/css/cot.css?ver=1776362564	16.9 KiB	640 ms
www.toronto.ca/wp-content/themes/cot/css/bootstrap.3.4.1.min.css?ver=1776362564	18.2 KiB	1.1 s
www.toronto.ca/wp-includes/css/dist/block-library/style.min.css?ver=6.8.3	14.5 KiB	955 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.

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
www.toronto.ca/wp-content/themes/cot/fonts/roboto-medium-webfont.woff2	10 ms
www.toronto.ca/wp-content/themes/cot/fonts/roboto-regular-webfont.woff2	10 ms
www.toronto.ca/wp-content/themes/cot/fonts/roboto-bold-webfont.woff2	5.0 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	5.0 ms

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: 300 ms 66.5 KiB

URL	Transfer Size	Est Savings
/wp-content/themes/cot/assets/fontawesome/css/all.min.css...	21.6 KiB	21.5 KiB
www.toronto.ca/wp-content/themes/cot/css/bootstrap.3.4.1.min.css?ver=1776362564	17.8 KiB	16.6 KiB
www.toronto.ca/wp-content/themes/cot/css/cot.css?ver=1776362564	16.4 KiB	14.4 KiB
www.toronto.ca/wp-includes/css/dist/block-library/style.min.css?ver=6.8.3	14.0 KiB	14.0 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: 3.6 s 455.0 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	177.1 KiB
/_/translate_http/_/js/k=translate_http.tr.nl.2-2JqXXxIUQ...	118.2 KiB	93.6 KiB
maps.googleapis.com/maps/api/js?client=gme-cityoftoronto&v=3	99.9 KiB	62.9 KiB
maps.googleapis.com/maps-api-v3/api/js/63/14d/util.js	102.7 KiB	38.3 KiB
maps.googleapis.com/maps-api-v3/api/js/63/14d/common.js	41.2 KiB	30.5 KiB
www.toronto.ca/wp-content/themes/cot/js/footer.js?ver=6.8.3	53.4 KiB	29.5 KiB
www.toronto.ca/resources/event_cal_widget/scripts/main1.0.8.js	64.8 KiB	23.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
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	1.4 s	1.2 s	142 ms
www.toronto.ca/	1.2 s	9.3 ms	5.5 ms
Unattributable	824 ms	17 ms	0.0 ms
www.toronto.ca/wp-content/themes/cot/js/jquery-3.6.0.min.js	810 ms	587 ms	17 ms
www.toronto.ca/wp-content/themes/cot/js/footer.js?ver=6.8.3	404 ms	212 ms	30 ms
/_/translate_http/_/js/k=translate_http.tr.nl.2-2JqXXxIUQ...	338 ms	259 ms	64 ms
maps.googleapis.com/maps/api/js?client=gme-cityoftoronto&v=3	255 ms	171 ms	60 ms
www.toronto.ca/resources/event_cal_widget/scripts/main1.0.8.js	164 ms	117 ms	47 ms
www.toronto.ca/resources/wp-feedback/scripts/main0.1.0.js	157 ms	134 ms	21 ms
/acs/account/97j62divdr/js/main/odc.js?_ora.context=analy...	125 ms	103 ms	7.2 ms
/infy/acs/account/97j62divdr/js/main/analytics-production...	109 ms	97 ms	7.2 ms
translate.google.com/translate_a/element.js?cb=translate&ver=6.8.3	52 ms	38 ms	13 ms
www.toronto.ca/wp-content/themes/cot/js/scripts.js?ver=6.8.3	51 ms	15 ms	7.0 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	3.2 s
Other	1.6 s
Style & Layout	587 ms
Script Parsing & Compilation	470 ms
Parse HTML & CSS	250 ms
Rendering	249 ms
Garbage Collection	27 ms

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

URL	Transfer Size	Est Savings
www.toronto.ca/wp-content/themes/cot/js/footer.js?ver=6.8.3	53.4 KiB	8.6 KiB
www.toronto.ca/wp-content/themes/cot/js/scripts.js?ver=6.8.3	10.1 KiB	5.1 KiB
www.toronto.ca/cot/script.js?ver=1.0.0	8.9 KiB	3.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.

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

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

●User Timing marks and measures 2 user timings

●Avoid long main-thread tasks 19 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 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 0 ms

○INP breakdown

○Avoid large layout shifts

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
© City of Toronto 1998 - 2026 `div > div.container-fluid > p > a`
Privacy `div > div.container-fluid > p > a`
Accessibility at the City of Toronto `div > div.container-fluid > p > a`

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

●`[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

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

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

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

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

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

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
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	348 x 249	350 x 250	522 x 374

●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

●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

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 #	Content	Error
3	`Disallow: readme.html`	`Pattern should either be empty, start with "/" or "*"`
4	`Disallow: license.txt`	`Pattern 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`