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
35%
Desktop Performance
62%

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 Paint15.4 s3.0 s< 2.5 s
First Input Delay600 ms250 ms< 100ms
Cumulative Layout Shift0.0570.023 0.1

Tracking scripts

All the tracking scripts on the site generated ~184 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 162 KB
in.hotjar.com 1 407 B
google-analytics.com 4 20 KB
stats.g.doubleclick.net 2 570 B
google.com 1 557 B
analytics.google.com 1 0 B

Opportunities

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.

VIC-Medium.7792938.woff2 ~27 KB ~9 KB
VIC-Bold.6690f57.woff2 ~26 KB ~9 KB
VIC-Regular.0d446b7.woff2 ~26 KB ~9 KB
VIC-SemiBold.0a0482a.woff2 ~25 KB ~8 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
Score48%94%
Timing3.1 s0.8 s

Largest Contentful Paint

MobileDesktop
Score0%34%
Timing15.4 s3.0 s

Total Blocking Time

MobileDesktop
Score19%63%
Timing1,270 ms280 ms

Cumulative Layout Shift

MobileDesktop
Score98%100%
Timing0.0570.023

Speed Index

MobileDesktop
Score2%4%
Timing12.9 s4.9 s

Time to Interactive

MobileDesktop
Score9%83%
Timing14.5 s2.8 s

Max Potential First Input Delay

MobileDesktop
Score4%50%
Timing600 ms250 ms

First Meaningful Paint

MobileDesktop
Score73%94%
Timing3.1 s0.8 s

Properly size images

MobileDesktop
Score34%77%
InsightPotential savings of 413 KiBPotential savings of 346 KiB

Defer offscreen images

MobileDesktop
Score67%100%
InsightPotential savings of 66 KiB

Reduce unused JavaScript

MobileDesktop
Score38%72%
InsightPotential savings of 314 KiBPotential savings of 311 KiB

Efficiently encode images

MobileDesktop
Score29%100%
InsightPotential savings of 534 KiB

Serve images in next-gen formats

MobileDesktop
Score16%87%
InsightPotential savings of 795 KiBPotential savings of 188 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 3,280 msRoot document took 3,730 ms

Avoids enormous network payloads

MobileDesktop
Score93%99%
InsightTotal size was 2,467 KiBTotal size was 1,867 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score38%51%
Insight19 resources found20 resources found

Avoid an excessive DOM size

MobileDesktop
Score100%57%
Insight441 elements1,298 elements

JavaScript execution time

MobileDesktop
Score59%96%
Timing2.9 s0.9 s

Minimizes main-thread work

MobileDesktop
Score38%95%
Timing4.7 s1.6 s

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail