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.

Largest Contentful Paint16.9 s3.5 s< 2.5 s
First Input Delay800 ms100 ms< 100ms
Cumulative Layout Shift0.0520.024 0.1

Tracking scripts

All the tracking scripts on the site generated ~146 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. 2 125 KB 3 21 KB


Optimise images

By optimising the following images, roughly 25 MB could be removed from the transfer size, about 105%. This would reduce the CO2 generated per page load from 5.37g grams to -0.29 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.
Turtle-300dpi.png 4 MB 15% 3 MB
Turtle-300dpi.png 4 MB 15% 3 MB
Cockatoo-300dpi.png 4 MB 15% 3 MB
Cockatoo-300dpi.png 4 MB 15% 3 MB
HarvestFoodTrail-1.png 3 MB 11% 2 MB
HarvestFoodTrail-1.png 3 MB 11% 2 MB
richmond-valley-sunrise.jpg 892 KB 4% 401 KB
richmond-valley-sunrise.jpg 892 KB 4% 401 KB
287354686_2185626338277245_6767863044447452594_n.jpg 834 KB 3% 529 KB
287354686_2185626338277245_6767863044447452594_n.jpg 834 KB 3% 529 KB
Top_Price_Bull.jpg 720 KB 3% 593 KB
DSC01673.jpg 700 KB 3% 586 KB
casino_river.jpg 644 KB 3% 261 KB
casino_river.jpg 644 KB 3% 261 KB
DSC_0140.jpg 549 KB 2% 201 KB
DSC_0140.jpg 549 KB 2% 201 KB
DSC_0137.jpg 546 KB 2% 202 KB
DSC_0137.jpg 546 KB 2% 202 KB
20220306_105048web.jpg 520 KB 2% 263 KB
20220306_105048web.jpg 520 KB 2% 263 KB
CasinoWTP_staff.jpg 494 KB 2% 181 KB
CasinoWTP_staff.jpg 494 KB 2% 181 KB
DSC_2101_1.jpg 468 KB 2% 164 KB
DSC_2101_1.jpg 468 KB 2% 164 KB
Ribbon_cutting.jpg 468 KB 2% 185 KB
Ribbon_cutting.jpg 468 KB 2% 185 KB
DSC_0468web.jpg 411 KB 2% 252 KB
casinofunrunlaunchweb.jpg 362 KB 2% 114 KB
casinofunrunlaunchweb.jpg 362 KB 2% 114 KB
SuperSunDayFunDaycoverphoto.jpg 289 KB 1% 122 KB
DSC6130small.jpg 283 KB 1% 230 KB
floodinquirythumb-1.jpg 279 KB 1% 133 KB
ecdev.jpg 275 KB 1% 90 KB
BarkerSt.jpg 262 KB 1% 155 KB
da.jpg 215 KB 1% 9 KB
truckshowthumbnail.jpg 177 KB 1% 105 KB
regionality.jpg 153 KB 1% 53 KB
Casino-industrial-site-Richmond-Valley-Regional-Job-Precinct2_0.jpg 150 KB 1% 55 KB
blazeaid_1.jpg 149 KB 1% 45 KB
reynoldsroadpromosmall.jpg 138 KB 1% 96 KB
305990582_511664127632304_5754693140178915294_n.png 104 KB 0% 74 KB
ecdevsmall.jpg 103 KB 0% 75 KB
placeplan.jpg 75 KB 0% 39 KB
planssmall.jpg 56 KB 0% 34 KB
logo.png 29 KB 0% 21 KB
t-icon-3.png 20 KB 0% 19 KB
icon-announcement.png 19 KB 0% 18 KB
t-icon-4.png 19 KB 0% 18 KB
areas-icon.png 18 KB 0% 18 KB
quick-links-icon.png 18 KB 0% 18 KB
t-icon-1.png 18 KB 0% 17 KB
DABC1093-E506-4850-82ED-7FB6D97E975A.jpeg 18 KB 0% 9 KB

Replace icon font files

Font icons can have a negative impact on performance and emissions because they can increase the size of the page and the amount of data that needs to be downloaded. Some specific reasons why font icons can be bad for performance and emissions include:

  1. Increased file size: Font icons are typically included as part of a web font, which can be a large file that needs to be downloaded. This can increase the overall size of the page, leading to slower load times and higher emissions.
  2. Inefficient rendering: Web fonts are sometimes loaded and rendered inefficiently, which can result in slow performance and higher emissions.
  3. Unused icons: Font icons often include a large number of icons that may not be used on a particular page, increasing the file size and leading to inefficient use of resources.

While icon fonts are still widely used on the web, and they can be a useful tool for adding icons to a website. it is a dated practice when there are better options such as SVG icons, which can be more efficient and have a lower impact on performance and emissions.

fa-solid-900.woff250 KB
fontawesome-webfont.woff276 KB
fa-regular-400.woff213 KB

Replace inlined font files

There are 1 inlined fonts that should converted to subresources.

Subset large font files

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.

AvenirNextLTPro-Bold.otf ~222 KB ~205 KB
AvenirNextLTPro-Demi.otf ~217 KB ~199 KB
AvenirNextLTPro-Regular.otf ~214 KB ~196 KB
AvenirNextLTPro-Medium.otf ~209 KB ~192 KB
x-font-woff;charset=utf-8;base64,d09GRgABAAAAAHvwAAsAAAAA3EgAAQAAAAAAAAAAAAAAAAAAAA ~31 KB ~13 KB

Convert font files to woff2

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.


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.

Replace jQuery and jQuery libraries with more modern code

jQuery is a popular and widely-used JavaScript library that simplifies web development by providing a set of tools and functions to interact with HTML documents, handle events, create animations, and make asynchronous HTTP requests.

In the past, jQuery was a very popular choice for web development because it simplified many common tasks and provided a consistent and cross-browser-compatible API. However, with the advancement of modern web technologies and improvements in browser capabilities, the need for jQuery has decreased.

Many modern web frameworks and libraries, such as React and Angular, provide their own set of tools for handling common tasks and interacting with the DOM, making jQuery less necessary in many cases. The Javascript engine in modern browsers have also become more consistent in the feature implementations often eliminating the need for a library like jQuery.

jQuery represents an opportunity because:

  1. Performance: While jQuery is a powerful and useful library, it can slow down website performance due to its large size and complex code. Modern browsers have also improved their native support for many of the features that jQuery provides, reducing the need for it.
  2. Maintainability: jQuery code can be difficult to maintain and update, particularly as web technologies evolve and change. This can make it harder for developers to keep up with best practices and standards for web development.
  3. Accessibility: Some jQuery plugins and features can create accessibility issues, particularly for users who rely on assistive technologies. This can make it harder for people with disabilities to use and access websites.

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.
Timing7.1 s2.2 s

Largest Contentful Paint

Timing16.9 s3.5 s

Total Blocking Time

Timing1,730 ms90 ms

Cumulative Layout Shift


Speed Index

Timing27.2 s8.6 s

Time to Interactive

Timing25.8 s6.5 s

Max Potential First Input Delay

Timing800 ms100 ms

First Meaningful Paint

Timing7.1 s2.2 s

Eliminate render-blocking resources

InsightPotential savings of 6,290 msPotential savings of 1,670 ms

Defer offscreen images

InsightPotential savings of 282 KiB

Minify JavaScript

InsightPotential savings of 155 KiBPotential savings of 155 KiB

Reduce unused CSS

InsightPotential savings of 112 KiBPotential savings of 91 KiB

Reduce unused JavaScript

InsightPotential savings of 616 KiBPotential savings of 625 KiB

Efficiently encode images

InsightPotential savings of 1,317 KiBPotential savings of 2,074 KiB

Serve images in next-gen formats

InsightPotential savings of 6,699 KiBPotential savings of 14,098 KiB

Reduce initial server response time

InsightRoot document took 1,790 msRoot document took 2,240 ms

Avoid multiple page redirects

InsightPotential savings of 1,110 msPotential savings of 340 ms

Avoid enormous network payloads

InsightTotal size was 15,053 KiBTotal size was 24,023 KiB

Serve static assets with an efficient cache policy

Insight118 resources found125 resources found

Avoid an excessive DOM size

Insight2,255 elements2,201 elements

JavaScript execution time

Timing4.3 s0.7 s

Minimize main-thread work

Timing11.2 s2.5 s

Ensure text remains visible during webfont load


Minimize third-party usage

InsightThird-party code blocked the main thread for 750 msThird-party code blocked the main thread for 20 ms

Does not use passive listeners to improve scrolling performance


Image elements do not have explicit width and height