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
90%
Desktop Performance
99%

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 Paint2.8 s0.8 s< 2.5 s
First Input Delay30 ms20 ms< 100ms
Cumulative Layout Shift00 0.1

Opportunities

Remove autoplaying or preloaded media files

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

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

Col-show.mp4 6 MB 93%

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.svg0 B
icomoon.woff22 KB
fontawesome-webfont.woff266 KB

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
cdn.colliercreative.com.aufontawesome-webfont.svg
cdn.colliercreative.com.auicomoon.woff
fonts.gstatic.compe0qMImSLYBIv1o4X1M8cce9I9s.woff2
use.typekit.netl
use.typekit.netl
use.typekit.netl
cdn.colliercreative.com.aufontawesome-webfont.woff2
fonts.gstatic.compe0qMImSLYBIv1o4X1M8cce9I9tAcVwo.woff2

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
Score57%96%
Timing2.8 s0.8 s

Largest Contentful Paint

MobileDesktop
Score83%98%
Timing2.8 s0.8 s

Speed Index

MobileDesktop
Score93%98%
Timing3.1 s0.9 s

Time to Interactive

MobileDesktop
Score97%100%
Timing2.8 s0.8 s

First Meaningful Paint

MobileDesktop
Score80%96%
Timing2.8 s0.8 s

Properly size images

MobileDesktop
Score100%93%
InsightPotential savings of 123 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 790 msRoot document took 770 ms

Preload Largest Contentful Paint image

MobileDesktop
Score0%100%

Avoid enormous network payloads

MobileDesktop
Score10%8%
InsightTotal size was 5,964 KiBTotal size was 6,119 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score10%9%
Insight7 resources found9 resources found

Avoids an excessive DOM size

MobileDesktop
Score99%99%
Insight486 elements486 elements

Minimizes main-thread work

MobileDesktop
Score99%100%
Timing1.2 s0.4 s

Largest Contentful Paint image was not lazily loaded

MobileDesktop
GradeFailPass