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.6 s3.0 s< 2.5 s
First Input Delay140 ms30 ms< 100ms
Cumulative Layout Shift0.8670.139 0.1

Tracking scripts

All the tracking scripts on the site generated ~208 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 21 KB 2 138 KB 1 48 KB 1 569 B 2 656 B


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.

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.9 s1.9 s

Largest Contentful Paint

Timing10.6 s3.0 s

Total Blocking Time

Timing160 ms0 ms

Cumulative Layout Shift


Speed Index

Timing9.8 s3.7 s

Time to Interactive

Timing10.9 s1.9 s

Max Potential First Input Delay

Timing140 ms30 ms

First Meaningful Paint

Timing7.9 s1.9 s

Eliminate render-blocking resources

InsightPotential savings of 7,790 msPotential savings of 2,080 ms

Minify CSS

InsightPotential savings of 36 KiBPotential savings of 36 KiB

Minify JavaScript

InsightPotential savings of 77 KiBPotential savings of 77 KiB

Reduce unused CSS

InsightPotential savings of 62 KiBPotential savings of 15 KiB

Reduce unused JavaScript

InsightPotential savings of 586 KiBPotential savings of 586 KiB

Efficiently encode images

InsightPotential savings of 86 KiBPotential savings of 92 KiB

Serve images in next-gen formats

InsightPotential savings of 312 KiBPotential savings of 388 KiB

Enable text compression

InsightPotential savings of 553 KiBPotential savings of 553 KiB

Reduce initial server response time

InsightRoot document took 1,110 msRoot document took 1,080 ms

Serve static assets with an efficient cache policy

Insight41 resources found39 resources found

Avoid an excessive DOM size

Insight939 elements939 elements

JavaScript execution time

Timing1.1 s0.2 s

Minimizes main-thread work

Timing2.3 s0.8 s

All text remains visible during webfont loads


Does not use passive listeners to improve scrolling performance


Image elements do not have explicit width and height