Insights

Google Lighthouse Performance

The Google Lighthouse performance score is a metric that measures the speed and performance of a website. It’s an overall score that ranges from 0 to 100 and is generated based on a number of different performance metrics, such as the time it takes for a website to load, the time it takes for a website to become interactive, the size of the resources used by the website, and other factors that impact the user experience.

A high performance score in Google Lighthouse indicates that a website is fast and responsive, which can lead to a better user experience and improved search engine rankings. On the other hand, a low performance score can indicate that a website is slow and unresponsive, and can negatively impact the user experience.

Mobile Performance
29%
Desktop Performance
23%

Core Web Vitals

Core Web Vitals are a set of specific factors that Google considers important in a webpage’s overall user experience. Core Web Vitals are made up of three specific page speed and user interaction measurements: Largest Contentful PaintFirst Input Delay, and Cumulative Layout Shift.

Pass or fail?

MobileFail
DesktopFail

CWV Breakdown

VitalMobileDesktopTarget
Largest Contentful Paint59.6 s8.2 s< 2.5 s
First Input Delay460 ms450 ms< 100ms
Cumulative Layout Shift0.0810.257 0.1

Tracking scripts

All the tracking scripts on the site generated ~1 MB of data

A tracking script is a code snippet designed to track the flow of visitors who visit a website. Media, advertising, and analytics organisations will provide a script to add to your website that sends data directly to their servers. This data can then be used to measure goals and conversions, analyse user behaviour, and influence advertising campaigns.

Consider how much of this data you actually need and use? How often do you review the analytics data, and does this inform genuine change? Are you actively running social media campaigns? Consider pausing or removing tracking scripts that aren’t being actively used.

View details
idgets.outbrain.com 9 120 KB
securepubads.g.doubleclick.net 19 700 KB
idget-pixels.outbrain.com 1 577 B
mv.outbrain.com 1 7 KB
static.cloudflareinsights.com 1 7 KB
c.amazon-adsystem.com 3 95 KB
ib.adnxs.com 8 6 KB
match.adsrvr.org 9 6 KB
aa.agkn.com 2 2 KB
x.bidswitch.net 7 5 KB
dis.criteo.com 1 432 B
cm.g.doubleclick.net 16 11 KB
dsp-cookie.adfarm1.adition.com 1 631 B
ps.eyeota.net 6 4 KB
pixel.rubiconproject.com 12 19 KB
loadus.exelator.com 3 3 KB
ssum-sec.casalemedia.com 2 3 KB
image8.pubmatic.com 3 3 KB
u.openx.net 2 2 KB
ups.analytics.yahoo.com 4 3 KB
ad.360yield.com 2 1 KB
s.ad.smaato.net 1 633 B
ssbsync.smartadserver.com 1 575 B
c.bing.com 2 2 KB
pixel-sync.sitescout.com 2 2 KB
cms.quantserve.com 2 1 KB
bh.contextweb.com 1 2 KB
trace.mediago.io 1 731 B
cm.rtbsystem.com 1 2 KB
rtb.adentifi.com 1 51 B
pxl.iqm.com 1 938 B
sync.1rx.io 1 427 B
cs.media.net 1 751 B
cs.admanmedia.com 1 0 B
csync.loopme.me 1 569 B
temu.com 1 894 B
sync.teads.tv 1 704 B
sync.outbrain.com 28 6 KB
pippio.com 2 1 KB
config.aps.amazon-adsystem.com 1 928 B
aax.amazon-adsystem.com 2 1 KB
htlb.casalemedia.com 2 2 KB
rtb.openx.net 2 1 KB
tlx.3lift.com 2 0 B
hbopenbid.pubmatic.com 2 860 B
image2.pubmatic.com 7 5 KB
ad.doubleclick.net 1 849 B
image4.pubmatic.com 2 1,001 B
s.amazon-adsystem.com 6 5 KB
google.com 4 1 KB
eventlog.outbrain.com 1 331 B
jadserve.postrelease.com 1 706 B
ads.pubmatic.com 2 14 KB
eb2.3lift.com 10 7 KB
microsoft-aunz-d.openx.net 1 1 KB
acdn.adnxs.com 1 17 KB
image6.pubmatic.com 2 6 KB
us-u.openx.net 3 1 KB
aax-eu.amazon-adsystem.com 2 1 KB
jp-u.openx.net 2 792 B
c1.adform.net 2 2 KB
uipglob.semasio.net 3 2 KB
um.simpli.fi 1 989 B
simage2.pubmatic.com 5 4 KB
px.ads.linkedin.com 2 1 KB
cms.analytics.yahoo.com 1 372 B
sg.semasio.net 2 1 KB
sync.ipredictive.com 2 1 KB
pixel.tapad.com 4 5 KB
simage4.pubmatic.com 2 712 B
sync-tm.everesttech.net 4 2 KB
p.rfihub.com 1 853 B
pixel.onaudience.com 1 358 B
d.turn.com 1 624 B
dpm.demdex.net 1 1 KB

Opportunities

Assets that need text compression enabled502 KB0.112g

By enabling text compression on 2 items, , roughly 502.5 KB could be removed from the page load.

View details
pubads_impl.js 536 KB 352 KB
ufs_web_display.js 221 KB 150 KB
Optimise images10 MB2.395g

By optimising the following images, roughly 10 MB could be removed from the transfer size, about 62%. This would reduce the CO2 generated per page load from 3.88g grams to 1.49 grams.

Images should be optimised for the web for several reasons:

  1. Reduced file size: Optimizing images can result in a smaller file size, which can help to reduce the amount of data that needs to be downloaded. This can lead to faster page load times and improved performance.
  2. Improved user experience: Optimising images can help to improve the overall user experience, as pages with optimised images load faster and are more responsive.
  3. Lower emissions: Optimising images can help to reduce the emissions associated with data transfer, as less data needs to be transmitted over the network.
  4. Better accessibility: Optimising images can make them more accessible to users with slower connections or limited data plans.
View details
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F15abb4ed-8c3f-4305-bce7-9ceddc23dc99 9 MB 53% 9 MB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F90914fdd-560c-4b18-bd40-2bd0dbc1cd14 270 KB 2% 251 KB
png 167 KB 1% 110 KB
png 166 KB 1% 110 KB
png 166 KB 1% 109 KB
png 165 KB 1% 109 KB
png 165 KB 1% 110 KB
terrain_radar_071_960x720.jpg 165 KB 1% 116 KB
png 165 KB 1% 109 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fec8a13da-28b4-4b60-861a-1541b656e84c 117 KB 1% 101 KB
1440995792465023716 75 KB 0% 39 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F02d8430b-8e2d-4322-a670-6d88e3b1b9d0 62 KB 0% 54 KB
16435823151229385626 58 KB 0% 44 KB
_300x2502x.jpg 57 KB 0% 37 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F3794a999-8a8c-48bf-9e90-f12e21310d7f 57 KB 0% 51 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fa3503251-7d0d-4bf5-a58f-dfa88278d12c 54 KB 0% 16 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F1856dec5-03cb-44f7-a49d-7d62ddcc26aa 54 KB 0% 17 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fc73e50cb-c91b-4527-b847-9e54ea6fcca7 52 KB 0% 17 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F3e48c8f9-0755-464f-ad35-759baeba1c1f 52 KB 0% 46 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fb3da3c33-3537-4e73-9722-e182a56469e7 50 KB 0% 44 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fb5236e8b-0ed6-43a6-944b-6f03a5c107db 46 KB 0% 16 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F4b9f39e9-08bf-47bf-bff9-dd9038d0582e 38 KB 0% 14 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F93f86da0-e6ae-4b9a-8bd8-1cec27a598c4 35 KB 0% 13 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F369363f1-6556-40fa-9771-d7a3cc699636 33 KB 0% 11 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F7f23d4cd-0925-4621-93c8-59a0d7073d62 32 KB 0% 12 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F2bf53047-9ac8-4b7e-8c26-1099dc71f975 30 KB 0% 26 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F9c46caa2-0261-49c3-ae55-6f602513492b 29 KB 0% 11 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F01c297ee-a314-486a-81bf-e7889c265c7b 29 KB 0% 24 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F9ada4bed-cd36-484d-bf1d-0803c22d403e 26 KB 0% 11 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F6582146a-30da-4dbf-a8b5-fdc87f8c5f5f 22 KB 0% 19 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F6431aa2a-b819-4499-82e7-f9750486667c 21 KB 0% 9 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Ff5b86652-a71b-44a5-8cec-7db2308e3f0b 19 KB 0% 16 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F37b5364d-7fe3-4d98-b8cb-92321e9f86e8 18 KB 0% 15 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fb0bac743-35b5-4916-821b-c6c92180edfe 18 KB 0% 15 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F392a4100-66f9-498c-a76d-9f470f5e96eb 13 KB 0% 11 KB
aca.676e2610.png 13 KB 0% 10 KB
Subset large font files57 KB0.013g

Fonts should be subsetted to reduce the file size, improve performance, and reduce emissions. Subsetting a font involves removing any characters that are not needed for a particular use case, resulting in a smaller file size and faster page load times. Some specific reasons why fonts should be subsetted include:

  1. Reduced file size: Subsetting a font removes any unused characters, which can result in a smaller file size. This can help to reduce the amount of data that needs to be downloaded, leading to faster page load times and lower emissions.
  2. Improved performance: Fonts that are subsetted are faster to load and render than fonts that are not subsetted. This can help to improve the overall performance of a website, leading to a better user experience.

Overall, subsetting fonts is a good practice for anyone looking to optimize the performance and reduce the emissions of a website of a website.

View details
c4250770ab8708b6-s.p.woff2 ~35 KB ~18 KB
hurme-black.woff ~31 KB ~13 KB
proximanova-bold.woff ~28 KB ~10 KB
proximanova-semibold.woff ~27 KB ~10 KB
b2142359fe988546-s.p.woff2 ~20 KB ~2 KB
ibm-plex-sans-v13-latin-600.woff2 ~19 KB ~2 KB
proximanova-regular.woff ~19 KB ~1 KB
ibm-plex-sans-v13-latin-regular.woff2 ~18 KB ~662 B
Convert font files to woff215 KB

WOFF2 is considered to be the best font format for web use because it provides a good balance of file size and compatibility. Some specific reasons why WOFF2 is a good font format include:

  1. Small file size: WOFF2 is a compressed font format, which means that it has a smaller file size compared to other font formats like TTF or OTF. This is important for web use because smaller file sizes can help to reduce the amount of data that needs to be downloaded, leading to faster page load times.
  2. High-quality font rendering: WOFF2 provides high-quality font rendering, making it a good choice for use on the web.

It’s worth noting that WOFF2 is not the only font format that can be used on the web, and there may be cases where other formats like WOFF or TTF are more suitable, depending on the specific requirements of the website. However, for most cases, WOFF2 is considered to be the best font format for web use due to its combination of small file size, good browser support, and high-quality font rendering.

View details
proximanova-semibold.woff woff
proximanova-bold.woff woff
hurme-black.woff woff
Remove third party font files

Font files should be loaded from the same hosting as the website because

  1. Increased loading time: Third-party sub-resources, such as scripts, fonts, or images, need to be downloaded from a separate server before they can be displayed on the website. This can increase the overall loading time of the page, leading to a slower user experience.
  2. Dependence on external servers: The loading of third-party subresources is dependent on the availability and performance of the external servers that host them. If these servers are slow or unavailable, it can result in slow page loading times or even errors.
  3. Increased risk of security threats: Third-party subresources can introduce security risks to a website, as they can contain malicious code or be used to track user activity.
View details
www.drive.com.au ibm-plex-sans-v13-latin-regular.woff2
www.drive.com.au ibm-plex-sans-v13-latin-600.woff2
www.drive.com.au b2142359fe988546-s.p.woff2
www.drive.com.au c4250770ab8708b6-s.p.woff2
fonts.gstatic.com 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2
First Contentful Paint

First Contentful Paint (FCP) is a performance metric that measures the time it takes for the first piece of content to be rendered on the screen when a user navigates to a web page. This content can be any visual element on the page, such as text, images, or a background color.

FCP is important because it directly affects the perceived speed of a website, and can impact user engagement and conversion rates. A faster FCP can lead to a better user experience and improved performance.

Here are a few ways you can optimise your FCP:

  1. Optimise images: Large, unoptimised images can slow down a page’s FCP. You can optimise images by compressing them, reducing their dimensions, and choosing the right format for each image.
  2. Minimise HTTP requests: Each resource requested by a web page, such as images, scripts, and stylesheets, requires a separate HTTP request. Minimising the number of HTTP requests can help to reduce the time it takes for a page to render.
  3. Prioritize critical content: Prioritizing critical content, such as above-the-fold content, can help to ensure that users see something on the screen quickly, even if the rest of the page is still loading.
  4. Reduce server response time: A slow server response time can significantly impact FCP. Optimizing server-side code and server settings can help to reduce response times and improve FCP.
  5. Use a performance monitoring tool: There are many tools available that can help you monitor your website’s performance, including FCP. These tools can help you identify performance issues and track your progress as you implement optimizations.
MobileDesktop
Score38%100%
Timing3.4 s0.4 s
Largest Contentful Paint

Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric

MobileDesktop
Score0%1%
Timing59.6 s8.2 s
Total Blocking Time

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.

MobileDesktop
Score5%1%
Timing2,370 ms1,490 ms
Cumulative Layout Shift

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.

MobileDesktop
Score94%48%
Timing0.0810.257
Speed Index

Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.

MobileDesktop
Score1%4%
Timing14.8 s4.8 s
Layout shift culprits

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.

MobileDesktop
Score100%0%
Optimize DOM size

A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size.

MobileDesktop
Score0%0%
Forced reflow

Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about forced reflow and its mitigations.

MobileDesktop
Score0%0%
LCP request discovery

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

MobileDesktop
Score0%0%
Network dependency tree

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.

MobileDesktop
Score0%0%
Time to Interactive

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.

MobileDesktop
Score0%2%
Timing59.6 s11.1 s
Max Potential First Input Delay

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.

MobileDesktop
Score11%12%
Timing460 ms450 ms