Insights

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
32%
Desktop Performance
79%

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.

VitalMobileDesktopTarget
Largest Contentful Paint8.1 s2.4 s< 2.5 s
First Input Delay800 ms120 ms< 100ms
Cumulative Layout Shift0.0020.001 0.1

Tracking scripts

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

google-analytics.com 2 21 KB
js-agent.newrelic.com 11 35 KB
bam.nr-data.net 2 944 B

Opportunities

Remove autoplaying or preloaded media files

By removing 1 autoplaying or preloaded videos, roughly 5.4 KB could be removed from the page load.

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

beep.mp3 5 KB 0%

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.
HostFont
fonts.gstatic.comKFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
fonts.gstatic.comKFOlCnqEu92Fr1MmWUlfBBc4AMP6lQ.woff2

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.
jquery.min.js 34 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.
MobileDesktop
Score34%90%
Timing3.5 s0.9 s

Largest Contentful Paint

MobileDesktop
Score2%49%
Timing8.1 s2.4 s

Total Blocking Time

MobileDesktop
Score3%99%
Timing2,780 ms60 ms

Speed Index

MobileDesktop
Score22%32%
Timing8.0 s2.8 s

Time to Interactive

MobileDesktop
Score10%80%
Timing13.8 s3.0 s

Max Potential First Input Delay

MobileDesktop
Score1%92%
Timing800 ms120 ms

First Meaningful Paint

MobileDesktop
Score62%90%
Timing3.5 s0.9 s

Eliminate render-blocking resources

MobileDesktop
Score43%83%
InsightPotential savings of 1,370 msPotential savings of 200 ms

Properly size images

MobileDesktop
Score88%100%
InsightPotential savings of 63 KiBPotential savings of 65 KiB

Defer offscreen images

MobileDesktop
Score39%100%
InsightPotential savings of 512 KiBPotential savings of 76 KiB

Reduce unused CSS

MobileDesktop
Score75%100%
InsightPotential savings of 66 KiBPotential savings of 14 KiB

Reduce unused JavaScript

MobileDesktop
Score38%83%
InsightPotential savings of 482 KiBPotential savings of 481 KiB

Serve images in next-gen formats

MobileDesktop
Score39%80%
InsightPotential savings of 400 KiBPotential savings of 309 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 1,150 msRoot document took 1,090 ms

Avoids enormous network payloads

MobileDesktop
Score98%99%
InsightTotal size was 2,016 KiBTotal size was 1,993 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score8%9%
Insight61 resources found60 resources found

Avoid an excessive DOM size

MobileDesktop
Score68%73%
Insight1,148 elements1,076 elements

JavaScript execution time

MobileDesktop
Score17%97%
Timing7.3 s0.8 s

Minimizes main-thread work

MobileDesktop
Score4%96%
Timing10.2 s1.5 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Minimize third-party usage

MobileDesktop
GradeFailPass
InsightThird-party code blocked the main thread for 940 msThird-party code blocked the main thread for 10 ms

Does not use passive listeners to improve scrolling performance

MobileDesktop
GradeFailFail

Avoid document.write()

MobileDesktop
GradeFailFail

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail