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
42%
Desktop Performance
83%

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 Paint10.2 s1.8 s< 2.5 s
First Input Delay1,010 ms250 ms< 100ms
Cumulative Layout Shift0.0280.017 0.1

Tracking scripts

All the tracking scripts on the site generated ~173 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 152 KB
in.hotjar.com 1 407 B
content.hotjar.io 1 205 B
google-analytics.com 2 20 KB
stats.g.doubleclick.net 2 585 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

Largest Contentful Paint

MobileDesktop
Score0%70%
Timing10.2 s1.8 s

Total Blocking Time

MobileDesktop
Score12%80%
Timing1,600 ms200 ms

Speed Index

MobileDesktop
Score31%65%
Timing7.1 s1.9 s

Time to Interactive

MobileDesktop
Score22%97%
Timing10.8 s1.9 s

Max Potential First Input Delay

MobileDesktop
Score0%51%
Timing1,010 ms250 ms

Properly size images

MobileDesktop
Score74%90%
InsightPotential savings of 52 KiBPotential savings of 154 KiB

Reduce unused JavaScript

MobileDesktop
Score43%80%
InsightPotential savings of 326 KiBPotential savings of 329 KiB

Serve images in next-gen formats

MobileDesktop
Score58%100%
InsightPotential savings of 61 KiBPotential savings of 94 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 760 msRoot document took 990 ms

Serve static assets with an efficient cache policy

MobileDesktop
Score64%61%
Insight15 resources found15 resources found

JavaScript execution time

MobileDesktop
Score59%99%
Timing2.9 s0.6 s

Minimizes main-thread work

MobileDesktop
Score48%99%
Timing4.1 s1.0 s

Minimize third-party usage

MobileDesktop
GradeFailPass
InsightThird-party code blocked the main thread for 440 msThird-party code blocked the main thread for 20 ms

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail