Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
www.qld.gov.au/home/_media/qldpremier.jpeg	180.0 s	42.3 KiB
www.qld.gov.au/design-system/_design/css/webfonts/fontawesome.css?v=0.1.2	180.0 s	24.2 KiB
app-script.monsido.com/v2/monsido-script.js	300.0 s	3.7 KiB
static.qgov.net.au/formio-qld/v2/v2.x.x-latest/formio-script.min.js	0.0 ms	1.4 KiB
cdn.jsdelivr.net/npm/flatpickr/dist/flatpickr.min.css	604800.0 s	3.8 KiB

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:32.487 source:map[column:11 line:517 type:source-location url:https://www.qld.gov.au/ urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Promotional image `section.qld-promo-panel > div.row > div.image-panel > img.promo-panel-image`	www.qld.gov.au/__data/assets/image/0019/612244/have-your-say.jpg	194.7 KiB	176.4 KiB
Making QLD Safer Promo `section.qld-promo-panel > div.row > div.image-panel > img.promo-panel-image`	www.qld.gov.au/__data/assets/image/0038/838568/qgov-mqs.jpg	70.9 KiB	56.4 KiB
Delivering for Queensland `div.col > div.card > div.card-img > div.card-img-top`	www.qld.gov.au/__data/assets/image/0021/833124/dfq.jpg	97.6 KiB	19.6 KiB
David Crisafulli, Premier of Queensland. `div.col-xs-12 > div.qld-link-list-card > div.card-img > div.qld-link-list-card__image`	www.qld.gov.au/home/_media/qldpremier.jpeg	41.8 KiB	18.9 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:350.964 label:Time to first byte subpart:timeToFirstByte] map[duration:398.924 label:Resource load delay subpart:resourceLoadDelay] map[duration:95.209 label:Resource load duration subpart:resourceLoadDuration] map[duration:1678.809 label:Element render delay subpart:elementRenderDelay]]

lhId: page-4-SECTION

nodeLabel: How can we help? Popular Public holidays Driver licence Car rego Apply for a Bl…

path: 1,HTML,1,BODY,15,MAIN,4,SECTION

selector: body#body > main#content > section.banner-with-search-tags__container

snippet: <section class="banner-with-search-tags__container banner-with-search-tags__container--bac…">

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-4-SECTION

nodeLabel: How can we help? Popular Public holidays Driver licence Car rego Apply for a Bl…

path: 1,HTML,1,BODY,15,MAIN,4,SECTION

selector: body#body > main#content > section.banner-with-search-tags__container

snippet: <section class="banner-with-search-tags__container banner-with-search-tags__container--bac…">

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.

URL	Transfer Size	Duration
www.qld.gov.au/design-system/_design/css/webfonts/fontawesome.css?v=0.1.2	24.2 KiB	150 ms
www.qld.gov.au/_qgdesigns/templates/qgds/qgds-banner/banner.css?v=0.0.12	5.4 KiB
www.qld.gov.au/_qgdesigns/css/qg-main.css?v=0.4.20	3.8 KiB
/__data/assets/git_bridge/0030/498603/assets/css/qld.boot...	128.7 KiB	1.5 s
/css?family=Lato:100,300,400,700,900,100italic,300italic,...	1.1 KiB	858 ms
/__data/assets/css_file_folder/0024/637152/homepage-style...	1.3 KiB
www.qld.gov.au/__data/assets/css_file_folder/0022/541309/QGDS-shim.css?v=0.5.103	18.4 KiB	300 ms
www.qld.gov.au/__data/assets/css_file/0025/644281/fancybox.min.css?v=0.1.0	4.0 KiB
www.qld.gov.au/__data/assets/css_file/0026/119177/squiz-119177_custom.css	1.9 KiB
www.qld.gov.au/__data/assets/css_file/0011/113510/rs-default.css	2.2 KiB
/__data/assets/css_file_folder/0027/644490/swe-legacy-sup...	6.5 KiB	150 ms
www.qld.gov.au/__data/assets/css_file/0019/113509/custom.css	4.4 KiB
www.qld.gov.au/__data/assets/css_file/0026/113399/royalslider.css	1.7 KiB
/__data/assets/css_file_folder/0015/110823/qg-components....	829 B
fonts.googleapis.com/css2?family=Noto+Sans:wght@400;600;700;900&display=swap	988 B	179 ms
cdn.jsdelivr.net/npm/flatpickr/dist/flatpickr.min.css	3.8 KiB	770 ms
code.jquery.com/jquery-3.6.1.min.js	30.6 KiB	1.1 s

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 818 ms

URL	Time Spent
qld.gov.au/	818 ms
www.qld.gov.au/	0.0 ms

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 240 ms 4.0 KiB

URL	Transfer Size	Est Savings
www.qld.gov.au/design-system/_design/css/webfonts/fontawesome.css?v=0.1.2	24.2 KiB	4.0 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 750 ms 130.7 KiB

URL	Transfer Size	Est Savings
/__data/assets/git_bridge/0030/498603/assets/css/qld.boot...	128.3 KiB	93.8 KiB
www.qld.gov.au/design-system/_design/css/webfonts/fontawesome.css?v=0.1.2	23.6 KiB	23.5 KiB
www.qld.gov.au/__data/assets/css_file_folder/0022/541309/QGDS-shim.css?v=0.5.103	18.0 KiB	13.5 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 660 ms 121.8 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-2BSW42XWCV&cx=c&gtm=4e64h1	174.3 KiB	64.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-PMDS7K	154.8 KiB	57.2 KiB

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	979 ms
Other	484 ms
Style & Layout	418 ms
Script Parsing & Compilation	163 ms
Parse HTML & CSS	138 ms
Rendering	33 ms

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

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

●User Timing marks and measures 5 user timings

●JavaScript execution time 1.1 s

●Avoid long main-thread tasks 10 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 80 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 130 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

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

●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

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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 the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

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

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

○Input buttons have discernible text.

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

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

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
code.jquery.com/jquery-3.6.1.min.js line 1, col 31702	`ReferenceError: slider is not defined at HTMLDocument.<anonymous> (https://www.qld.gov.au/__data/assets/js_file/0019/113392/custom.js?v=0.8.0:285:5) at e (https://code.jquery.com/jquery-3.6.1.min.js:2:30038) at t (https://code.jquery.com/jquery-3.6.1.min.js:2:30340)`

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`