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.

Pass or fail?


CWV Breakdown

Largest Contentful Paint11.5 s5.0 s< 2.5 s
First Input Delay490 ms210 ms< 100ms
Cumulative Layout Shift0.7470.332 0.1


Optimise images2 MB0.356g

By optimising the following images, roughly 2 MB could be removed from the transfer size, about 43%. This would reduce the CO2 generated per page load from 0.83g grams to 0.48 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.
View details
amrFyKQRZFT85BLVS33Kvhi6JD6oBwLouWORyktT.jpg 369 KB 10% 125 KB
NSb461TwjNwuezxOTttaGPx6Bi33wyGDIcErHy31.jpg 327 KB 9% 118 KB
6rO0Xkpq04womEGWA2fKpKj6iIdshnZ8TJNO8dkS.jpg 301 KB 8% 102 KB
4tYWLEG6Pmz2DYm21QJY4Ayfy9MtjRKMhfgBotkJ.png 262 KB 7% 228 KB
YIGl4hRZk4jz1yNkvrZ1DcQohwUELiFzQHMSPrGC.png 254 KB 7% 112 KB
PlZlSULLxVUTGGbOQatNXYIIzjo9JxQxLF8ZeuAi.jpg 251 KB 7% 95 KB
k4w6I8wf8p8CRfPvxkaMwFrbRTWHJ1XiIYiFuGgJ.jpg 189 KB 5% 50 KB
Vqc9VRpwpJb4aLDcKpsKzRHiqaBz3OXFbBBX0L5W.png 181 KB 5% 145 KB
UFdWn1VNKkTSBqUTCiQxHu3YWHKlfjExo6uOznou.png 143 KB 4% 111 KB
Qhz10YIgCaUISTgoLilJxqISmBBcYFh2207Soarl.png 83 KB 2% 47 KB
XWo8tPmptCz0QJD442lTMD8aFtup9jjpeBPJxwB3.png 83 KB 2% 60 KB
1PXxHlPV0BaAFbZvzOsjH1Tri0i1zK1a4Xhwt7Sa.jpg 66 KB 2% 24 KB
2KjE7D4MODnzHU9MGND4AzqrDTNQvVMOoyeO1MAP.jpg 65 KB 2% 47 KB
jw70VpWtmWPCYTqEvLHlDUPNLFW4hezFEygbXuvQ.jpg 64 KB 2% 23 KB
psD2spthhhUjJ4k4ftaQB4YRKElseZt0fJApQCyP.jpg 64 KB 2% 24 KB
xzjRJLa0nGkZn2lr4jYXaCBzpVTtH02xYHff9azl.png 60 KB 2% 41 KB
COtLYFHiyZvedi0vs8ZdvHMCKQtMSKFOK8IHueCZ.jpg 55 KB 1% 22 KB
LBulsNPWb7ffTzqZNNwCH9HIx8kdZANO9zNCV5zH.jpg 54 KB 1% 19 KB
yQxY9N3awVfvf57GIX1LZGPMjHyhASROnqNwguNv.png 52 KB 1% 42 KB
Rs8J4JmiKL1LfjsyJlpgJvOfmVVTDhX6chLpP5iV.jpg 44 KB 1% 18 KB
qVEKsGb8U5aEOiR0h8sC3Q1EhDf3xfUVHVnHncQo.png 42 KB 1% 25 KB
cQMimuXWKGGjFkRmhkdQd5d84nNvmLvEAcXoSFgL.jpg 37 KB 1% 30 KB
f7hqpnpgDKOO5YC7yt8RNa5kAT7Ykjj8WT0MTFle.jpg 36 KB 1% 17 KB
NUMJlqQNAdzzIjWNXzzNdehkpj3e2hFa64JFMeXn.jpg 29 KB 1% 22 KB
bZSHEoBTYGKmIYprPQkOAX5lwpXig2J5usyXm1zb.png 25 KB 1% 16 KB
mzrYue0vRuVRM8t7aI0mIlYiREZj8rwGPzNBLgMq.png 17 KB 0% 11 KB
IVyYPZSwnn75V7CJ30fTkWJLAbnaId6Bw0fUbOq1.png 15 KB 0% 9 KB
sign-up-153cb60e.png 14 KB 0% 10 KB
Subset large font files14 KB0.003g

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.

View details
pe0TMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp7t1R-tQKr51.woff2 ~31 KB ~14 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.
View details pe0TMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp7t1R-tQKr51.woff2
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.
Timing5.8 s3.0 s
Largest Contentful Paint

Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric

Timing11.5 s5.0 s
Total Blocking Time

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.

Timing630 ms140 ms
Cumulative Layout Shift

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.

Speed Index

Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.

Timing13.2 s5.0 s
Time to Interactive

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Timing13.4 s4.7 s
Max Potential First Input Delay

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Timing490 ms210 ms
First Meaningful Paint

First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Timing5.8 s3.0 s