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
64%
Desktop Performance
76%

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.8 s1.2 s< 2.5 s
First Input Delay190 ms40 ms< 100ms
Cumulative Layout Shift0.0030.368 0.1

Tracking scripts

All the tracking scripts on the site generated ~435 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 3 214 KB
google-analytics.com 4 21 KB
stats.g.doubleclick.net 1 579 B
connect.facebook.net 3 160 KB
snap.licdn.com 1 5 KB
clarity.ms 2 25 KB
google.com 1 557 B
cdn.linkedin.oribi.io 1 465 B
px.ads.linkedin.com 3 3 KB
facebook.com 2 328 B
linkedin.com 1 2 KB
q.clarity.ms 3 909 B
c.clarity.ms 2 2 KB
c.bing.com 1 1 KB

Opportunities

Remove autoplaying or preloaded media files

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

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

EmoteBakersVideo_01-1.mp4 767 KB 20%
header-top.mp4 721 KB 19%

Optimise images

By optimising the following images, roughly 993 KB could be removed from the transfer size, about 25%. This would reduce the CO2 generated per page load from 0.87g grams to 0.65 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.
fullwidth-SP.png 609 KB 16% 547 KB
suzuki-full.png 395 KB 10% 349 KB
woo-expert-gold-color.png 46 KB 1% 28 KB
banner-logo.png 40 KB 1% 10 KB
two-people-sharing-idea.jpeg 35 KB 1% 8 KB
banner-logo-mobile-r.png 30 KB 1% 17 KB
bigcommerce.png 26 KB 1% 17 KB
Partner-Main-Tile-2-e1675750269870.png 26 KB 1% 17 KB

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.

Apercu-Regular.woff ~28 KB ~11 KB
Apercu-Bold.woff ~28 KB ~10 KB
Apercu-Light.woff ~27 KB ~10 KB

Convert font files to woff2

WOFF2 is considered to be the best font format for web use because it provides a good balance of file size and compatibility. Some specific reasons why WOFF2 is a good font format include:

  1. Small file size: WOFF2 is a compressed font format, which means that it has a smaller file size compared to other font formats like TTF or OTF. This is important for web use because smaller file sizes can help to reduce the amount of data that needs to be downloaded, leading to faster page load times.
  2. High-quality font rendering: WOFF2 provides high-quality font rendering, making it a good choice for use on the web.

It’s worth noting that WOFF2 is not the only font format that can be used on the web, and there may be cases where other formats like WOFF or TTF are more suitable, depending on the specific requirements of the website. However, for most cases, WOFF2 is considered to be the best font format for web use due to its combination of small file size, good browser support, and high-quality font rendering.

Fontformat
Apercu-Light.woffwoff
Apercu-Regular.woffwoff
Apercu-Bold.woffwoff

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
Score92%100%
Timing1.7 s0.5 s

Largest Contentful Paint

MobileDesktop
Score15%89%
Timing5.8 s1.2 s

Total Blocking Time

MobileDesktop
Score67%100%
Timing410 ms0 ms

Cumulative Layout Shift

MobileDesktop
Score100%29%
Timing0.0030.368

Speed Index

MobileDesktop
Score55%68%
Timing5.5 s1.9 s

Time to Interactive

MobileDesktop
Score45%100%
Timing7.8 s0.7 s

Max Potential First Input Delay

MobileDesktop
Score69%100%
Timing190 ms40 ms

First Meaningful Paint

MobileDesktop
Score97%98%
Timing1.8 s0.7 s

Eliminate render-blocking resources

MobileDesktop
Score55%88%
InsightPotential savings of 660 msPotential savings of 150 ms

Properly size images

MobileDesktop
Score48%87%
InsightPotential savings of 191 KiBPotential savings of 162 KiB

Reduce unused CSS

MobileDesktop
Score88%93%
InsightPotential savings of 136 KiBPotential savings of 131 KiB

Reduce unused JavaScript

MobileDesktop
Score41%74%
InsightPotential savings of 240 KiBPotential savings of 296 KiB

Serve images in next-gen formats

MobileDesktop
Score0%49%
InsightPotential savings of 1,894 KiBPotential savings of 993 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 970 msRoot document took 970 ms

Use video formats for animated content

MobileDesktop
Score67%93%
InsightPotential savings of 103 KiBPotential savings of 103 KiB

Preload Largest Contentful Paint image

MobileDesktop
Score0%100%

Avoid enormous network payloads

MobileDesktop
Score28%53%
InsightTotal size was 4,780 KiBTotal size was 3,895 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score37%23%
Insight12 resources found19 resources found

JavaScript execution time

MobileDesktop
Score72%100%
Timing2.2 s0.4 s

Minimizes main-thread work

MobileDesktop
Score43%99%
Timing4.4 s1.0 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Minimize third-party usage

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

Largest Contentful Paint image was not lazily loaded

MobileDesktop
GradeFailPass

Avoid document.write()

MobileDesktop
GradePassFail

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail