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
uwaterloo.ca/fonts/Bureau_Grot-Condensed_Book.woff2	25 ms
uwaterloo.ca/fonts/lineto-typ1451-regular.woff2	20 ms
uwaterloo.ca/fonts/Bureau_Grot-Book.woff2	15 ms
uwaterloo.ca/fonts/Bureau_Grot-Condensed_Bold.woff2	15 ms
uwaterloo.ca/fonts/Bureau_Grot-Light.woff2	10 ms
uwaterloo.ca/fonts/lineto-typ1451-medium.woff2	10 ms

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:7.301 source:map[column:8495 line:5 type:source-location url:https://uwaterloo.ca/ 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:158.892 source:map[type:text value:[unattributed]]] map[reflowTime:3.315 source:map[column:52061 line:1 type:source-location url:https://uwaterloo.ca/sites/default/files/js/js_K0AVs7DJKR_a7_Vk27HZOpkH8tP2fsTngk57D3Bl9BY.js urlProvider:network]] map[reflowTime:1.005 source:map[column:52780 line:1 type:source-location url:https://uwaterloo.ca/sites/default/files/js/js_K0AVs7DJKR_a7_Vk27HZOpkH8tP2fsTngk57D3Bl9BY.js urlProvider:network]] map[reflowTime:0.216 source:map[column:52838 line:1 type:source-location url:https://uwaterloo.ca/sites/default/files/js/js_K0AVs7DJKR_a7_Vk27HZOpkH8tP2fsTngk57D3Bl9BY.js urlProvider:network]] map[reflowTime:0.226 source:map[column:52902 line:1 type:source-location url:https://uwaterloo.ca/sites/default/files/js/js_K0AVs7DJKR_a7_Vk27HZOpkH8tP2fsTngk57D3Bl9BY.js urlProvider:network]] map[reflowTime:0.538 source:map[column:56721 line:1 type:source-location url:https://uwaterloo.ca/sites/default/files/js/js_K0AVs7DJKR_a7_Vk27HZOpkH8tP2fsTngk57D3Bl9BY.js urlProvider:network]] map[reflowTime:0.726 source:map[column:52083 line:1 type:source-location url:https://uwaterloo.ca/sites/default/files/js/js_K0AVs7DJKR_a7_Vk27HZOpkH8tP2fsTngk57D3Bl9BY.js urlProvider:network]] map[reflowTime:1.275 source:map[column:53815 line:1 type:source-location url:https://uwaterloo.ca/sites/default/files/js/js_K0AVs7DJKR_a7_Vk27HZOpkH8tP2fsTngk57D3Bl9BY.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
Dr. Sarah Burch walking across Waterloo campus `div.uw-waterloo-news > div.uw-waterloo-news__featured > picture.uw-picture > img.uw-picture__fallback`	/sites/default/files/styles/uw_is_media_x_large/public/up...	116.8 KiB	92.1 KiB
Aerial view of campus with yellow checkmark `a > div.card__banner--media > picture.uw-picture > img.uw-picture__fallback`	/sites/default/files/styles/uw_is_media_x_large/public/up...	107.4 KiB	62.5 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-2-IMG

nodeLabel: Professor teaching a student with VO2 max machine

path: 1,HTML,1,BODY,5,DIV,0,DIV,2,MAIN,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,ARTICLE,0,DIV,0,DIV,0,A,1,DIV,0,PICTURE,8,IMG

selector: a > div.card__banner--media > picture.uw-picture > img.uw-picture__fallback

snippet: <img class="uw-picture__fallback" src="https://uwaterloo.ca/sites/default/files/styles/uw_is_media_x_large/public…" alt="Professor teaching a student with VO2 max machine">

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

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.

URL	Transfer Size	Duration
/sites/default/files/css/css_mvPXsrvEKREtRqwt2W6WaQZQ8ZCA...	131.0 KiB	244 ms
/sites/default/files/css/css_yYIob_JSc1msF-q-DpGs3SxT09DU...	4.7 KiB

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
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
/signals/config/1633448083948715?v=2.9.303&r=stable&domai...	1200.0 s	44.5 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.8 KiB
tags.srv.stackadapt.com/events.js	5.0 s	7.7 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
origin.acuityplatform.com/event/v2/pixel.js	0.0 ms	2.7 KiB
wat.test.technolutions.net/ping	1794.0 s	966 B
/collect?v=2&fmt=js&pid=6710970&time=1776802408163&li_ads...	0.0 ms	272 B
/tr/?id=1633448083948715&ev=PageView&dl=https%3A%2F%2Fuwa...	0.0 ms	16 B

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

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

URL	Transfer Size	Est Savings
/sites/default/files/js/js_K0AVs7DJKR_a7_Vk27HZOpkH8tP2fs...	71.9 KiB	10.2 KiB

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: 80 ms 118.7 KiB

URL	Transfer Size	Est Savings
/sites/default/files/css/css_mvPXsrvEKREtRqwt2W6WaQZQ8ZCA...	129.0 KiB	118.7 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: 40 ms 487.0 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/destination?id=AW-869143110&cx=c&gtm=4e64h1	170.1 KiB	67.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-M9XLVF	175.3 KiB	67.5 KiB
www.googletagmanager.com/gtag/js?id=G-L2Z2MKPQ2G	155.4 KiB	64.6 KiB
www.googletagmanager.com/gtag/destination?id=AW-848079280&cx=c&gtm=4e64h1	145.6 KiB	61.7 KiB
www.googletagmanager.com/gtag/js?id=G-W3BFRPSG9B&cx=c&gtm=4e64h1	171.9 KiB	60.8 KiB
www.googletagmanager.com/gtag/destination?id=AW-868082214&cx=c&gtm=4e64h1	134.1 KiB	58.7 KiB
/sites/default/files/js/js_K0AVs7DJKR_a7_Vk27HZOpkH8tP2fs...	71.9 KiB	41.2 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	34.6 KiB
cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.7/config/TeX-AMS_HTML.js?V=2.7.7	53.1 KiB	29.9 KiB

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

●Max Potential First Input Delay 110 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Avoids enormous network payloads Total size was 1,997 KiB

●User Timing marks and measures 29 user timings

●JavaScript execution time 0.8 s

●Minimizes main-thread work 1.6 s

●Avoid long main-thread tasks 7 long tasks found

●Avoid non-composited animations 5 animated elements found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 90 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 15 layout shifts 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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
We use cookies on this site to enhance your user experience Select 'Accept all… `body.org-default > div#sliding-popup > div.eu-cookie-compliance-banner > div.popup-content`

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Discover Waterloo by the numbers → `div.uw-text-align--center > div.uw-copy-text > div.uw-copy-text__wrapper > h3`

These are opportunities to improve keyboard navigation in your application.

○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

●Input buttons have discernible text.

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

●Select elements have associated label elements.

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

○`<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
AttributionReporting	snap.licdn.com/li.lms-analytics/insight.min.js

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

Source	Description
www.googletagmanager.com/gtm.js?id=GTM-M9XLVF line 244, col 482	Loading the script 'https://bat.bing.com/bat.js' violates the following Content Security Policy directive: "default-src 'self' 'unsafe-inline' 'unsafe-eval' data: https://uwaterloo.ca https://.uwaterloo.ca https://maxcdn.bootstrapcdn.com https://.google.com https://.google-analytics.com https://.googleapis.com https://.gstatic.com https://.googletagmanager.com https://.googleusercontent.com https://.googleadservices.com https://.g.doubleclick.net https://6263835.fls.doubleclick.net https://ad.doubleclick.net https://14868352.fls.doubleclick.net https://cdnjs.cloudflare.com https://twitter.com https://.twitter.com https://.twimg.com https://.facebook.com https://.facebook.net https://scontent.xx.fbcdn.net https://.youtube.com https://.youtube-nocookie.com https://s.ytimg.com https://.livestream.com https://.webspellchecker.net https://cdn.mathjax.org https://.addtoany.com https://.vimeo.com https://.vimeocdn.com https://cdn.leafletjs.com https://cdn-geoweb.s3.amazonaws.com https://cdn.maptiks.com https://api.tiles.mapbox.com https://d591zijq8zntj.cloudfront.net https://.libanswers.com https://.libchat.com https://secure.skype.com https://cdn-akamai.mookie1.com https://.tiqcdn.com https://snap.licdn.com https://.ads.linkedin.com https://secure.adnxs.com https://public.tableau.com https://codepen.io https://cpwebassets.codepen.io https://static.codepen.io https://public.codepenassets.com https://app.powerbi.com https://s.yimg.com https://sp.analytics.yahoo.com https://chat.socialintents.com https://hcaptcha.com https://newassets.hcaptcha.com https://code.jquery.com https://experience.arcgis.com https://api.mapbox.com https://www.instagram.com https://vuejs.org https://cdn.jsdelivr.net https://js-agent.newrelic.com https://bam.nr-data.net https://us-central1-pantheon-psapps.cloudfunctions.net https://cdn.ckeditor.com https://netdna.bootstrapcdn.com https://.hotjar.com https://.hotjar.io https://.kuali.co https://drupal-oauth.mailchimp.com https://srv.stackadapt.com https://.srv.stackadapt.com https://qvdt3feo.com https://origin.acuityplatform.com https://e.acuityplatform.com https://*.clarity.ms https://c.bing.com https://www.redditstatic.com https://events.reddit.com https://wat-2.test.technolutions.net https://wat.test.technolutions.net https://fw.cdn.technolutions.net https://mx.technolutions.net https://wat-backup.test.technolutions.net https://slate-technolutions-net.cdn.technolutions.net https://grad-apply-uwaterloo-ca.cdn.technolutions.net". Note that 'script-src-elem' was not explicitly set, so 'default-src' is used as a fallback. The action has been blocked.

www.googletagmanager.com/gtm.js?id=GTM-M9XLVF line 244, col 482

Loading the script 'https://bat.bing.com/bat.js' violates the following Content Security Policy directive: "default-src 'self' 'unsafe-inline' 'unsafe-eval' data: https://uwaterloo.ca https://*.uwaterloo.ca https://maxcdn.bootstrapcdn.com https://*.google.com https://*.google-analytics.com https://*.googleapis.com https://*.gstatic.com https://*.googletagmanager.com https://*.googleusercontent.com https://*.googleadservices.com https://*.g.doubleclick.net https://6263835.fls.doubleclick.net https://ad.doubleclick.net https://14868352.fls.doubleclick.net https://cdnjs.cloudflare.com https://twitter.com https://*.twitter.com https://*.twimg.com https://*.facebook.com https://*.facebook.net https://scontent.xx.fbcdn.net https://*.youtube.com https://*.youtube-nocookie.com https://s.ytimg.com https://*.livestream.com https://*.webspellchecker.net https://cdn.mathjax.org https://*.addtoany.com https://*.vimeo.com https://*.vimeocdn.com https://cdn.leafletjs.com https://cdn-geoweb.s3.amazonaws.com https://cdn.maptiks.com https://api.tiles.mapbox.com https://d591zijq8zntj.cloudfront.net https://*.libanswers.com https://*.libchat.com https://secure.skype.com https://cdn-akamai.mookie1.com https://*.tiqcdn.com https://snap.licdn.com https://*.ads.linkedin.com https://secure.adnxs.com https://public.tableau.com https://codepen.io https://cpwebassets.codepen.io https://static.codepen.io https://public.codepenassets.com https://app.powerbi.com https://s.yimg.com https://sp.analytics.yahoo.com https://chat.socialintents.com https://hcaptcha.com https://newassets.hcaptcha.com https://code.jquery.com https://experience.arcgis.com https://api.mapbox.com https://www.instagram.com https://vuejs.org https://cdn.jsdelivr.net https://js-agent.newrelic.com https://bam.nr-data.net https://us-central1-pantheon-psapps.cloudfunctions.net https://cdn.ckeditor.com https://netdna.bootstrapcdn.com https://*.hotjar.com https://*.hotjar.io https://*.kuali.co https://drupal-oauth.mailchimp.com https://srv.stackadapt.com https://*.srv.stackadapt.com https://qvdt3feo.com https://origin.acuityplatform.com https://e.acuityplatform.com https://*.clarity.ms https://c.bing.com https://www.redditstatic.com https://events.reddit.com https://wat-2.test.technolutions.net https://wat.test.technolutions.net https://fw.cdn.technolutions.net https://mx.technolutions.net https://wat-backup.test.technolutions.net https://slate-technolutions-net.cdn.technolutions.net https://grad-apply-uwaterloo-ca.cdn.technolutions.net". Note that 'script-src-elem' was not explicitly set, so 'default-src' is used as a fallback. The action has been blocked.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●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

●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

100

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.

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

○robots.txt is valid