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
34%
Desktop Performance
72%

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 Paint9.6 s2.1 s< 2.5 s
First Input Delay1,200 ms230 ms< 100ms
Cumulative Layout Shift00 0.1

Tracking scripts

All the tracking scripts on the site generated ~642 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
assets.adobedtm.com 4 183 KB
googletagmanager.com 3 219 KB
js.adsrvr.org 2 4 KB
bat.bing.com 3 16 KB
connect.facebook.net 2 169 KB
googleads.g.doubleclick.net 1 2 KB
google.com 1 620 B
ad.doubleclick.net 2 2 KB
clarity.ms 2 21 KB
colesonline.sc.omtrdc.net 1 419 B
cm.everesttech.net 1 543 B
colessupermarketspty.tt.omtrdc.net 3 11 KB
m.clarity.ms 2 592 B
sync.mathtag.com 1 727 B
c.clarity.ms 2 2 KB
insight.adsrvr.org 1 597 B
match.adsrvr.org 5 3 KB
c.bing.com 1 1 KB
dpm.demdex.net 1 911 B
pixel.rubiconproject.com 1 959 B
tags.bluekai.com 1 794 B
cm.g.doubleclick.net 1 714 B
sync-tm.everesttech.net 2 1 KB
rtd.tubemogul.com 1 419 B
rtd-tm.everesttech.net 1 0 B

Opportunities

Subset large font files87 KB0.019g

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
ITCAvantGardeGothicW05-Bold.woff2 ~63 KB ~45 KB
AvantGardeGothicITCW05-Demi.woff2 ~59 KB ~42 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
Score91%100%
Timing1.7 s0.5 s
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%58%
Timing9.6 s2.1 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
Score1%75%
Timing4,140 ms220 ms
Speed Index

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

MobileDesktop
Score0%0%
Timing16.8 s6.6 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
Score8%66%
Timing15.0 s3.7 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%57%
Timing1,200 ms230 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
Score98%100%
Timing1.7 s0.5 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%56%
InsightPotential savings of 998 KiBPotential savings of 1,219 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
Score29%62%
InsightPotential savings of 400 KiBPotential savings of 447 KiB
Efficiently encode images

Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

MobileDesktop
Score43%89%
InsightPotential savings of 232 KiBPotential savings of 232 KiB
Serve images in next-gen formats

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.

MobileDesktop
Score9%56%
InsightPotential savings of 1,314 KiBPotential savings of 1,314 KiB
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
Score81%80%
InsightTotal size was 3,012 KiBTotal size was 3,051 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
Score1%1%
Insight52 resources found52 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
Score28%28%
Insight1,767 elements1,767 elements
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
Score21%94%
Timing6.5 s1.0 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
Score1%72%
Timing13.5 s2.9 s
Minimize third-party usage

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
GradeFailPass
InsightThird-party code blocked the main thread for 2,530 msThird-party code blocked the main thread for 130 ms
Image elements do not have explicit width and height

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

MobileDesktop
GradeFailFail