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 Paint16.4 s2.7 s< 2.5 s
First Input Delay420 ms170 ms< 100ms
Cumulative Layout Shift0.2810.25 0.1

Tracking scripts

All the tracking scripts on the site generated ~95 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 95 KB 1 401 B 5 0 B 2 0 B


Remove autoplaying or preloaded media files4 videos5.2 MB1.37g CO2

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

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

View details
segment-1.m4s 3 MB 24%
segment-2.m4s 2 MB 16%
segment-1.m4s 793 KB 7%
segment-1.m4s 233 KB 2%
Assets that need text compression enabled3 MB0.738g

By enabling text compression on 81 items, , roughly 2.8 MB could be removed from the page load.

View details
frontend.min.css 448 KB 406 KB
global.css 234 KB 224 KB
jet-elements.css 229 KB 208 KB
/ 219 KB 190 KB
frontend.min.css 197 KB 173 KB
blog-layouts-module.css 147 KB 136 KB
woo-module.css 102 KB 92 KB
jet-search.css 86 KB 78 KB
public.css 83 KB 77 KB
theme.css 70 KB 60 KB
tippy-bundle.js 78 KB 59 KB
vue.min.js 91 KB 58 KB
jquery.min.js 86 KB 56 KB
custom-jet-blocks.css 61 KB 55 KB
selectWoo.full.min.js 76 KB 55 KB
jet-elements.min.js 77 KB 53 KB
jet-search.js 61 KB 49 KB
frontend-modules.min.js 66 KB 48 KB
fontawesome.min.css 57 KB 44 KB
all.min.css 56 KB 44 KB
jet-menu-public-scripts.js 52 KB 41 KB
elements-handlers.min.js 41 KB 31 KB
jet-tabs-frontend.css 33 KB 29 KB
frontend.min.js 39 KB 27 KB
wp-polyfill.min.js 38 KB 24 KB
jet-tricks-frontend.css 27 KB 23 KB
font-awesome.min.css 30 KB 23 KB
jet-tricks-frontend.js 30 KB 23 KB
style.css 27 KB 22 KB
v4-shims.min.css 26 KB 22 KB
chosen.jquery.min.js 28 KB 22 KB
photoswipe.min.js 31 KB 19 KB
frontend.min.js 24 KB 18 KB
jet-blocks.min.js 21 KB 16 KB
animations.min.css 18 KB 16 KB
elementor-icons.min.css 19 KB 15 KB
style.css 19 KB 15 KB
jquery.flexslider.min.js 21 KB 15 KB
post-147.css 17 KB 15 KB
jet-tabs-frontend.min.js 20 KB 15 KB
jet-elements-skin.css 17 KB 14 KB
dwf.js 20 KB 14 KB
core.min.js 21 KB 14 KB
popperjs.js 18 KB 12 KB
swiper.min.css 16 KB 12 KB
underscore.min.js 18 KB 11 KB
wc-blocks.css 12 KB 10 KB
add-to-cart-variation.min.js 13 KB 10 KB
sourcebuster.min.js 14 KB 10 KB
waypoints.min.js 12 KB 9 KB
index.js 13 KB 9 KB
jquery-migrate.min.js 13 KB 9 KB
index.js 11 KB 8 KB
chosen.min.css 10 KB 8 KB
widgets-scripts.js 11 KB 8 KB
post-37.css 8 KB 7 KB
dialog.min.js 11 KB 7 KB
wc-memberships-blocks.min.css 8 KB 7 KB
general.min.js 10 KB 6 KB
jquery.blockUI.min.js 9 KB 6 KB
photoswipe-ui-default.min.js 10 KB 6 KB
default-skin.min.css 8 KB 6 KB
wp-polyfill-inert.min.js 8 KB 6 KB
i18n.min.js 9 KB 5 KB
post-9277.css 5 KB 4 KB
single-product.min.js 6 KB 4 KB
jet-plugins.js 6 KB 4 KB
regenerator-runtime.min.js 6 KB 4 KB
wc-memberships-blocks-common.min.js 6 KB 4 KB
imagesloaded.min.js 5 KB 4 KB
theme-script.js 5 KB 4 KB
wc-memberships-frontend.min.css 4 KB 3 KB
webpack-pro.runtime.min.js 6 KB 3 KB
general.min.css 4 KB 3 KB
webpack.runtime.min.js 5 KB 3 KB
index.js 4 KB 3 KB
hooks.min.js 4 KB 3 KB
photoswipe.min.css 3 KB 2 KB
add-to-cart.min.js 3 KB 2 KB
styles.css 3 KB 2 KB
jquery.zoom.min.js 3 KB 1 KB
Optimise images462 KB0.119g

By optimising the following images, roughly 462 KB could be removed from the transfer size, about 4%. This would reduce the CO2 generated per page load from 2.78g grams to 2.66 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.
Replace icon font files77 KB0.02g

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.

View details
fa-solid-900.woff2 77 KB
Subset large font files17 KB0.004g

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
BngMUXZYTXPIvIBgJJSb6ufN5qWr4xCC.woff2 ~34 KB ~17 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 KFOlCnqEu92Fr1MmSU5fBBc4AMP6lQ.woff2 BngMUXZYTXPIvIBgJJSb6ufN5qWr4xCC.woff2 KFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2 KFOlCnqEu92Fr1MmYUtfBBc4AMP6lQ.woff2 KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2 KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
Replace jQuery and jQuery libraries with more modern code183 KB0.05g

jQuery is a popular and widely-used JavaScript library that simplifies web development by providing a set of tools and functions to interact with HTML documents, handle events, create animations, and make asynchronous HTTP requests.

In the past, jQuery was a very popular choice for web development because it simplified many common tasks and provided a consistent and cross-browser-compatible API. However, with the advancement of modern web technologies and improvements in browser capabilities, the need for jQuery has decreased.

Many modern web frameworks and libraries, such as React and Angular, provide their own set of tools for handling common tasks and interacting with the DOM, making jQuery less necessary in many cases. The Javascript engine in modern browsers have also become more consistent in the feature implementations often eliminating the need for a library like jQuery.

jQuery represents an opportunity because:

  1. Performance: While jQuery is a powerful and useful library, it can slow down website performance due to its large size and complex code. Modern browsers have also improved their native support for many of the features that jQuery provides, reducing the need for it.
  2. Maintainability: jQuery code can be difficult to maintain and update, particularly as web technologies evolve and change. This can make it harder for developers to keep up with best practices and standards for web development.
  3. Accessibility: Some jQuery plugins and features can create accessibility issues, particularly for users who rely on assistive technologies. This can make it harder for people with disabilities to use and access websites.
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.
Timing14.7 s2.5 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

Timing16.4 s2.7 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.

Timing1,060 ms350 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.

Timing15.1 s6.3 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.

Timing25.6 s6.1 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.

Timing420 ms170 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.

Timing14.7 s2.5 s