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 Paint3.0 s1.7 s< 2.5 s
First Input Delay460 ms100 ms< 100ms
Cumulative Layout Shift00 0.1

Tracking scripts

All the tracking scripts on the site generated ~83 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. 3 4 KB 1 9 KB 36 24 KB 2 1 KB 4 3 KB 1 722 B 1 904 B 2 2 KB 2 1 KB 1 726 B 3 2 KB 2 775 B 1 639 B 1 186 B 1 1 KB 2 1 KB 1 1 KB 1 444 B 1 282 B 1 992 B 1 887 B 2 2 KB 1 993 B 2 2 KB 2 1 KB 1 866 B 4 4 KB 1 221 B 2 1 KB 4 2 KB 2 2 KB 2 1 KB 2 1 KB 1 689 B 2 2 KB 1 3 KB 1 800 B 1 611 B 2 1 KB 1 508 B 1 0 B


Remove autoplaying or preloaded media files

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

This would reduce the page transfer size by 31% and reduce the pages emissions from 0.99 grams of CO2 to 0.69 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.

A1CebqMttoL.mp4 1 MB 31%
A1CebqMttoL.mp4 0 B 0%

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.

ozb5-CLHQWI6Soc.woff2 ~29 KB ~12 KB
Dv1WQ5DdeMS5qP7.woff2 ~28 KB ~10 KB
KwhNPG8Jz-Vz2X7.woff2 ~23 KB ~6 KB
VjTR4RqBzY0mUYx.woff2 ~22 KB ~4 KB
WOnTLzkiaEccV7F.woff2 ~18 KB ~171 B
2SazJx$EeTHfhMN.woff2 ~18 KB ~48 B

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.

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.9 s0.7 s

Largest Contentful Paint

Timing3.0 s1.7 s

Total Blocking Time

Timing670 ms20 ms

Speed Index

Timing6.9 s1.5 s

Time to Interactive

Timing13.2 s2.1 s

Max Potential First Input Delay

Timing460 ms100 ms

First Meaningful Paint

Timing2.9 s0.7 s

Properly size images

InsightPotential savings of 354 KiBPotential savings of 740 KiB

Defer offscreen images

InsightPotential savings of 611 KiBPotential savings of 248 KiB

Reduce unused JavaScript

InsightPotential savings of 163 KiBPotential savings of 193 KiB

Efficiently encode images

InsightPotential savings of 39 KiBPotential savings of 110 KiB

Serve images in next-gen formats

InsightPotential savings of 271 KiBPotential savings of 619 KiB

Enable text compression

InsightPotential savings of 5 KiBPotential savings of 5 KiB

Reduce initial server response time

InsightRoot document took 830 msRoot document took 610 ms

Avoid enormous network payloads

InsightTotal size was 5,348 KiBTotal size was 4,450 KiB

Uses efficient cache policy on static assets

Insight25 resources found19 resources found

Avoid an excessive DOM size

Insight1,065 elements1,689 elements

JavaScript execution time

Timing5.1 s0.7 s

Minimize main-thread work

Timing12.7 s2.1 s

Ensure text remains visible during webfont load


Minimize third-party usage

InsightThird-party code blocked the main thread for 1,970 msThird-party code blocked the main thread for 50 ms

Does not use passive listeners to improve scrolling performance


Avoid document.write()


Image elements do not have explicit width and height


Does not have a <meta name="viewport"> tag with width or initial-scale