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
34%
Desktop Performance
37%

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 Paint6.7 s1.3 s< 2.5 s
First Input Delay1,060 ms350 ms< 100ms
Cumulative Layout Shift0.0771.165 0.1

Tracking scripts

All the tracking scripts on the site generated ~585 KB 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 113 KB
securepubads.g.doubleclick.net 14 231 KB
idget-pixels.outbrain.com 1 577 B
mv.outbrain.com 1 7 KB
ib.adnxs.com 6 5 KB
match.adsrvr.org 6 4 KB
beacon.krxd.net 1 0 B
aa.agkn.com 1 857 B
x.bidswitch.net 4 2 KB
dis.criteo.com 1 432 B
cm.g.doubleclick.net 15 10 KB
dsp.adfarm1.adition.com 1 635 B
ps.eyeota.net 3 2 KB
pixel.rubiconproject.com 13 21 KB
loadus.exelator.com 3 3 KB
ssum-sec.casalemedia.com 2 3 KB
image8.pubmatic.com 3 3 KB
u.openx.net 2 1 KB
ups.analytics.yahoo.com 3 2 KB
ice.360yield.com 2 1 KB
s.ad.smaato.net 1 771 B
ssbsync.smartadserver.com 1 595 B
c.bing.com 2 2 KB
pixel-sync.sitescout.com 2 2 KB
cms.quantserve.com 2 2 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 953 B
sync.1rx.io 1 439 B
cs.media.net 1 801 B
cs.admanmedia.com 1 741 B
cr-p30.ladsp.com 2 2 KB
csync.loopme.me 1 581 B
sync.outbrain.com 27 6 KB
pippio.com 1 813 B
image2.pubmatic.com 5 2 KB
static.cloudflareinsights.com 1 7 KB
c.amazon-adsystem.com 3 81 KB
image4.pubmatic.com 2 882 B
ad.doubleclick.net 1 849 B
config.aps.amazon-adsystem.com 1 928 B
aax.amazon-adsystem.com 1 471 B
tlx.3lift.com 1 0 B
hbopenbid.pubmatic.com 1 198 B
htlb.casalemedia.com 1 932 B
rtb.openx.net 1 545 B
google.com 4 1 KB
eventlog.outbrain.com 1 331 B
ads.pubmatic.com 2 12 KB
eb2.3lift.com 10 7 KB
microsoft-aunz-d.openx.net 1 1,016 B
acdn.adnxs.com 1 17 KB
image6.pubmatic.com 2 6 KB
us-u.openx.net 4 2 KB
jp-u.openx.net 2 770 B
s.amazon-adsystem.com 5 4 KB
um.simpli.fi 1 989 B
sync.ipredictive.com 2 1 KB
simage2.pubmatic.com 5 2 KB
px.ads.linkedin.com 2 1 KB
aax-eu.amazon-adsystem.com 1 855 B
pixel.tapad.com 2 2 KB
simage4.pubmatic.com 1 356 B
p.rfihub.com 1 0 B
sync-tm.everesttech.net 1 0 B
pm.w55c.net 1 0 B

Opportunities

Assets that need text compression enabled1 KB0g

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

View details
PugMaster 2 KB 1 KB
Optimise images3 MB0.675g

By optimising the following images, roughly 3 MB could be removed from the transfer size, about 36%. This would reduce the CO2 generated per page load from 1.89g grams to 1.22 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%2F71d0fe88-3d32-466e-aa81-2f10a5d6221d 521 KB 6% 473 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F529e75f4-ccc6-4a74-ae65-6606221267de 496 KB 6% 456 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fb87e60a1-5d47-48f7-8220-767a6b2d167b 492 KB 6% 441 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F243a4ae2-ba50-4a66-a80d-5ae10ac5ddac 453 KB 5% 425 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F0f16c121-bb53-4460-a7be-f255fed9a084 414 KB 5% 371 KB
terrain_radar_071_960x720.jpg 165 KB 2% 116 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fe2eb281a-d5aa-4d49-9a80-56469a699b27 158 KB 2% 141 KB
2535071382309803173 81 KB 1% 66 KB
929688771883862112 74 KB 1% 33 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F4a54748a-ff5f-4d5e-9be1-88af8808483d 72 KB 1% 19 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fe8346f80-26cf-4685-866f-2b946c147678 69 KB 1% 16 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F5cca06cf-d88d-4b28-9102-89f96882ee4a 66 KB 1% 57 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F88114ce0-33b1-40b5-ab20-ce9f4784c693 55 KB 1% 16 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F7ffa8a66-852a-445c-bd03-86aa7094ac59 51 KB 1% 45 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fbd46fc8c-eebe-452a-99c9-59268bc0f5a0 50 KB 1% 15 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F59334729-6efc-4b0f-ba79-5b8ef0c98563 48 KB 1% 42 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fe84a9318-98e1-45ce-9f4f-4080fb505173 47 KB 1% 43 KB
7393566702861360674 40 KB 0% 23 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F75d69864-5b81-4faf-933c-6415ab55e228 39 KB 0% 14 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fca4c89d4-6b2b-400a-936b-6245aecfb9a3 36 KB 0% 13 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F7e8b1b47-686b-421e-a00d-1349cf6a9dc2 36 KB 0% 13 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F9f1340fc-adee-4228-bce6-474cfa79553f 30 KB 0% 12 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Ff00f83af-f50e-4251-9f3f-a670df18dff4 27 KB 0% 24 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fd7845a68-f761-4383-867c-3faa402f042c 27 KB 0% 23 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F5393831f-3335-472c-9d9f-eda48d15af24 24 KB 0% 21 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F95a0f888-cb99-46ab-bae5-89c63ac4833c 20 KB 0% 17 KB
png 19 KB 0% 9 KB
png 19 KB 0% 9 KB
png 19 KB 0% 9 KB
png 18 KB 0% 9 KB
png 18 KB 0% 9 KB
png 18 KB 0% 9 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F82d52d0c-123d-48a7-a2b9-1f5167324379 14 KB 0% 12 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fd8c587a0-fe86-4b1b-a6d5-489eb9d6a6e3 14 KB 0% 12 KB
aca.676e2610.png 13 KB 0% 10 KB
Subset large font files45 KB0.01g

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
hurme-black.woff ~31 KB ~13 KB
proximanova-bold.woff ~28 KB ~10 KB
proximanova-medium.woff ~27 KB ~10 KB
proximanova-semibold.woff ~27 KB ~10 KB
proximanova-regular.woff ~19 KB ~1 KB
ibm-plex-sans-v13-latin-regular.woff2 ~18 KB ~582 B
Convert font files to woff219 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-bold.woff woff
proximanova-semibold.woff woff
hurme-black.woff woff
proximanova-medium.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
fonts.gstatic.com 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.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
Score81%100%
Timing2.1 s0.5 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
Score8%87%
Timing6.7 s1.3 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
Score0%11%
Timing8,200 ms770 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
Score95%1%
Timing0.0771.165
Speed Index

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

MobileDesktop
Score1%15%
Timing14.8 s3.6 s
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%7%
Timing52.5 s9.0 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
Score0%25%
Timing1,060 ms350 ms
First Meaningful Paint

First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

MobileDesktop
Score85%98%
Timing2.6 s0.6 s