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
58%
Desktop Performance
74%

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.

VitalMobileDesktopTarget
Largest Contentful Paint13.4 s3.8 s< 2.5 s
First Input Delay230 ms100 ms< 100ms
Cumulative Layout Shift0.090.06 0.1

Tracking scripts

All the tracking scripts on the site generated ~65 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.

googletagmanager.com 1 44 KB
google-analytics.com 2 21 KB

Opportunities

Optimise images

By optimising the following images, roughly 4 MB could be removed from the transfer size, about 59%. This would reduce the CO2 generated per page load from 1.66g grams to 0.69 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.
131023-A374-scaled.jpg 1 MB 19% 391 KB
131023-A374-scaled.jpg 1 MB 19% 391 KB
u3Bs5JOQ.jpeg-scaled.jpg 1 MB 19% 371 KB
u3Bs5JOQ.jpeg-scaled.jpg 1 MB 19% 371 KB
shutterstock_780604204.jpg 1 MB 18% 1,001 KB
Hunters-Hill-Logo_black.png 429 KB 7% 250 KB
P5210013-e1565654378215-scaled.jpg 360 KB 6% 158 KB
HuntersHillDraft-67-e1573181027848-scaled.jpg 338 KB 5% 94 KB
HuntersHill-35-e1565654276994.jpg 318 KB 5% 173 KB
Untitled-design-14.png 236 KB 4% 209 KB
Boronia-Park-project-milestone-500x334-1.jpg 196 KB 3% 169 KB
Planting-500x334-1.jpg 127 KB 2% 99 KB
Untitled-500-%C3%97-334-px.png 85 KB 1% 58 KB
ANZAC-Web-Event.png 56 KB 1% 29 KB

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.

Raleway-Bold.ttf ~82 KB ~64 KB
Raleway-Regular.ttf ~80 KB ~63 KB
Raleway-Medium.ttf ~79 KB ~61 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.

Fontformat
Raleway-Regular.ttfttf
Raleway-Medium.ttfttf
Raleway-Bold.ttfttf

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.
MobileDesktop
Score36%91%
Timing3.4 s0.9 s

Largest Contentful Paint

MobileDesktop
Score0%20%
Timing13.4 s3.8 s

Total Blocking Time

MobileDesktop
Score91%100%
Timing190 ms50 ms

Cumulative Layout Shift

MobileDesktop
Score92%98%
Timing0.090.06

Speed Index

MobileDesktop
Score38%50%
Timing6.5 s2.3 s

Time to Interactive

MobileDesktop
Score86%100%
Timing4.1 s1.0 s

Max Potential First Input Delay

MobileDesktop
Score58%96%
Timing230 ms100 ms

First Meaningful Paint

MobileDesktop
Score64%91%
Timing3.4 s0.9 s

Eliminate render-blocking resources

MobileDesktop
Score66%85%
InsightPotential savings of 470 msPotential savings of 190 ms

Properly size images

MobileDesktop
Score34%50%
InsightPotential savings of 414 KiBPotential savings of 984 KiB

Minify JavaScript

MobileDesktop
Score75%93%
InsightPotential savings of 40 KiBPotential savings of 40 KiB

Reduce unused JavaScript

MobileDesktop
Score61%93%
InsightPotential savings of 73 KiBPotential savings of 73 KiB

Efficiently encode images

MobileDesktop
Score0%48%
InsightPotential savings of 1,009 KiBPotential savings of 1,183 KiB

Serve images in next-gen formats

MobileDesktop
Score0%32%
InsightPotential savings of 3,014 KiBPotential savings of 2,907 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 1,710 msRoot document took 1,770 ms

Avoid enormous network payloads

MobileDesktop
Score6%6%
InsightTotal size was 6,428 KiBTotal size was 6,426 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score8%8%
Insight63 resources found62 resources found

Avoids an excessive DOM size

MobileDesktop
Score97%97%
Insight615 elements615 elements

JavaScript execution time

MobileDesktop
Score99%100%
Timing0.5 s0.1 s

Minimizes main-thread work

MobileDesktop
Score95%100%
Timing1.7 s0.6 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Does not use passive listeners to improve scrolling performance

MobileDesktop
GradeFailFail

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail