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 Paint4.2 s8.1 s< 2.5 s
First Input Delay710 ms800 ms< 100ms
Cumulative Layout Shift00.005 0.1

Tracking scripts

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

View details 1 4 KB 2 3 KB 34 25 KB 2 1 KB 3 2 KB 2 2 KB 4 3 KB 2 1 KB 1 630 B 1 1 KB 1 282 B 1 980 B 1 863 B 2 2 KB 1 993 B 2 2 KB 1 879 B 2 2 KB 1 475 B 1 689 B 2 2 KB 1 3 KB 1 774 B 1 906 B 4 2 KB 1 705 B 1 915 B 1 235 B 1 726 B 1 0 B 1 186 B 1 556 B 2 1 KB 1 445 B 1 0 B 4 4 KB 1 221 B 2 1 KB 2 1 KB 2 1 KB 1 626 B 2 1 KB 1 285 B


Assets that need text compression enabled5 KB0.001g

By enabling text compression on 1 items, , roughly 5.5 KB could be removed from the page load.

View details
pr 8 KB 5 KB
Optimise images1 MB0.292g

By optimising the following images, roughly 1 MB could be removed from the transfer size, about 29%. This would reduce the CO2 generated per page load from 1g grams to 0.7 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
A1b1E5SFy-L._SX3000_.jpg 1 MB 24% 820 KB
91z9IKrLsHL._SX1500_.jpg 583 KB 13% 464 KB
XCM_CUTTLE_1495399_270960_200x200_1X_en_au._CB577753139_.jpg 20 KB 0% 13 KB
51ul0byEB9L._AC_SY200_.jpg 16 KB 0% 8 KB
Subset large font files34 KB0.008g

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
ozb5-CLHQWI6Soc.woff2 ~29 KB ~12 KB
Dv1WQ5DdeMS5qP7.woff2 ~28 KB ~10 KB
KwhNPG8Jz-Vz2X7.woff2 ~24 KB ~7 KB
VjTR4RqBzY0mUYx.woff2 ~22 KB ~4 KB
WOnTLzkiaEccV7F.woff2 ~18 KB ~846 B
2SazJx$EeTHfhMN.woff2 ~18 KB ~283 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.
View details pDxWAF1pBB0dzGB.woff2 KFPk-9IF4FqAqY-.woff2 Dv1WQ5DdeMS5qP7.woff2 VjTR4RqBzY0mUYx.woff2 WOnTLzkiaEccV7F.woff2 2SazJx$EeTHfhMN.woff2 ozb5-CLHQWI6Soc.woff2 KwhNPG8Jz-Vz2X7.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.
Timing3.6 s1.1 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

Timing4.2 s8.1 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.

Timing2,110 ms4,700 ms
Speed Index

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

Timing7.9 s6.5 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.5 s10.9 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.

Timing710 ms800 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.

Timing3.6 s1.1 s
Eliminate render-blocking resources

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.

InsightPotential savings of 30 ms
Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

InsightPotential savings of 399 KiBPotential savings of 1,462 KiB
Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.

InsightPotential savings of 868 KiBPotential savings of 1,905 KiB
Reduce unused JavaScript

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

InsightPotential savings of 128 KiBPotential savings of 139 KiB
Efficiently encode images

Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

InsightPotential savings of 78 KiBPotential savings of 631 KiB
Serve images in next-gen formats

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.

InsightPotential savings of 549 KiBPotential savings of 1,147 KiB
Avoid enormous network payloads

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

InsightTotal size was 2,444 KiBTotal size was 4,458 KiB
Uses efficient cache policy on static assets

A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.

Insight17 resources found36 resources found
Avoid an excessive DOM size

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.

Insight1,111 elements1,656 elements
Reduce JavaScript execution time

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Timing7.3 s7.6 s
Minimize main-thread work

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Timing12.1 s14.4 s
Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.

Reduce the impact of third-party code

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.

InsightThird-party code blocked the main thread for 3,000 msThird-party code blocked the main thread for 2,830 ms
Does not use passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.

Image elements do not have explicit width and height

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

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

A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.