Spain · Madrid Completed: Apr 21, 2026 23:27 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 73 / 100
Based on 8 categories, 0 sections
Room to improve — your 17.9s load time is above Google's 2.5s 'Good' threshold.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Well-optimized for search — your content is discoverable.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Rich content metadata — your pages look great everywhere.
Heavier than average — reducing page weight saves energy and bandwidth.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 15.4 MB (4.2 MB transferred)
Performance issues directly impact user engagement and conversion rates.
1 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
2 image(s) missing alt attribute
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/5b4f1f5c-d42f-4953-910d-f2979d68f9f7)<a href="https://beavercheck.com/results/5b4f1f5c-d42f-4953-910d-f2979d68f9f7"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fadelaide.edu.au" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fadelaide.edu.auThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 17.9s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.
9 barrier(s) likely increasing bounce by ~33%.
Page takes 17.9s to load
+12% bounceUsers abandon at ~3s — you're 15.4s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 2.2s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Layout shifts during page load
+3% bounceContent movement causes mis-clicks on CTAs and form fields
Fix: Add width/height to images; reserve space for late-loading embeds
1 form field(s) without a label
+2% bounceScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
Fix: Associate every input with a visible <label for="…">; add autocomplete attributes
Content is hard to read
+2% bounceGraduate-level reading difficulty — limits the addressable audience for product or blog pages
Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
3 broken link(s) on the page
+5% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
AUD 660 investment → AUD 1.64/month returns + AUD 50,200,000 risk avoided
AUD 660
6h · 5 findings
AUD 1.64 /mo
~AUD 20 / year
AUD 50,200,000
if kept compliant
AUD 110 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
6.0 developer hours at A$110/hr
Based on Australia rates (A$110/hr)
Start here for the best return on investment
AUD 4,183,335 / month at risk
~AUD 50,200,020 / year if left unfixed
AUD 50,200,000
+4 more
AUD 1.64 /mo
13297.7 MB/mo × 0.123 AUD/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.02 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
17.93 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.19 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.127
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
7.24 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
32.82 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
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.
Performance issues directly impact user engagement and conversion rates.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Adelaide University div.herobanner > div#teaser-58e1634af2 > picture.cmp-herobanner__image > img | /content/dam/adelaideuniversity/images/home/banners/banne... | 211.0 KiB | 199.2 KiB |
Adelaide University div.herobanner > div#teaser-a9576f9a35 > picture.cmp-herobanner__image > img | /content/dam/adelaideuniversity/images/home/banners/hero-... | 71.6 KiB | 47.8 KiB |
Adelaide University city buildings div.herobanner > div#teaser-22ed1d912f > picture.cmp-herobanner__image > img | /content/dam/adelaideuniversity/images/home/banners/hero-... | 101.2 KiB | 30.2 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
This website uses cookies to ensure you get the best experience on our website,… div.aem-Grid > div.cookiesbanner > div#cookiesbanner-275a0be0f4 > dialog#cookiebanner--initial-alert | 0.126 |
clear search button div.cmp-fb--search > form > div.cmp-fb--search-field-wrapper > div.cmp-fb--search-input-suggestion | 0.001 |
Find your degree or career div > div > div.cmp-fb--search > h2.cmp-searchbar--title--text | 0.000 |
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.
Performance issues directly impact user engagement and conversion rates.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-c... | 294.7 KiB | 45.4 KiB |
| /etc.clientlibs/core/fd/af-clientlibs/core-forms-componen... | 116.5 KiB | 31.2 KiB |
| launchpad.privacymanager.io/latest/launchpad.bundle.js | 40.2 KiB | 12.7 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-w... | 64.8 KiB | 61.0 KiB |
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-c... | 63.6 KiB | 58.7 KiB |
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-b... | 11.0 KiB | 10.8 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-c... | 294.7 KiB | 235.6 KiB |
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-w... | 423.6 KiB | 212.4 KiB |
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 361.8 KiB | 176.9 KiB |
| t.contentsquare.net/uxa/9fe0d40f5d1d5.js | 137.9 KiB | 109.0 KiB |
| analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwOQ.js | 120.9 KiB | 92.5 KiB |
| /etc.clientlibs/core/fd/af-clientlibs/core-forms-componen... | 116.5 KiB | 74.1 KiB |
| www.googletagmanager.com/gtag/js?id=AW-16577573883 | 143.6 KiB | 61.3 KiB |
| analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js | 109.2 KiB | 55.8 KiB |
| www.googletagmanager.com/gtag/js?id=AW-16615096847 | 146.6 KiB | 53.4 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.5 KiB | 30.4 KiB |
| assets.adobedtm.com/be58e65e508a/0b9fe534cc0d/launch-57963a17723e.min.js | 169.6 KiB | 27.0 KiB |
| /etc.clientlibs/clientlibs/granite/jquery.lc-784289902421... | 35.0 KiB | 23.3 KiB |
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-b... | 31.3 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.
Performance issues directly impact user engagement and conversion rates.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 5.1 s |
| Other | 1.1 s |
| Script Parsing & Compilation | 804 ms |
| Style & Layout | 682 ms |
| Parse HTML & CSS | 160 ms |
| Garbage Collection | 116 ms |
| Rendering | 98 ms |
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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Performance issues directly impact user engagement and conversion rates.
| URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
Close icon div.cmp-cookiebanner > div.cmp-cookiebanner__close > a > img.cookiebanner-close | adelaide.edu.au/content/dam/adelaideuniversity/images/global/graphics/close.png | 12 x 12 | 16 x 16 | 18 x 18 |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | |
| AttributionReporting |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| /about/news/2026/daily-probiotic-could-help-prevent-skin-... | Read More |
| adelaide.edu.au/about/news/2026/recreational-ketamine-use-is-on-the-rise/ | Read More |
| /about/news/2026/seaweed-compound-shows-major-methane-cut... | Read More |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
635 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.98 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
346 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.014
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.25 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
6.46 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Adelaide University div.herobanner > div#teaser-58e1634af2 > picture.cmp-herobanner__image > img | /content/dam/adelaideuniversity/images/home/banners/banne... | 211.0 KiB | 158.9 KiB |
Girl looking down at two dogs div.cmp-teaser__image > div.cmp-image > div#teaser-5bf6546a75-image > img.cmp-image__image | /adobe/dynamicmedia/deliver/dm-aid--95a8467c-8fe6-428c-93... | 126.5 KiB | 110.4 KiB |
Wastewater research div.cmp-teaser__image > div.cmp-image > div#teaser-721de72824-image > img.cmp-image__image | /adobe/dynamicmedia/deliver/dm-aid--c3214386-58a1-4bf2-9c... | 123.4 KiB | 106.6 KiB |
Adelaide University div.herobanner > div#teaser-a9576f9a35 > picture.cmp-herobanner__image > img | /content/dam/adelaideuniversity/images/home/banners/hero-... | 165.6 KiB | 79.2 KiB |
Black cows in a paddock div.cmp-teaser__image > div.cmp-image > div#teaser-92c9faf4ad-image > img.cmp-image__image | /adobe/dynamicmedia/deliver/dm-aid--56140db7-d1ec-4cec-a1... | 70.5 KiB | 61.6 KiB |
Adelaide University city buildings div.herobanner > div#teaser-22ed1d912f > picture.cmp-herobanner__image > img | /content/dam/adelaideuniversity/images/home/banners/hero-... | 101.2 KiB | 17.3 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-c... | 294.7 KiB | 45.4 KiB |
| /etc.clientlibs/core/fd/af-clientlibs/core-forms-componen... | 116.4 KiB | 31.2 KiB |
| launchpad.privacymanager.io/latest/launchpad.bundle.js | 40.2 KiB | 12.7 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-w... | 64.8 KiB | 60.9 KiB |
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-c... | 63.6 KiB | 59.2 KiB |
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-b... | 11.0 KiB | 10.9 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-c... | 294.7 KiB | 235.6 KiB |
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-w... | 423.7 KiB | 212.4 KiB |
| www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js | 361.8 KiB | 177.0 KiB |
| t.contentsquare.net/uxa/9fe0d40f5d1d5.js | 137.9 KiB | 109.0 KiB |
| analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js | 109.2 KiB | 84.4 KiB |
| /etc.clientlibs/core/fd/af-clientlibs/core-forms-componen... | 116.4 KiB | 74.1 KiB |
| www.googletagmanager.com/gtag/js?id=AW-16577573883 | 143.6 KiB | 62.0 KiB |
| analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwOQ.js | 120.9 KiB | 60.3 KiB |
| www.googletagmanager.com/gtag/js?id=AW-16615096847 | 146.6 KiB | 51.7 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.5 KiB | 30.9 KiB |
| assets.adobedtm.com/be58e65e508a/0b9fe534cc0d/launch-57963a17723e.min.js | 185.6 KiB | 29.5 KiB |
| /etc.clientlibs/clientlibs/granite/jquery.lc-784289902421... | 35.0 KiB | 23.3 KiB |
| /etc.clientlibs/adelaideuniversity/clientlibs/clientlib-b... | 31.2 KiB | 23.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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.4 s |
| Other | 335 ms |
| Script Parsing & Compilation | 238 ms |
| Style & Layout | 179 ms |
| Parse HTML & CSS | 51 ms |
| Garbage Collection | 22 ms |
| Rendering | 22 ms |
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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | |
| AttributionReporting |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| /about/news/2026/daily-probiotic-could-help-prevent-skin-... | Read More |
| adelaide.edu.au/about/news/2026/recreational-ketamine-use-is-on-the-rise/ | Read More |
| /about/news/2026/seaweed-compound-shows-major-methane-cut... | Read More |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback