Skip to content
Audit Complete

Results for https://healthdirect.gov.au

Visit site
AU · AUD (A$) · Estimated Applicable regulations: Privacy Act 1988 · DDA Dev cost: A$ 110/hr How jurisdiction is detected
Corporate / Enterprise · estimated Tracking: leads
Singapore Singapore · Singapore Completed: Apr 22, 2026 22:01 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C73

Site Health

Score: 73 / 100

Based on 8 categories, 0 sections

Room to improve — your 27.8s 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.

Good server performance with room for optimization.

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.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Amazon Route 53 · 966 peers
You 73
·
Avg 72
At average
0 50 100
Better than 50% of Amazon Route 53 sites See full Amazon Route 53 benchmark →
Babel · 97 peers
You 73
·
Avg 70
At average
0 50 100
Better than 72% of Babel sites See full Babel benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
3

Page weighs 8.9 MB (4.7 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
4

1 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
5

1 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fhealthdirect.gov.au)](https://beavercheck.com/results/e8bc2311-60bd-4b35-aaf8-b2fbd182a734)
<a href="https://beavercheck.com/results/e8bc2311-60bd-4b35-aaf8-b2fbd182a734"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fhealthdirect.gov.au" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fhealthdirect.gov.au

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 27.8s 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.

2 security gaps detected — browsers may warn visitors about your site.
Your LCP is 27.8s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

3 critical 5 warning

8 barrier(s) likely increasing bounce by ~31%.

Speed (2)

Page takes 27.8s to load

+12% bounce

Users abandon at ~3s — you're 25.3s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 2.3s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning 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% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

Severe layout shift during page load

+6% bounce

Users mis-click when content jumps — converting intent into frustration

Fix: Reserve space for images, ads, and embeds with explicit width/height

1 form field(s) without a label

+2% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard 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

1 broken link(s) on the page

+2% bounce

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

Return on Investment

AUD 660 investment → AUD 1.82/month returns + AUD 50,200,000 risk avoided

Payback period: > 2 years First-year ROI: -97%

Investment

AUD 660

6h · 5 findings

Monthly returns

AUD 1.82 /mo

~AUD 22 / year

  • Bandwidth savings AUD 1.82

Regulatory risk avoided

AUD 50,200,000

if kept compliant

  • Privacy Act 1988 AUD 50,000,000
  • DDA AUD 200,000

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.

Full methodology & sources

Estimated Remediation Cost

A$660

6.0 developer hours at A$110/hr

Based on Australia rates (A$110/hr)

Quick wins
A$110 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
A$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

AUD 4,183,335 / month at risk

~AUD 50,200,022 / year if left unfixed

Compliance Risk

AUD 50,200,000

Privacy Act 1988DDA
  • No privacy policy link detected
    Privacy Act 1988: AUD 66,000 – AUD 50,000,000
  • 2 advertising/retargeting trackers detected
    Privacy Act 1988: AUD 66,000 – AUD 50,000,000
  • Trackers detected but no cookie policy found
    Privacy Act 1988: AUD 66,000 – AUD 50,000,000

+6 more

Bandwidth Waste

AUD 1.82 /mo

14784.8 MB/mo × 0.123 AUD/GB

  • Optimize transfer: save ~1.5 MB per page load
    Saves AUD 1.82/mo

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.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

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

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

5
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
58
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

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.

7.48 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

27.79 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

2.31 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.855

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

27.85 s

Detailed Report

Audit breakdown by category with detailed findings.

5

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

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.

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
/images/carousel/w1920h1080/bf5n5a_farmer-on-mobile-phone...0.0 ms1.6 MiB
www.healthdirect.gov.au/assets/1/styles/main.css600.0 s666.2 KiB
www.healthdirect.gov.au/assets/1/scripts/veyron.js600.0 s125.6 KiB
/signals/config/286390378916509?v=2.9.303&r=stable&domain...1200.0 s101.9 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
www.healthdirect.gov.au/assets/images/logo-gov-wa.svg600.0 s69.1 KiB
www.healthdirect.gov.au/assets/images/logo-gov-dep-health.svg600.0 s43.6 KiB
/components/webcomponentsjs/0.7.20/webcomponents-lite.min.js600.0 s39.0 KiB
www.healthdirect.gov.au/assets/images/SC-landing_page.svg600.0 s38.5 KiB
/signals/config/269174040245015?v=2.9.303&r=stable&domain...1200.0 s34.6 KiB
cdn-oc.readspeaker.com/script/8207/webReader/webReader.js?pids=wr0.0 ms28.2 KiB
www.healthdirect.gov.au/assets/images/logo-gov-qld.svg600.0 s28.4 KiB
www.healthdirect.gov.au/assets/1/scripts/hsfPanel.js600.0 s24.3 KiB
www.healthdirect.gov.au/assets/images/logo-gov-act.svg600.0 s21.5 KiB
www.healthdirect.gov.au/assets/images/logo-gov-sa.svg600.0 s21.0 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
/script/8207/webReader/r/r2889/ReadSpeaker.Styles-Button....86400.0 s39.8 KiB
www.healthdirect.gov.au/assets/1/scripts/auth.js600.0 s10.3 KiB
www.healthdirect.gov.au/assets/1/scripts/http-helper.js600.0 s9.5 KiB
www.healthdirect.gov.au/assets/images/logo-gov-tas.svg600.0 s8.9 KiB
www.healthdirect.gov.au/assets/images/logo-hda.svg600.0 s6.5 KiB
www.healthdirect.gov.au/assets/images/app-google-play.png600.0 s6.3 KiB
www.healthdirect.gov.au/assets/images/app-apple-store.png600.0 s6.2 KiB
www.healthdirect.gov.au/assets/images/logo-gov-nsw.svg600.0 s5.6 KiB
www.healthdirect.gov.au/assets/images/logo-gov-nt.svg600.0 s5.4 KiB
www.healthdirect.gov.au/assets/images/logo-gov-vic.svg600.0 s4.4 KiB
www.healthdirect.gov.au/assets/1/scripts/home.js600.0 s3.1 KiB
www.healthdirect.gov.au/assets/1/scripts/idle-session-timeout.js600.0 s2.5 KiB
www.healthdirect.gov.au/components/veyron/bootstrapper.js600.0 s1.7 KiB
/rp.gif?ts=1776895251963&id=a2_h7rhbsh1b9m8&event=PageVis...0.0 ms666 B
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.3 KiB
/tr/?id=269174040245015&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms19 B
/tr/?id=286390378916509&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms16 B

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.855427] map[node:map[boundingRect:map[bottom:1613 height:1350 left:0 right:412 top:263 width:412] lhId:page-2-SECTION nodeLabel:Symptom Checker Get started Who is this symptom check for? Me Someone else B… path:2,HTML,1,BODY,4,MAIN,3,SECTION selector:body > main.homepage > section.homepage_content snippet:<section class="homepage_content"> type:node] score:0.855407 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1897 height:50 left:105 right:307 top:1847 width:203] lhId:page-6-IMG nodeLabel:Healthdirect logo path:2,HTML,1,BODY,13,SECTION,1,IMG selector:body > section.content_partners > img.content_partners-hda-logo snippet:<img class="content_partners-hda-logo" src="/assets/images/logo-hda.svg" alt="Healthdirect logo"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:49 height:44 left:274 right:308 top:5 width:34] lhId:page-1-BUTTON nodeLabel:Sign in path:2,HTML,1,BODY,3,HEADER,0,DIV,0,DIV,1,DIV,1,DIV,0,BUTTON selector:div.hda-head_content-common > div.hda-head_col-mob-menu > div#header-buttons-mobile > button.hda-head_col-mob-menu-account-signin-btn snippet:<button class="hda-head_col-mob-menu-account-signin-btn" aria-controls="menu-sign" aria-haspopup="menu" aria-expanded="false" onclick="handleToggle()"> type:node] score:2e-05 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:40 height:30 left:15 right:135 top:10 width:120] lhId:page-5-IMG nodeLabel:healthdirect australia logo path:2,HTML,1,BODY,3,HEADER,0,DIV,0,DIV,0,DIV,0,A,0,IMG selector:div.hda-head_content-common > div.hda-head_col-logo > a.hda-head_col-logo-link > img.hda-head_col-logo-img snippet:<img class="hda-head_col-logo-img" src="/assets/images/logo-hda.svg" alt="healthdirect australia logo"> type:node]]] type:subitems]]]

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.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:10.183 source:map[column:20540 line:5 type:source-location url:https://www.healthdirect.gov.au/assets/1/scripts/veyron.js urlProvider:network]] map[reflowTime:71.755 source:map[type:text value:[unattributed]]]]

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
Get health information and advice body > main.homepage > header.homepage_hero
/images/carousel/w1920h1080/bf5n5a_farmer-on-mobile-phone...1.6 MiB1.3 MiB

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-HEADER
nodeLabel: Get health information and advice
path: 2,HTML,1,BODY,4,MAIN,1,HEADER
selector: body > main.homepage > header.homepage_hero
snippet: <header class="homepage_hero veyron-home-carousel show" style="background-image: url(&quot;https://media.healthdirect.org.au/images/carousel/w1…&quot;);">

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.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Symptom Checker Get started Who is this symptom check for? Me Someone else B… body > main.homepage > section.homepage_content
0.855
Sign in div.hda-head_content-common > div.hda-head_col-mob-menu > div#header-buttons-mobile > button.hda-head_col-mob-menu-account-signin-btn
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.

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: 3.4 s 618.0 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

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

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
Script Evaluation3.7 s
Other956 ms
Script Parsing & Compilation698 ms
Style & Layout399 ms
Garbage Collection171 ms
Parse HTML & CSS93 ms
Rendering80 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.4 KiB
URLTransfer SizeEst Savings
inline: function supported…3.1 KiB2.4 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
download from google play div.hda-foot_col-social-app > p > a > img.hda-foot_col-social-app-store-img
www.healthdirect.gov.au/assets/images/app-google-play.png
download from the App store div.hda-foot_col-social-app > p > a > img.hda-foot_col-social-app-store-img
www.healthdirect.gov.au/assets/images/app-apple-store.png
ACT Government logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-act.svg
Victorian government logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-vic.svg
Australian Government, health department logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-dep-health.svg
Government of South Australia logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-sa.svg
Tasmanian government logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-tas.svg
Government of Western Australia logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-wa.svg
healthdirect australia logo div.hda-head_content-common > div.hda-head_col-logo > a.hda-head_col-logo-link > img.hda-head_col-logo-img
www.healthdirect.gov.au/assets/images/logo-hda.svg
Healthdirect logo body > section.content_partners > img.content_partners-hda-logo
www.healthdirect.gov.au/assets/images/logo-hda.svg
New South Wales government logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-nsw.svg
Northern Territory Government logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-nt.svg
Queensland Government logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-qld.svg

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

Optimize DOM size
LCP breakdown
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 12 user timings
Avoid long main-thread tasks 20 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 590 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 290 ms
INP breakdown
Avoid non-composited animations
100

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.

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 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.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
Identical links have the same purpose.
`[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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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.
58

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
www.healthdirect.gov.au/Allowed

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
ReferenceError: require is not defined at https://www.healthdirect.gov.au/assets/1/scripts/http-helper.js:1:7335
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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

49
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
95
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
58
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

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.

2.04 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

5.63 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

148 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.231

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.39 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.04 s

Detailed Report

Audit breakdown by category with detailed findings.

49

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

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.

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
/images/carousel/w1920h1080/bf5n5a_farmer-on-mobile-phone...0.0 ms1.6 MiB
www.healthdirect.gov.au/assets/1/styles/main.css600.0 s666.2 KiB
www.healthdirect.gov.au/assets/1/scripts/veyron.js600.0 s125.6 KiB
/signals/config/286390378916509?v=2.9.303&r=stable&domain...1200.0 s101.9 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
www.healthdirect.gov.au/assets/images/logo-gov-wa.svg600.0 s69.1 KiB
www.healthdirect.gov.au/assets/images/logo-gov-dep-health.svg600.0 s43.6 KiB
/components/webcomponentsjs/0.7.20/webcomponents-lite.min.js600.0 s39.0 KiB
www.healthdirect.gov.au/assets/images/SC-landing_page.svg600.0 s38.5 KiB
/signals/config/269174040245015?v=2.9.303&r=stable&domain...1200.0 s34.6 KiB
cdn-oc.readspeaker.com/script/8207/webReader/webReader.js?pids=wr0.0 ms28.2 KiB
www.healthdirect.gov.au/assets/images/logo-gov-qld.svg600.0 s28.4 KiB
www.healthdirect.gov.au/assets/1/scripts/hsfPanel.js600.0 s24.3 KiB
www.healthdirect.gov.au/assets/images/logo-gov-act.svg600.0 s21.5 KiB
www.healthdirect.gov.au/assets/images/logo-gov-sa.svg600.0 s21.0 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
/script/8207/webReader/r/r2889/ReadSpeaker.Styles-Button....86400.0 s39.9 KiB
www.healthdirect.gov.au/assets/1/scripts/auth.js600.0 s10.3 KiB
www.healthdirect.gov.au/assets/1/scripts/http-helper.js600.0 s9.5 KiB
www.healthdirect.gov.au/assets/images/logo-gov-tas.svg600.0 s8.9 KiB
www.healthdirect.gov.au/assets/images/logo-hda.svg600.0 s6.5 KiB
www.healthdirect.gov.au/assets/images/app-google-play.png600.0 s6.3 KiB
www.healthdirect.gov.au/assets/images/app-apple-store.png600.0 s6.2 KiB
www.healthdirect.gov.au/assets/images/logo-gov-nsw.svg600.0 s5.6 KiB
www.healthdirect.gov.au/assets/images/logo-gov-nt.svg600.0 s5.4 KiB
www.healthdirect.gov.au/assets/images/logo-gov-vic.svg600.0 s4.4 KiB
www.healthdirect.gov.au/assets/1/scripts/home.js600.0 s3.1 KiB
www.healthdirect.gov.au/assets/1/scripts/idle-session-timeout.js600.0 s2.5 KiB
www.healthdirect.gov.au/components/veyron/bootstrapper.js600.0 s1.7 KiB
/rp.gif?ts=1776895270373&id=a2_h7rhbsh1b9m8&event=PageVis...0.0 ms666 B
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.3 KiB
/tr/?id=269174040245015&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms19 B
/tr/?id=286390378916509&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms16 B

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.230751] map[node:map[boundingRect:map[bottom:1201 height:592 left:0 right:1350 top:609 width:1350] lhId:page-7-SECTION nodeLabel:Check your symptoms Find a health service Find health information Symptom Chec… path:2,HTML,1,BODY,4,MAIN,3,SECTION selector:body > main.homepage > section.homepage_content snippet:<section class="homepage_content"> type:node] score:0.230418 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1161 height:241 left:170 right:655 top:920 width:485] lhId:page-10-IMG nodeLabel:div.veyron-symptomchecker-panel-homepage > form.cont > div.widget-sym-col > img.widget-sym-img path:2,HTML,1,BODY,4,MAIN,3,SECTION,1,DIV,1,DIV,1,SECTION,0,DIV,0,FORM,0,DIV,2,IMG selector:div.veyron-symptomchecker-panel-homepage > form.cont > div.widget-sym-col > img.widget-sym-img snippet:<img class="widget-sym-img tablet-up" src="assets/images/SC-landing_page.svg"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:142 height:42 left:857 right:1200 top:100 width:343] lhId:page-3-FORM nodeLabel:Enter your search terms path:2,HTML,1,BODY,3,HEADER,0,DIV,1,DIV,2,NAV,1,UL,5,LI,1,FORM selector:nav.hda-head_menu-row-bar > ul.hda-head_menu-row-bar-nav > li.hda-head_menu-row-bar-nav-level-1-item > form#search-form-node-desktop-mode snippet:<form id="search-form-node-desktop-mode" class="hda-head_menu-row-node-desktop-mode-search"> type:node] score:0.000333 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1161 height:241 left:170 right:655 top:920 width:485] lhId:page-10-IMG nodeLabel:div.veyron-symptomchecker-panel-homepage > form.cont > div.widget-sym-col > img.widget-sym-img path:2,HTML,1,BODY,4,MAIN,3,SECTION,1,DIV,1,DIV,1,SECTION,0,DIV,0,FORM,0,DIV,2,IMG selector:div.veyron-symptomchecker-panel-homepage > form.cont > div.widget-sym-col > img.widget-sym-img snippet:<img class="widget-sym-img tablet-up" src="assets/images/SC-landing_page.svg"> type:node]]] type:subitems]]]

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.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:12.719 source:map[column:20540 line:5 type:source-location url:https://www.healthdirect.gov.au/assets/1/scripts/veyron.js urlProvider:network]] map[reflowTime:36.767 source:map[type:text value:[unattributed]]]]

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
Get health information and advice body > main.homepage > header.homepage_hero
/images/carousel/w1920h1080/bf5n5a_farmer-on-mobile-phone...1.6 MiB1.3 MiB
download from google play div.hda-foot_col-social-app > p > a > img.hda-foot_col-social-app-store-img
www.healthdirect.gov.au/assets/images/app-google-play.png5.5 KiB4.1 KiB
download from the App store div.hda-foot_col-social-app > p > a > img.hda-foot_col-social-app-store-img
www.healthdirect.gov.au/assets/images/app-apple-store.png5.5 KiB4.1 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-0-HEADER
nodeLabel: Get health information and advice
path: 2,HTML,1,BODY,4,MAIN,1,HEADER
selector: body > main.homepage > header.homepage_hero
snippet: <header class="homepage_hero veyron-home-carousel show" style="background-image: url(&quot;https://media.healthdirect.org.au/images/carousel/w1…&quot;);">

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.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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: 683 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Check your symptoms Find a health service Find health information Symptom Chec… body > main.homepage > section.homepage_content
0.230
Enter your search terms nav.hda-head_menu-row-bar > ul.hda-head_menu-row-bar-nav > li.hda-head_menu-row-bar-nav-level-1-item > form#search-form-node-desktop-mode
0.000

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

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: 620 ms 651.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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

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

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.4 KiB
URLTransfer SizeEst Savings
inline: function supported…3.1 KiB2.4 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
div.veyron-symptomchecker-panel-homepage > form.cont > div.widget-sym-col > img.widget-sym-img div.veyron-symptomchecker-panel-homepage > form.cont > div.widget-sym-col > img.widget-sym-img
www.healthdirect.gov.au/assets/images/SC-landing_page.svg
download from google play div.hda-foot_col-social-app > p > a > img.hda-foot_col-social-app-store-img
www.healthdirect.gov.au/assets/images/app-google-play.png
download from the App store div.hda-foot_col-social-app > p > a > img.hda-foot_col-social-app-store-img
www.healthdirect.gov.au/assets/images/app-apple-store.png
ACT Government logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-act.svg
Victorian government logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-vic.svg
Australian Government, health department logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-dep-health.svg
Government of South Australia logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-sa.svg
Tasmanian government logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-tas.svg
Government of Western Australia logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-wa.svg
healthdirect australia logo div.hda-head_content-common > div.hda-head_col-logo > a.hda-head_col-logo-link > img.hda-head_col-logo-img
www.healthdirect.gov.au/assets/images/logo-hda.svg
Healthdirect logo body > section.content_partners > img.content_partners-hda-logo
www.healthdirect.gov.au/assets/images/logo-hda.svg
New South Wales government logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-nsw.svg
Northern Territory Government logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-nt.svg
Queensland Government logo section.content_partners > div > a > img
www.healthdirect.gov.au/assets/images/logo-gov-qld.svg

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

Max Potential First Input Delay 120 ms
Optimize DOM size
LCP breakdown
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 14 user timings
JavaScript execution time 0.8 s
Minimizes main-thread work 1.5 s
Avoid long main-thread tasks 5 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 360 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 110 ms
INP breakdown
Avoid non-composited animations
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.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.veyron-symptomchecker-panel-homepage > form.cont > div.widget-sym-col > img.widget-sym-img div.veyron-symptomchecker-panel-homepage > form.cont > div.widget-sym-col > img.widget-sym-img

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
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
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
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 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.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
Identical links have the same purpose.
`[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 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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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.
58

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
www.healthdirect.gov.au/Allowed

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
ReferenceError: require is not defined at https://www.healthdirect.gov.au/assets/1/scripts/http-helper.js:1:7335
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
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.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.veyron-symptomchecker-panel-homepage > form.cont > div.widget-sym-col > img.widget-sym-img div.veyron-symptomchecker-panel-homepage > form.cont > div.widget-sym-col > img.widget-sym-img

Format your HTML in a way that enables crawlers to better understand your app’s content.

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
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback