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 Paint5.4 s1.9 s< 2.5 s
First Input Delay360 ms360 ms< 100ms
Cumulative Layout Shift0.0350.112 0.1

Tracking scripts

All the tracking scripts on the site generated ~184 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 153 KB 4 21 KB 1 5 KB 1 457 B 3 3 KB 1 2 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.

free-fa-brands-400.woff276 KB
free-fa-regular-400.woff214 KB
free-fa-solid-900.woff277 KB

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

Time to Interactive

Timing10.7 s2.8 s

Speed Index

Timing9.0 s3.5 s

Total Blocking Time

Timing670 ms340 ms

Largest Contentful Paint

Timing5.4 s1.9 s

Cumulative Layout Shift


Max Potential First Input Delay

Timing360 ms360 ms

First Meaningful Paint

Timing2.7 s0.6 s

Eliminate render-blocking resources

InsightPotential savings of 1,650 msPotential savings of 350 ms

Properly size images

InsightPotential savings of 10 KiBPotential savings of 52 KiB

Defer offscreen images

InsightPotential savings of 63 KiB

Reduce unused CSS

InsightPotential savings of 125 KiBPotential savings of 118 KiB

Reduce unused JavaScript

InsightPotential savings of 178 KiBPotential savings of 151 KiB

Enable text compression

InsightPotential savings of 14 KiBPotential savings of 14 KiB

Reduce initial server response time

InsightRoot document took 1,670 msRoot document took 1,750 ms

Serve static assets with an efficient cache policy

Insight7 resources found7 resources found

Avoids an excessive DOM size

Insight521 elements521 elements

JavaScript execution time

Timing2.5 s1.0 s

Minimizes main-thread work

Timing4.5 s1.7 s

Ensure text remains visible during webfont load


Reduce the impact of third-party code

InsightThird-party code blocked the main thread for 840 msThird-party code blocked the main thread for 400 ms

Image elements do not have explicit width and height