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
20%
Desktop Performance
52%

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.

Pass or fail?

MobileFail
DesktopFail

CWV Breakdown

VitalMobileDesktopTarget
Largest Contentful Paint10.4 s1.4 s< 2.5 s
First Input Delay2,220 ms750 ms< 100ms
Cumulative Layout Shift0.2950.133 0.1

Tracking scripts

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

View details
googletagmanager.com 5 467 KB
secure.leadforensics.com 3 13 KB
google-analytics.com 7 22 KB
js.adsrvr.org 2 4 KB
google.com 2 620 B
9358165.fls.doubleclick.net 2 2 KB
googleads.g.doubleclick.net 1 2 KB
stats.g.doubleclick.net 2 1 KB
snap.licdn.com 2 9 KB
cdn.linkedin.oribi.io 1 465 B
px.ads.linkedin.com 3 3 KB
linkedin.com 1 4 KB
insight.adsrvr.org 1 433 B
match.adsrvr.org 3 3 KB
pixel.rubiconproject.com 1 959 B
cm.g.doubleclick.net 1 779 B
ups.analytics.yahoo.com 3 2 KB

Opportunities

Remove autoplaying or preloaded media files9 videos7.4 MB1.7g CO2

By removing 9 autoplaying or preloaded videos, roughly 7.4 MB could be removed from the page load.

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

View details
3ef5ab36.mp4 4 MB 31%
3ef5ab36.mp4 3 MB 23%
7d491177.mp4 308 KB 3%
7d491177.mp4 259 KB 2%
81c9bf81.mp4 250 KB 2%
7d491177.mp4 223 KB 2%
830f5260.mp4 75 KB 1%
6cc18177.mp4 52 KB 0%
6229ceab.mp4 52 KB 0%
Optimise images34 KB0.008g

By optimising the following images, roughly 34 KB could be removed from the transfer size, about 0%. This would reduce the CO2 generated per page load from 2.64g grams to 2.63 grams.

Images should be optimised for the web for several reasons:

  1. Reduced file size: Optimizing images can result in a smaller file size, which can help to reduce the amount of data that needs to be downloaded. This can lead to faster page load times and improved performance.
  2. Improved user experience: Optimising images can help to improve the overall user experience, as pages with optimised images load faster and are more responsive.
  3. Lower emissions: Optimising images can help to reduce the emissions associated with data transfer, as less data needs to be transmitted over the network.
  4. Better accessibility: Optimising images can make them more accessible to users with slower connections or limited data plans.
View details
image 279 KB 2% 34 KB
Subset large font files124 KB0.028g

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.

View details
Inter-Regular.woff2 ~97 KB ~80 KB
FoundersGrotesk-Medium.woff2 ~33 KB ~16 KB
FoundersGrotesk-Regular.woff2 ~32 KB ~15 KB
FoundersGrotesk-RegularItalic.woff2 ~32 KB ~14 KB
Largest Contentful Paint

Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric

MobileDesktop
Score0%83%
Timing10.4 s1.4 s
Total Blocking Time

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.

MobileDesktop
Score0%0%
Timing7,100 ms2,260 ms
Cumulative Layout Shift

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.

MobileDesktop
Score40%81%
Timing0.2950.133
Speed Index

Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.

MobileDesktop
Score3%7%
Timing12.5 s4.3 s
Time to Interactive

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

MobileDesktop
Score0%27%
Timing24.6 s6.0 s
Max Potential First Input Delay

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

MobileDesktop
Score0%1%
Timing2,220 ms750 ms
First Meaningful Paint

First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

MobileDesktop
Score32%86%
Timing4.8 s1.0 s
Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

MobileDesktop
Score12%72%
InsightPotential savings of 778 KiBPotential savings of 1,352 KiB
Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.

MobileDesktop
Score78%100%
InsightPotential savings of 89 KiBPotential savings of 84 KiB
Reduce unused CSS

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

MobileDesktop
Score55%41%
InsightPotential savings of 148 KiBPotential savings of 148 KiB
Reduce unused JavaScript

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

MobileDesktop
Score12%33%
InsightPotential savings of 692 KiBPotential savings of 692 KiB
Reduce initial server response time

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

MobileDesktop
GradeFailFail
InsightRoot document took 670 msRoot document took 660 ms
Avoid enormous network payloads

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

MobileDesktop
Score2%0%
InsightTotal size was 7,451 KiBTotal size was 11,802 KiB
Serve static assets with an efficient cache policy

A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.

MobileDesktop
Score26%27%
Insight32 resources found32 resources found
Avoid an excessive DOM size

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.

MobileDesktop
Score33%33%
Insight1,683 elements1,671 elements
Reduce JavaScript execution time

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

MobileDesktop
Score7%38%
Timing10.6 s4.4 s
Minimize main-thread work

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

MobileDesktop
Score0%10%
Timing16.2 s7.9 s
Reduce the impact of third-party code

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.

MobileDesktop
GradeFailFail
InsightThird-party code blocked the main thread for 2,730 msThird-party code blocked the main thread for 820 ms
Some third-party resources can be lazy loaded with a facade

Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.

MobileDesktop
GradeFailFail
Insight1 facade alternative available1 facade alternative available
Does not use passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.

MobileDesktop
GradeFailFail