Skip to content
https://rjwdigital.com.au

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

61

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.

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.

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-DIV
nodeLabel: section#zgxktrcstxrzekybecxlccierlbbaouxbspz_zgxktrcstxrzekybecxlccierlbbaouxbspz > div.brz-section__content > div.brz-bg > div.brz-bg-image
path: 1,HTML,1,BODY,6,DIV,3,SECTION,0,DIV,0,DIV,0,DIV
selector: section#zgxktrcstxrzekybecxlccierlbbaouxbspz_zgxktrcstxrzekybecxlccierlbbaouxbspz > div.brz-section__content > div.brz-bg > div.brz-bg-image
snippet: <div class="brz-bg-image">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.0 s

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.

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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: 0.0 ms 3.5 KiB

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

Max Potential First Input Delay 110 ms
Layout shift culprits
Optimize DOM size
Font display
Forced reflow
Improve image delivery
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify JavaScript
Avoids enormous network payloads Total size was 2,334 KiB
JavaScript execution time 0.6 s
Minimizes main-thread work 1.9 s
Avoid long main-thread tasks 8 long tasks found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 240 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 200 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
User Timing marks and measures
Avoid non-composited animations
90

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Free Strategy Session div.brz-container > div.brz-wrapper-clone > a.brz-a > span.brz-span
Strategies to make your business more visible in today's digital world. div.brz-rich-text > div > p.brz-tp-lg-paragraph > span.brz-cp-color7
Learn More div.brz-column__items > div.brz-wrapper-clone > a.brz-a > span.brz-span
Brand and creative management to make your business stand out. div.brz-rich-text > div > p.brz-text-lg-center > span.brz-cp-color7
Learn More div.brz-column__items > div.brz-wrapper-clone > a.brz-a > span.brz-span
Focused ad campaigns to hand deliver targeted results to you. div.brz-rich-text > div > p.brz-text-lg-center > span.brz-cp-color7
Learn More div.brz-column__items > div.brz-wrapper-clone > a.brz-a > span.brz-span
Learn More div.brz-column__items > div.brz-wrapper-clone > a.brz-a > span.brz-span
1300 545 237 div.brz-column__items > div.brz-wrapper-clone > a.brz-a > span.brz-span
Read More div.brz-column__items > div.brz-wrapper-clone > a.brz-a > span.brz-span
Read More div.brz-column__items > div.brz-wrapper-clone > a.brz-a > span.brz-span
Read More div.brz-column__items > div.brz-wrapper-clone > a.brz-a > span.brz-span

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a
div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a
div.brz-column__items > div.brz-wrapper-clone > div.brz-icon__container > a.brz-a div.brz-column__items > div.brz-wrapper-clone > div.brz-icon__container > a.brz-a
div.brz-column__items > div.brz-wrapper-clone > div.brz-icon__container > a.brz-a div.brz-column__items > div.brz-wrapper-clone > div.brz-icon__container > a.brz-a
div.brz-column__items > div.brz-wrapper-clone > div.brz-icon__container > a.brz-a div.brz-column__items > div.brz-wrapper-clone > div.brz-icon__container > a.brz-a
div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a
div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a
div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a
div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a
div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a
div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a div.brz-column__items > div.brz-css-d-wrapper > div.brz-image > a.brz-a
div.brz-column__items > div.brz-wrapper-clone > div.brz-icon__container > a.brz-a div.brz-column__items > div.brz-wrapper-clone > div.brz-icon__container > a.brz-a
div.brz-column__items > div.brz-wrapper-clone > div.brz-icon__container > a.brz-a div.brz-column__items > div.brz-wrapper-clone > div.brz-icon__container > a.brz-a
div.brz-column__items > div.brz-wrapper-clone > div.brz-icon__container > a.brz-a div.brz-column__items > div.brz-wrapper-clone > div.brz-icon__container > a.brz-a

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
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
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[accesskey]` values are unique
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
Buttons have an accessible name
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
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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.
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.
81

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
85

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

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

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links are crawlable
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback