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
Desktop Performance

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?


CWV Breakdown

Largest Contentful Paint11.9 s2.0 s< 2.5 s
First Input Delay300 ms130 ms< 100ms
Cumulative Layout Shift0.1140.017 0.1

Tracking scripts

All the tracking scripts on the site generated ~428 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 2 182 KB 2 21 KB 2 4 KB 1 2 KB 6 7 KB 2 190 KB 2 576 B 3 3 KB 2 0 B 1 620 B 2 656 B 1 17 KB


Remove autoplaying or preloaded media files1 video12.2 MB3.21g CO2

By removing 1 autoplaying or preloaded videos, roughly 12.2 MB could be removed from the page load.

This would reduce the page transfer size by 57% and reduce the pages emissions from 5.6 grams of CO2 to 2.39 grams of CO2.

Autoplaying videos can have a negative impact on the user experience for several reasons:

  1. Increased data usage: Autoplaying videos can consume a lot of data, especially if they are set to play in high definition. This can be a problem for users with limited data plans or slow connections, who may experience slow or interrupted playback.
  2. Annoyance factor: Autoplaying videos can be annoying for users, especially if they are accompanied by sound. This can lead to a negative perception of the website and decreased engagement.
  3. Reduced accessibility: Autoplaying videos can be a problem for users with accessibility needs, such as users who are blind or have hearing difficulties.
  4. Increased page load time: Autoplaying videos can increase the overall page load time, leading to a slower user experience.
  5. Decreased battery life: Autoplaying videos can consume a lot of battery power, especially on mobile devices, leading to reduced battery life.

In order to minimise the impact of autoplaying videos on the user experience, it is recommended to use them sparingly and only when necessary. It is also important to provide users with the option to turn off autoplaying videos and to allow them to control the playback of videos on the page. Additionally, videos should be optimised for performance and should be accompanied by captions or transcripts to improve accessibility.

View details
alpine_biodiversity_webheader.mp4 12 MB 57%
Assets that need text compression enabled1 MB0.286g

By enabling text compression on 5 items, , roughly 1.1 MB could be removed from the page load.

View details
optimized-min.js 1 MB 974 KB
optimized-min.js 98 KB 71 KB
optimized-min.js 69 KB 53 KB
optimized-min.js 12 KB 8 KB
optimized-min.js 5 KB 3 KB
Optimise images4 MB1.042g

By optimising the following images, roughly 4 MB could be removed from the transfer size, about 19%. This would reduce the CO2 generated per page load from 5.6g grams to 4.56 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
volunteer-tour-yarra-bend-park-450x450.jpg 1 MB 6% 992 KB
junior-rangers-450x450.jpg 938 KB 4% 751 KB
220902_new-holland-honeyeater_1920x1124.jpg 725 KB 3% 481 KB
camping-lake-elizabeth-1140x667.png 543 KB 2% 484 KB
junior-rangers-ocean-grove-1920x307.jpg 505 KB 2% 351 KB
camping-grampians-peaks-trail-1200x250.jpg 442 KB 2% 356 KB
citizen-science-450x450.jpg 229 KB 1% 185 KB
all-abilities-wilsons-promontory-450x450.jpg 202 KB 1% 162 KB
wilsonsprom_sealerscove1_1140pxwide.jpg 138 KB 1% 28 KB
wattle-park-full-res-8181_1140w.jpg 107 KB 0% 25 KB
walking-4-budj-bim-national-park-1920x1124.jpg 96 KB 0% 20 KB
image-promotion.jpg 94 KB 0% 48 KB
3-walking-grampians-national-park-1920x1124.jpg 75 KB 0% 19 KB
lyrebird-ridge-track-tarra-bulga-national-park-1920x1124.jpg 73 KB 0% 18 KB
1-walking-kinglake-national-park-1920x1124.jpg 68 KB 0% 14 KB
1-lighthouse-point-hicks-croajingalong-national-park-1920x1124.jpg 62 KB 0% 15 KB
friends-walking-along-yarra-river-yarra-bend-park-1920x1124.jpg 61 KB 0% 13 KB
1-accessibility-yarra-bend-1920x1124.jpg 57 KB 0% 11 KB
2-kayaking-gippsland-lakes-coastal-park-2910x1124.jpg 55 KB 0% 15 KB
1-dog-walking-albert-park-1920x1124.jpg 53 KB 0% 15 KB
group-walking-gresswell-forest-1920x1124.jpg 49 KB 0% 10 KB
1-lookout-masons-falls-kinglake-national-park-1920x1124.jpg 48 KB 0% 10 KB
2-camping-bunga-arm-gippsland-lakes-coastal-park-east-1920x1124.jpg 37 KB 0% 10 KB
junior-rangers-point-cook-marine-park-1920x1124.jpg 35 KB 0% 9 KB
Subset large font files10 KB0.003g

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
opensans-bold.woff ~21 KB ~4 KB
opensans-semibold.woff ~21 KB ~4 KB
opensans.woff ~21 KB ~3 KB
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.
Timing3.2 s1.0 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

Timing11.9 s2.0 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.

Timing720 ms190 ms
Cumulative Layout Shift

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

Speed Index

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

Timing11.0 s3.1 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.

Timing13.3 s4.5 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.

Timing300 ms130 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.

Timing3.2 s1.0 s
Eliminate render-blocking resources

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.

InsightPotential savings of 680 msPotential savings of 100 ms
Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

InsightPotential savings of 2,573 KiBPotential savings of 2,959 KiB
Reduce unused CSS

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.

InsightPotential savings of 280 KiBPotential savings of 281 KiB
Reduce unused JavaScript

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

InsightPotential savings of 808 KiBPotential savings of 1,683 KiB
Efficiently encode images

Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

InsightPotential savings of 1,973 KiBPotential savings of 1,973 KiB
Serve images in next-gen formats

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.

InsightPotential savings of 3,812 KiBPotential savings of 3,812 KiB
Enable text compression

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.

InsightPotential savings of 3 KiBPotential savings of 1,108 KiB
Initial server response time was short

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

InsightRoot document took 620 msRoot document took 550 ms
Avoid serving legacy JavaScript to modern browsers

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript

InsightPotential savings of 30 KiBPotential savings of 52 KiB
Avoid enormous network payloads

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

InsightTotal size was 20,358 KiBTotal size was 21,726 KiB
Serve static assets with an efficient cache policy

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

Insight73 resources found73 resources found
Avoids an excessive DOM size

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.

Insight827 elements792 elements
JavaScript execution time

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Timing1.9 s0.7 s
Minimizes main-thread work

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

Timing4.8 s1.8 s
Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.

Minimize third-party usage

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.

InsightThird-party code blocked the main thread for 520 msThird-party code blocked the main thread for 150 ms
Uses passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.

Image elements do not have explicit width and height

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions