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 Paint10.8 s2.9 s< 2.5 s
First Input Delay970 ms460 ms< 100ms
Cumulative Layout Shift0.0360.022 0.1


Optimise images

By optimising the following images, roughly 1,013 KB could be removed from the transfer size, about 32%. This would reduce the CO2 generated per page load from 0.81g grams to 0.55 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
LBES_background_web-v2.jpg 897 KB 29% 194 KB
LBES_background_web-v2.jpg 897 KB 29% 194 KB
Pure_Tour_Background.jpg 272 KB 9% 191 KB
PF_Header_Logo.png 237 KB 8% 178 KB
Home_Page_Mobile_Image.jpg 121 KB 4% 61 KB
Mobile+Community+Logos.png 105 KB 3% 65 KB
White+Shape+Cut+Top.png 49 KB 2% 32 KB
Free%2BRange%2BEggs%2BSign.png 46 KB 1% 11 KB
Pure_Tour_Logo.png 35 KB 1% 22 KB
Community+Logo+1.png 29 KB 1% 20 KB
Community+Logo+5.png 22 KB 1% 12 KB
Service+Icon+-+Milling.png 19 KB 1% 13 KB
Button-Y-IMG.png 17 KB 1% 11 KB
Community+Logo+4.png 15 KB 0% 9 KB

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.

View details
Typekit: l ~27 KB ~9 KB
Typekit: l ~20 KB ~3 KB
Typekit: l ~20 KB ~2 KB
Typekit: l ~19 KB ~2 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 l l l l l l l l l l l l

Replace jQuery and jQuery libraries with more modern code

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.
View details
jquery.min.js 30 KB

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.
Timing7.6 s2.0 s

Largest Contentful Paint

Timing10.8 s2.9 s

Total Blocking Time

Timing640 ms280 ms

Speed Index

Timing11.0 s2.8 s

Time to Interactive

Timing12.5 s2.7 s

Max Potential First Input Delay

Timing970 ms460 ms

First Meaningful Paint

Timing7.8 s2.1 s

Eliminate render-blocking resources

InsightPotential savings of 5,530 msPotential savings of 1,390 ms

Properly size images

InsightPotential savings of 347 KiBPotential savings of 309 KiB

Defer offscreen images

InsightPotential savings of 242 KiB

Reduce unused JavaScript

InsightPotential savings of 497 KiBPotential savings of 496 KiB

Efficiently encode images

InsightPotential savings of 99 KiBPotential savings of 99 KiB

Serve images in next-gen formats

InsightPotential savings of 771 KiBPotential savings of 820 KiB

Reduce initial server response time

InsightRoot document took 1,160 msRoot document took 980 ms

Preload Largest Contentful Paint image

InsightPotential savings of 1,080 msPotential savings of 550 ms

Avoid enormous network payloads

InsightTotal size was 2,620 KiBTotal size was 3,137 KiB

Serve static assets with an efficient cache policy

Insight17 resources found17 resources found

Avoids an excessive DOM size

Insight477 elements511 elements

JavaScript execution time

Timing2.6 s1.0 s

Minimizes main-thread work

Timing4.2 s2.0 s

Ensure text remains visible during webfont load


Reduce the impact of third-party code

InsightThird-party code blocked the main thread for 1,380 msThird-party code blocked the main thread for 390 ms

Image elements do not have explicit width and height