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
58%
Desktop Performance
80%

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 Paint5.7 s2.4 s< 2.5 s
First Input Delay210 ms40 ms< 100ms
Cumulative Layout Shift0.0160.011 0.1

Tracking scripts

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

googletagmanager.com 2 138 KB
connect.facebook.net 2 138 KB
googleads.g.doubleclick.net 1 2 KB
google.com 1 620 B
google-analytics.com 3 21 KB
clarity.ms 2 25 KB
stats.g.doubleclick.net 1 569 B
facebook.com 3 1 KB
z.clarity.ms 3 882 B
c.clarity.ms 2 2 KB
c.bing.com 1 1 KB

Opportunities

Replace inlined font files

There are 10 inlined fonts that should converted to subresources.

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
Score64%99%
Timing2.6 s0.6 s

Largest Contentful Paint

MobileDesktop
Score17%49%
Timing5.7 s2.4 s

Total Blocking Time

MobileDesktop
Score69%100%
Timing390 ms0 ms

Speed Index

MobileDesktop
Score13%24%
Timing9.1 s3.1 s

Time to Interactive

MobileDesktop
Score7%100%
Timing15.3 s0.6 s

Max Potential First Input Delay

MobileDesktop
Score63%100%
Timing210 ms40 ms

First Meaningful Paint

MobileDesktop
Score85%99%
Timing2.6 s0.6 s

Eliminate render-blocking resources

MobileDesktop
Score46%93%
InsightPotential savings of 1,080 msPotential savings of 90 ms

Properly size images

MobileDesktop
Score100%97%
InsightPotential savings of 39 KiB

Minify CSS

MobileDesktop
Score58%97%
InsightPotential savings of 52 KiBPotential savings of 52 KiB

Minify JavaScript

MobileDesktop
Score75%100%
InsightPotential savings of 13 KiBPotential savings of 13 KiB

Reduce unused CSS

MobileDesktop
Score34%80%
InsightPotential savings of 412 KiBPotential savings of 266 KiB

Reduce unused JavaScript

MobileDesktop
Score0%48%
InsightPotential savings of 1,059 KiBPotential savings of 1,059 KiB

Enable text compression

MobileDesktop
Score0%46%
InsightPotential savings of 1,118 KiBPotential savings of 1,118 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 2,710 msRoot document took 1,970 ms

Avoid serving legacy JavaScript to modern browsers

MobileDesktop
Score88%93%
InsightPotential savings of 43 KiBPotential savings of 43 KiB

Avoids enormous network payloads

MobileDesktop
Score91%91%
InsightTotal size was 2,584 KiBTotal size was 2,585 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score30%30%
Insight10 resources found10 resources found

Avoid an excessive DOM size

MobileDesktop
Score82%82%
Insight945 elements945 elements

JavaScript execution time

MobileDesktop
Score74%100%
Timing2.1 s0.4 s

Minimizes main-thread work

MobileDesktop
Score29%97%
Timing5.4 s1.4 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Minimize third-party usage

MobileDesktop
GradeFailPass
InsightThird-party code blocked the main thread for 260 msThird-party code blocked the main thread for 0 ms

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail