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 Paint9.0 s2.6 s< 2.5 s
First Input Delay1,080 ms360 ms< 100ms
Cumulative Layout Shift0.0020.001 0.1

Tracking scripts

All the tracking scripts on the site generated ~417 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. 1 44 KB 2 173 KB 1 5 KB 4 4 KB 3 23 KB 2 139 KB 1 0 B 3 3 KB 2 656 B 1 2 KB 1 0 B 3 20 KB 2 577 B 1 0 B 1 557 B 1 1 KB


Optimise images

By optimising the following images, roughly 330 KB could be removed from the transfer size, about 13%. This would reduce the CO2 generated per page load from 0.64g grams to 0.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.

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.

VIC-Medium.7792938.woff2 ~25 KB ~7 KB
VIC-Bold.6690f57.woff2 ~25 KB ~7 KB
VIC-Regular.0d446b7.woff2 ~25 KB ~7 KB
VIC-SemiBold.0a0482a.woff2 ~24 KB ~6 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.
Timing2.7 s0.7 s

Largest Contentful Paint

Timing9.0 s2.6 s

Total Blocking Time

Timing1,980 ms410 ms

Speed Index

Timing8.8 s2.3 s

Time to Interactive

Timing16.7 s3.3 s

Max Potential First Input Delay

Timing1,080 ms360 ms

First Meaningful Paint

Timing2.7 s0.7 s

Eliminate render-blocking resources

InsightPotential savings of 1,020 msPotential savings of 280 ms

Properly size images

InsightPotential savings of 171 KiBPotential savings of 401 KiB

Defer offscreen images

InsightPotential savings of 539 KiBPotential savings of 107 KiB

Reduce unused JavaScript

InsightPotential savings of 496 KiBPotential savings of 499 KiB

Serve images in next-gen formats

InsightPotential savings of 262 KiBPotential savings of 330 KiB

Reduce initial server response time

InsightRoot document took 1,020 msRoot document took 1,040 ms

Avoids enormous network payloads

InsightTotal size was 2,409 KiBTotal size was 2,485 KiB

Serve static assets with an efficient cache policy

Insight29 resources found30 resources found

Avoid an excessive DOM size

Insight680 elements1,921 elements

JavaScript execution time

Timing4.4 s1.3 s

Minimize main-thread work

Timing7.3 s2.1 s

Minimize third-party usage

InsightThird-party code blocked the main thread for 450 msThird-party code blocked the main thread for 30 ms

Image elements do not have explicit width and height