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
8%
Desktop Performance
38%

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 Paint13.2 s3.7 s< 2.5 s
First Input Delay920 ms150 ms< 100ms
Cumulative Layout Shift1.0640.816 0.1

Tracking scripts

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

connect.facebook.net 4 356 KB
google-analytics.com 2 21 KB
stats.g.doubleclick.net 1 575 B
google.com 1 557 B
facebook.com 6 984 B
fresnel.vimeocdn.com 5 0 B
player-telemetry.vimeo.com 2 0 B

Opportunities

Remove autoplaying or preloaded media files

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

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

segment-1.m4s 1 MB 19%
07371c9c.mp4 256 KB 3%
889a3fbb.mp4 2 KB 0%
acc22f74.mp4 2 KB 0%

Optimise images

By optimising the following images, roughly 2 MB could be removed from the transfer size, about 26%. This would reduce the CO2 generated per page load from 1.69g grams to 1.25 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.
046e38b6-ff5d-eb87-df15-d981db18c01e.jpg 1 MB 20% 979 KB
046e38b6-ff5d-eb87-df15-d981db18c01e.jpg 1 MB 20% 979 KB

Replace icon font files

Font icons can have a negative impact on performance and emissions because they can increase the size of the page and the amount of data that needs to be downloaded. Some specific reasons why font icons can be bad for performance and emissions include:

  1. Increased file size: Font icons are typically included as part of a web font, which can be a large file that needs to be downloaded. This can increase the overall size of the page, leading to slower load times and higher emissions.
  2. Inefficient rendering: Web fonts are sometimes loaded and rendered inefficiently, which can result in slow performance and higher emissions.
  3. Unused icons: Font icons often include a large number of icons that may not be used on a particular page, increasing the file size and leading to inefficient use of resources.

While icon fonts are still widely used on the web, and they can be a useful tool for adding icons to a website. it is a dated practice when there are better options such as SVG icons, which can be more efficient and have a lower impact on performance and emissions.

FontSize
fontawesome-webfont.woff277 KB
fontawesome-webfont.woff276 KB
fontawesome-webfont.woff276 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.

cabin_i4.d842691f340f784c85693accd3cc7aaa6af9102a.woff2 ~24 KB ~6 KB
cabin_n4.90cfc8efed7ff88f02d58b22d38933ec75887560.woff2 ~24 KB ~6 KB
cabin_n7.3703a1f5733b06a58cf91470aca19cfd07978070.woff2 ~23 KB ~6 KB
glyphicons-halflings-regular.woff2 ~19 KB ~961 B

Remove third party font files

Font files should be loaded from the same hosting as the website because

  1. Increased loading time: Third-party sub-resources, such as scripts, fonts, or images, need to be downloaded from a separate server before they can be displayed on the website. This can increase the overall loading time of the page, leading to a slower user experience.
  2. Dependence on external servers: The loading of third-party subresources is dependent on the availability and performance of the external servers that host them. If these servers are slow or unavailable, it can result in slow page loading times or even errors.
  3. Increased risk of security threats: Third-party subresources can introduce security risks to a website, as they can contain malicious code or be used to track user activity.
HostFont
fonts.shopifycdn.comcabin_n4.90cfc8efed7ff88f02d58b22d38933ec75887560.woff2
cdn.shopify.comfontawesome-webfont.woff2
fonts.shopifycdn.comcabin_n7.3703a1f5733b06a58cf91470aca19cfd07978070.woff2
fonts.gstatic.comesDR31xSG-6AGleN2tWkkJUEGpA.woff2
assets.reviews.ioreviewsio-font.woff2
fonts.shopifycdn.comcabin_i4.d842691f340f784c85693accd3cc7aaa6af9102a.woff2
d1azc1qln24ryf.cloudfront.netrevsglobal-pr-mod.woff2
cdnjs.cloudflare.comfontawesome-webfont.woff2
maxcdn.bootstrapcdn.comfontawesome-webfont.woff2
maxcdn.bootstrapcdn.comglyphicons-halflings-regular.woff2

Replace jQuery and jQuery libraries with more modern code

jQuery is a popular and widely-used JavaScript library that simplifies web development by providing a set of tools and functions to interact with HTML documents, handle events, create animations, and make asynchronous HTTP requests.

In the past, jQuery was a very popular choice for web development because it simplified many common tasks and provided a consistent and cross-browser-compatible API. However, with the advancement of modern web technologies and improvements in browser capabilities, the need for jQuery has decreased.

Many modern web frameworks and libraries, such as React and Angular, provide their own set of tools for handling common tasks and interacting with the DOM, making jQuery less necessary in many cases. The Javascript engine in modern browsers have also become more consistent in the feature implementations often eliminating the need for a library like jQuery.

jQuery represents an opportunity because:

  1. Performance: While jQuery is a powerful and useful library, it can slow down website performance due to its large size and complex code. Modern browsers have also improved their native support for many of the features that jQuery provides, reducing the need for it.
  2. Maintainability: jQuery code can be difficult to maintain and update, particularly as web technologies evolve and change. This can make it harder for developers to keep up with best practices and standards for web development.
  3. Accessibility: Some jQuery plugins and features can create accessibility issues, particularly for users who rely on assistive technologies. This can make it harder for people with disabilities to use and access websites.
jquery.fancybox.js 23 KB
jquery.min.js 31 KB
jquery.min.js 31 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
Score55%97%
Timing2.8 s0.7 s

Largest Contentful Paint

MobileDesktop
Score0%20%
Timing13.2 s3.7 s

Total Blocking Time

MobileDesktop
Score2%73%
Timing3,120 ms230 ms

Cumulative Layout Shift

MobileDesktop
Score2%4%
Timing1.0640.816

Speed Index

MobileDesktop
Score11%5%
Timing9.5 s4.6 s

Time to Interactive

MobileDesktop
Score0%39%
Timing25.5 s5.1 s

Max Potential First Input Delay

MobileDesktop
Score0%84%
Timing920 ms150 ms

First Meaningful Paint

MobileDesktop
Score58%97%
Timing3.6 s0.7 s

Properly size images

MobileDesktop
Score29%74%
InsightPotential savings of 446 KiBPotential savings of 373 KiB

Defer offscreen images

MobileDesktop
Score46%91%
InsightPotential savings of 150 KiBPotential savings of 260 KiB

Minify CSS

MobileDesktop
Score88%100%
InsightPotential savings of 8 KiBPotential savings of 8 KiB

Minify JavaScript

MobileDesktop
Score100%95%
InsightPotential savings of 21 KiBPotential savings of 21 KiB

Reduce unused CSS

MobileDesktop
Score58%83%
InsightPotential savings of 99 KiBPotential savings of 113 KiB

Reduce unused JavaScript

MobileDesktop
Score9%54%
InsightPotential savings of 804 KiBPotential savings of 800 KiB

Efficiently encode images

MobileDesktop
Score36%74%
InsightPotential savings of 363 KiBPotential savings of 363 KiB

Serve images in next-gen formats

MobileDesktop
Score2%50%
InsightPotential savings of 979 KiBPotential savings of 979 KiB

Enable text compression

MobileDesktop
Score0%45%
InsightPotential savings of 389 KiBPotential savings of 389 KiB

Initial server response time was short

MobileDesktop
GradeFailPass
InsightRoot document took 740 msRoot document took 560 ms

Avoid enormous network payloads

MobileDesktop
Score5%2%
InsightTotal size was 6,679 KiBTotal size was 7,547 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score1%1%
Insight44 resources found44 resources found

Avoid an excessive DOM size

MobileDesktop
Score0%0%
Insight4,141 elements4,170 elements

Reduce JavaScript execution time

MobileDesktop
Score24%89%
Timing6.0 s1.3 s

Minimize main-thread work

MobileDesktop
Score1%51%
Timing13.3 s3.9 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Minimize third-party usage

MobileDesktop
GradeFailPass
InsightThird-party code blocked the main thread for 2,930 msThird-party code blocked the main thread for 200 ms

Some third-party resources can be lazy loaded with a facade

MobileDesktop
GradeFailFail
Insight1 facade alternative available1 facade alternative available

Does not use passive listeners to improve scrolling performance

MobileDesktop
GradeFailFail

Avoid document.write()

MobileDesktop
GradeFailFail

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail