Skip to content
https://uwa.edu.au

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.

75

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.

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.

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-0-IMG
nodeLabel: standout--desktop.jpg
path: 1,HTML,1,BODY,27,DIV,5,DIV,1,MAIN,0,DIV,1,SECTION,0,DIV,0,UL,0,LI,0,IMG
selector: div._inner > ul._viewport > li#hero-carousel-1 > img._large
snippet: <img height="1046" dam-content-type="Image" alt="standout--desktop.jpg" width="2440" thumbnailsrc="https://www.assethub.uwa.edu.au/api/gateway/216946/thumbnail" dam-id="llPxGwG4QgutXcLlMXQiEg" class="_large" src="https://www.assethub.uwa.edu.au/api/public/content/81f1977cf56e4dc8a887071…">

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.

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
/a4d8a0fb3923-sitecorexmc9b86-prod33ed-3cbd/media/images/...14400.0 s362.4 KiB
/a4d8a0fb3923-sitecorexmc9b86-prod33ed-3cbd/media/images/...14400.0 s322.1 KiB
/a4d8a0fb3923-sitecorexmc9b86-prod33ed-3cbd/media/images/...14400.0 s242.8 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
/a4d8a0fb3923-sitecorexmc9b86-prod33ed-3cbd/media/images/...14400.0 s96.7 KiB
/a4d8a0fb3923-sitecorexmc9b86-prod33ed-3cbd/media/images/...14400.0 s70.9 KiB
/signals/config/867027410046883?v=2.9.303&r=stable&domain...1200.0 s44.9 KiB
/web-flow-libs/uwaxn1f61qtsuguu5wqmobzgtgj7ew7f/46/lib.mi...0.0 ms29.0 KiB
www.uwa.edu.au/img/icons/footer_indigenous_light.png14400.0 s16.4 KiB
scripts.clarity.ms/0.8.60-beta/clarity.js86400.0 s25.0 KiB
/visualid/devcore/1/_assets/img/uwacrest-small-white.svg43200.0 s19.0 KiB
pixel.byspotify.com/ping.min.js3600.0 s10.3 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
d1mj578wat5n4o.cloudfront.net/boxever-1.4.9.min.js0.0 ms7.5 KiB
siteimproveanalytics.com/js/siteanalyze_82458.js86400.0 s13.3 KiB
www.uwa.edu.au/img/icons/flag-australia.png14400.0 s6.4 KiB
static.weboffice.uwa.edu.au/visualid/devcore/1/_assets/img/member-go8_white.svg43200.0 s7.7 KiB
/v1/files/pages/styles/content-styles.css?sitecoreContext...0.0 ms2.7 KiB
www.uwa.edu.au/img/icons/social-youtube_white.svg14400.0 s1.5 KiB
www.uwa.edu.au/img/icons/social-linkedin_white.svg14400.0 s1.5 KiB
www.uwa.edu.au/img/icons/social-instagram_white.svg14400.0 s1.4 KiB
www.uwa.edu.au/img/icons/menu-chevron_sky.svg14400.0 s1.4 KiB
www.uwa.edu.au/img/icons/menu-chevron_white.svg14400.0 s1.4 KiB
www.uwa.edu.au/img/icons/social-facebook_white.svg14400.0 s1.3 KiB
www.uwa.edu.au/img/icons/link-arrow_bright.svg14400.0 s1.2 KiB
www.uwa.edu.au/img/icons/search_blue.svg14400.0 s1.2 KiB
www.uwa.edu.au/img/icons/social-x_white.svg14400.0 s1.1 KiB
/collect?v=2&fmt=js&pid=110729&time=1776819981377&url=htt...0.0 ms689 B
www.uwa.edu.au/img/icons/media-pause_white.svg14400.0 s1009 B
www.uwa.edu.au/img/icons/arrow-up.svg14400.0 s937 B
www.uwa.edu.au/img/icons/chevron-right_white.svg14400.0 s868 B
www.uwa.edu.au/img/icons/chevron-right_bright.svg14400.0 s851 B
www.uwa.edu.au/img/icons/chevron-left_bright.svg14400.0 s831 B
www.uwa.edu.au/img/icons/chevron-left_white.svg14400.0 s823 B
/config/au/e26b7ee2-0fc8-4603-a49c-e031d9e8c23d.js?v=3.55...0.0 ms475 B
hello.myfonts.net/count/3ab790604800.0 s372 B
/tr/?id=867027410046883&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms19 B
/p.css?s=1&k=fes2lhi&ht=tk&f=36957.36958.36963.36964.3696...604800.0 s172 B

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
ezone_stairs_02_HR.jpg div._inner > ul._viewport > li#hero-carousel-3 > img._large
/api/public/content/67aa38a8b145497e9c5b4bacf017be10?v=62...405.9 KiB279.5 KiB
girl at UWA div._inner > ul._viewport > li#hero-carousel-2 > img._large
/a4d8a0fb3923-sitecorexmc9b86-prod33ed-3cbd/media/images/...361.9 KiB191.0 KiB
Woman in lab div._inner > ul._viewport > li#hero-carousel-4 > img._large
/a4d8a0fb3923-sitecorexmc9b86-prod33ed-3cbd/media/images/...321.6 KiB150.8 KiB
UWA21_4 [SENG9839].jpg div.column__stack > div.image__liftout > div._image > img
/api/public/content/99411f3b5ddb4386947a53a934027568?v=75...149.5 KiB107.9 KiB
standout--desktop.jpg div._inner > ul._viewport > li#hero-carousel-1 > img._large
/api/public/content/81f1977cf56e4dc8a88707152cd845d3?v=99...221.6 KiB95.2 KiB
UWA21_4 [SENG1475].jpg li > a.card__raised > div._image > img
/api/public/content/aefa75d4728e4f74a25d3484da5cb744?v=cb...85.8 KiB68.3 KiB
UWA21_7 [SENG3474].jpg li > a.card__raised > div._image > img
/api/public/content/e58cb5f756414e6986e16672c119a1a3?v=9d...69.0 KiB57.2 KiB
great gate (1 of 1).jpg li > a.card__raised > div._image > img
/api/public/content/14f59778231747eabdc3af72ebb05c7c?v=f8...68.8 KiB57.1 KiB
UWA-March-412 [Image by Jarrad Seng].jpg li > a.card__raised > div._image > img
/api/public/content/6dff02a3ee214701bcc3fff57d8ffa76?v=48...65.2 KiB47.7 KiB
Pat Dudgeon CARD.jpg li > a.card__raised > div._image > img
/api/public/content/SwD_AtLxQcyd8hwkwCUvWg-WebStandard-4x...58.3 KiB46.6 KiB
NESP-Fish-pops-Card-944x522.jpg li > a.card__raised > div._image > img
/api/public/content/6j6nNAmqSE2B3W3M5HR9HA-WebStandard-4x...54.5 KiB42.8 KiB
UWA21_3 [SENG5591].jpg div.column__stack > div.image__liftout > div._image > img
/api/public/content/0dbf6933282940fa86910d1015bf4b7a?v=32...73.8 KiB38.9 KiB
UWA-November222[ImagebyJarradSeng].jpg li > a.card__raised > div._image > img
/api/public/content/1f5717bf71a14c26911de031749e8daa?v=95...41.8 KiB30.6 KiB
MAT03489.jpg li > a.card__raised > div._image > img
/api/public/content/kfCVhqNnRh2LSCJBnhz9uA-WebStandard-4x...47.8 KiB30.3 KiB
UWA21_5 [SENG2571].jpg li > a.card__raised > div._image > img
/api/public/content/fe78288b0ea4480d90c172449ef211cf?v=1c...39.3 KiB28.8 KiB
UWA21_1 [SENG0540].jpg div.column__stack > div.image__liftout > div._image > img
/api/public/content/dab1c669656145589c515b1baa385e8e?v=3d...52.4 KiB27.6 KiB
The-Kids-UWA-malaria-funding-Card-944x522.jpg li > a.card__raised > div._image > img
/api/public/content/Hev4s4sPSDOvDpGHeNSfjA-WebStandard-4x...32.2 KiB23.6 KiB

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: 525 ms
URLTime Spent
uwa.edu.au/256 ms
www.uwa.edu.au/270 ms
www.uwa.edu.au/home0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 540 ms
URLTime Spent
www.uwa.edu.au/home640 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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: 0.0 ms 25.2 KiB
URLTransfer SizeEst Savings
/_next/static/css/874468d7c9b864e0.css?dpl=dpl_7tBuqLGahn...30.7 KiB25.2 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
The University of Western Australia li#uwa-header__container-logo > div.uwa-nav__logo > a > img
/visualid/devcore/1/_assets/img/uwacrest-small-white.svg
Group of 8 Member ul._member > li > a > img
static.weboffice.uwa.edu.au/visualid/devcore/1/_assets/img/member-go8_white.svg

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
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 26 user timings
●JavaScript execution time 0.8 s
●Minimizes main-thread work 1.8 s
●Avoid long main-thread tasks 9 long tasks found
●Avoid non-composited animations 1 animated element found
●Network Requests
●Network Round Trip Times 310 ms
●Server Backend Latencies 1,340 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid large layout shifts 1 layout shift found
○INP breakdown
92

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Study li#uwa-header__container-site > nav#uwa-nav__site > ul.__display > li
Life at UWA li#uwa-header__container-site > nav#uwa-nav__site > ul.__display > li
Our research li#uwa-header__container-site > nav#uwa-nav__site > ul.__display > li
Partners and community li#uwa-header__container-site > nav#uwa-nav__site > ul.__display > li
About us li#uwa-header__container-site > nav#uwa-nav__site > ul.__display > li
More li#uwa-header__container-site > nav#uwa-nav__site > ul.__display > li

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Australia nav > details.uwa-footer__language > summary._flag-australia > a

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
●`[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>`).
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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>`.
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: the server responded with a status of 404 ()

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
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

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
How can we help you? div._inner > div._title > h2 > a

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

Send Feedback