Skip to content
https://usask.ca

Lighthouse Mobile

· 0 checks — Mobile 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.

52

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
news.usask.ca/images/2025/campus-winter-08-1.jpg604800.0 s371.1 KiB
news.usask.ca/images/2026/jumbotron-main.jpg604800.0 s246.4 KiB
www.usask.ca/_images/homepage_banner/students-outside-spring1.webp604800.0 s137.3 KiB
www.usask.ca/_images/homepage/discovery.jpeg604800.0 s124.9 KiB
www.usask.ca/_images/homepage_banner/dentistry-lab.jpg604800.0 s122.0 KiB
www.usask.ca/_images/land_acknowledgement.jpg604800.0 s116.1 KiB
news.usask.ca/images/2026/mb1_5649.jpg604800.0 s107.4 KiB
www.usask.ca/_images/homepage_banner/students-studing-louis-loft.webp604800.0 s102.1 KiB
www.usask.ca/_images/program-search.jpg604800.0 s59.3 KiB
www.usask.ca/_images/homepage/syncrotron.jpg604800.0 s38.4 KiB
usaskcdn.ca/limestone2/latest/css/limestone.min.css604800.0 s37.6 KiB
www.usask.ca/_images/homepage/winter.jpg604800.0 s33.7 KiB
usaskcdn.ca/limestone2/latest/img/symbols_sprite_sheet.png604800.0 s31.2 KiB
/embed/176d8305eb20cbb06f8b70b1dbcc820e/17c93f4827302b34d...0.0 ms3.1 KiB
www.usask.ca/_images/homepage/students-outside.jpg604800.0 s28.5 KiB
www.usask.ca/_images/homepage/interntional1.jpg604800.0 s27.1 KiB
www.usask.ca/_images/logos/usask-logo-lg.png604800.0 s26.4 KiB
usaskcdn.ca/limestone2/latest/js/bootstrap.bundle.min.js604800.0 s23.1 KiB
usaskcdn.ca/limestone2/latest/js/limestone.min.js604800.0 s9.0 KiB
usaskcdn.ca/limestone2/stable/img/uofs-logo.webp604800.0 s6.7 KiB
usaskcdn.ca/limestone2/latest/css/homepage_banner.css604800.0 s1.5 KiB

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.

URLEst Savings
usaskcdn.ca/limestone2/latest/fonts/usask-icons/usask-icons.ttf?ym2f97695 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
div.row > div.col-12 > div.card > figure div.row > div.col-12 > div.card > figure
news.usask.ca/images/2025/campus-winter-08-1.jpg370.7 KiB244.2 KiB
div.row > div.col-12 > div.card > figure div.row > div.col-12 > div.card > figure
news.usask.ca/images/2026/jumbotron-main.jpg246.0 KiB119.4 KiB
Located on Treaty 6 Territory and the Homeland of the Métis We pay our respect … body > div.uofs-page > div#content > section#section-7
www.usask.ca/_images/land_acknowledgement.jpg115.7 KiB30.3 KiB
CLS div#section-1-subsection-1 > div.row > div.col-6 > img
www.usask.ca/_images/homepage/syncrotron.jpg38.0 KiB25.8 KiB
University of Saskatchewan header.py-0 > div.d-flex > a.me-auto > img.uofs-header-logo
www.usask.ca/_images/logos/usask-logo-lg.png26.1 KiB23.8 KiB
CLS div#section-1-subsection-1 > div.row > div.col-6 > img
www.usask.ca/_images/homepage/winter.jpg33.3 KiB21.0 KiB
description div#section-1-subsection-1 > div.row > div.col-6 > img.pull-right
www.usask.ca/_images/homepage/students-outside.jpg28.1 KiB15.9 KiB
description div#section-1-subsection-1 > div.row > div.col-6 > img.pull-right
www.usask.ca/_images/homepage/interntional1.jpg26.7 KiB14.4 KiB
thorvaldson building div#section-2-subsection-0 > div.row > div.col-md-4 > img.mb-4
www.usask.ca/_images/program-search.jpg58.9 KiB11.3 KiB
body > section#Sectionheading > div#bg_images > div#uofs-section-bg2 body > section#Sectionheading > div#bg_images > div#uofs-section-bg2
www.usask.ca/_images/homepage_banner/dentistry-lab.jpg121.6 KiB4.4 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:1327.72 label:Time to first byte subpart:timeToFirstByte] map[duration:1153.889 label:Resource load delay subpart:resourceLoadDelay] map[duration:358.329 label:Resource load duration subpart:resourceLoadDuration] map[duration:111.782 label:Element render delay subpart:elementRenderDelay]]
lhId: page-10-DIV
nodeLabel: body > section#Sectionheading > div#bg_images > div#uofs-section-bg1
path: 1,HTML,1,BODY,2,SECTION,1,DIV,0,DIV
selector: body > section#Sectionheading > div#bg_images > div#uofs-section-bg1
snippet: <div class="uofs-section-bg-fade" id="uofs-section-bg1">

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-10-DIV
nodeLabel: body > section#Sectionheading > div#bg_images > div#uofs-section-bg1
path: 1,HTML,1,BODY,2,SECTION,1,DIV,0,DIV
selector: body > section#Sectionheading > div#bg_images > div#uofs-section-bg1
snippet: <div class="uofs-section-bg-fade" id="uofs-section-bg1">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
www.usask.ca/http/1.1
usaskcdn.ca/limestone2/latest/css/limestone.min.csshttp/1.1
www.usask.ca/_images/logos/usask-logo-lg.pnghttp/1.1
usaskcdn.ca/limestone2/latest/css/homepage_banner.csshttp/1.1
www.usask.ca/_images/program-search.jpghttp/1.1
usaskcdn.ca/limestone2/stable/img/uofs-logo.webphttp/1.1
usaskcdn.ca/limestone2/latest/js/bootstrap.bundle.min.jshttp/1.1
usaskcdn.ca/limestone2/latest/js/limestone.min.jshttp/1.1
usaskcdn.ca/limestone2/latest/fonts/usask-icons/usask-icons.ttf?ym2f97http/1.1
www.usask.ca/_images/homepage_banner/students-studing-louis-loft.webphttp/1.1
www.usask.ca/_images/homepage_banner/dentistry-lab.jpghttp/1.1
www.usask.ca/_images/homepage_banner/students-outside-spring1.webphttp/1.1
www.usask.ca/_images/homepage/discovery.jpeghttp/1.1
www.usask.ca/_images/land_acknowledgement.jpghttp/1.1
usaskcdn.ca/limestone2/latest/img/symbols_sprite_sheet.pnghttp/1.1
www.usask.ca/_images/homepage/interntional1.jpghttp/1.1
www.usask.ca/_images/homepage/winter.jpghttp/1.1
www.usask.ca/_images/homepage/students-outside.jpghttp/1.1
www.usask.ca/_images/homepage/syncrotron.jpghttp/1.1
usaskcdn.ca/limestone2/latest/img/uofs-crest.svghttp/1.1
usaskcdn.ca/limestone2/latest/img/favicon.pnghttp/1.1

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

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
usaskcdn.ca/limestone2/latest/css/limestone.min.css37.6 KiB1.6 s

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: 1.3 s
URLTime Spent
usask.ca/1.3 s
www.usask.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

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: 150 ms 53.9 KiB
URLTransfer SizeEst Savings
usaskcdn.ca/limestone2/latest/css/limestone.min.css37.1 KiB33.4 KiB
.flockler-grid-items{background:var(--fl-background,transparent);box-sizing:border-box; … } …20.6 KiB20.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: 910 ms 158.1 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-7P8QY8C9QK&cx=c&gtm=4e64k0172.9 KiB66.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-NPKLVP6134.6 KiB64.0 KiB
plugins.flockler.com/embed/v3/embed-grid.js58.2 KiB28.0 KiB

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.

CategoryTime Spent
Other1.1 s
Script Evaluation837 ms
Style & Layout468 ms
Script Parsing & Compilation199 ms
Rendering195 ms
Parse HTML & CSS62 ms
Garbage Collection22 ms

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
thorvaldson building div#section-2-subsection-0 > div.row > div.col-md-4 > img.mb-4
www.usask.ca/_images/program-search.jpg
University of Saskatchewan header.py-0 > div.d-flex > a.me-auto > img.uofs-header-logo
www.usask.ca/_images/logos/usask-logo-lg.png
University of Saskatchewan footer.pt-5 > p > a > img
usaskcdn.ca/limestone2/stable/img/uofs-logo.webp

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

●Layout shift culprits
●Optimize DOM size
●Forced reflow
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 2,234 KiB
●User Timing marks and measures 7 user timings
●JavaScript execution time 1.0 s
●Avoid long main-thread tasks 7 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 170 ms
●Server Backend Latencies 240 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 260 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
95

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.

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
Living in Saskatchewan, Canada div.col-12 > div#section-1-subsection-0 > div.small > h4
Research that improves lives in our community and beyond. div.row > div.col-12 > div#section-4-subsection-0 > h4.h4
USask leads the way in tackling relevant, global issues such as vaccine develop… section#section-5 > div.container-fluid > div#section-5-subsection-0 > h4.text-muted
We pay our respect to the First Nations and Métis ancestors of this place and r… div.col-12 > div#section-7-subsection-0 > div.small > h4

These are opportunities to improve keyboard navigation in your application.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
USask News div.container-fluid > div#section-3-subsection-0 > h2.h3 > a

These are opportunities to improve the legibility of your content.

○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
●`<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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●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
○`<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
○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.
○`[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.
96

Best Practices

General

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
www.usask.ca/
The source list for the Content Security Policy directive 'media-src' contains an invalid source: '*$'. It will be ignored.
●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 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
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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback