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
30%
Desktop Performance
44%

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.3 s2.7 s< 2.5 s
First Input Delay1,320 ms570 ms< 100ms
Cumulative Layout Shift0.0020.001 0.1

Tracking scripts

All the tracking scripts on the site generated ~508 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
googleoptimize.com 1 50 KB
googletagmanager.com 2 193 KB
10880935.fls.doubleclick.net 4 5 KB
connect.facebook.net 2 170 KB
vc.hotjar.io 1 339 B
facebook.com 2 656 B
snap.licdn.com 2 9 KB
google-analytics.com 3 21 KB
amplify.outbrain.com 1 7 KB
cdn.taboola.com 3 29 KB
s.yimg.com 2 8 KB
analytics.google.com 1 0 B
stats.g.doubleclick.net 2 577 B
tr.outbrain.com 2 220 B
ave.outbrain.com 1 442 B
google.com 1 557 B
cdn.linkedin.oribi.io 1 470 B
px.ads.linkedin.com 3 3 KB
trc.taboola.com 1 3 KB
sp.analytics.yahoo.com 1 928 B
pips.taboola.com 1 331 B
cds.taboola.com 1 123 B
linkedin.com 1 4 KB
trc-events.taboola.com 2 1 KB

Opportunities

Assets that need text compression enabled604 KB0.156g

By enabling text compression on 10 items, , roughly 603.6 KB could be removed from the page load.

View details
menu_link_content 87 KB 78 KB
menu_link_content 86 KB 77 KB
menu_link_content 85 KB 77 KB
menu_link_content 85 KB 77 KB
menu_link_content 84 KB 76 KB
menu_link_content 84 KB 76 KB
menu_link_content 83 KB 75 KB
menu_link_content 51 KB 46 KB
sites 16 KB 14 KB
menu_link_content 8 KB 7 KB
Optimise images330 KB0.085g

By optimising the following images, roughly 330 KB could be removed from the transfer size, about 10%. This would reduce the CO2 generated per page load from 0.86g grams to 0.77 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
Subset large font files31 KB0.008g

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
VIC-Medium.7792938.woff2 ~26 KB ~8 KB
VIC-Bold.6690f57.woff2 ~26 KB ~8 KB
VIC-Regular.0d446b7.woff2 ~25 KB ~8 KB
VIC-SemiBold.0a0482a.woff2 ~25 KB ~7 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
Score30%48%
Timing3.7 s1.6 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
Score1%41%
Timing9.3 s2.7 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%3%
Timing4,240 ms1,130 ms
Speed Index

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

MobileDesktop
Score13%31%
Timing9.2 s2.8 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%16%
Timing24.5 s7.1 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%5%
Timing1,320 ms570 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
Score57%48%
Timing3.7 s1.6 s
Eliminate render-blocking resources

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.

MobileDesktop
Score46%81%
InsightPotential savings of 1,070 msPotential savings of 260 ms
Properly size images

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

MobileDesktop
Score63%100%
InsightPotential savings of 171 KiBPotential savings of 401 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
Score33%100%
InsightPotential savings of 433 KiBPotential savings of 107 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
Score18%48%
InsightPotential savings of 525 KiBPotential savings of 524 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
Score52%75%
InsightPotential savings of 262 KiBPotential savings of 330 KiB
Enable text compression

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.

MobileDesktop
Score13%32%
InsightPotential savings of 604 KiBPotential savings of 604 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
Score76%72%
InsightTotal size was 3,168 KiBTotal size was 3,319 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
Score22%21%
Insight34 resources found35 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
Score97%21%
Insight642 elements1,945 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
Score19%58%
Timing6.8 s3.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
Score2%36%
Timing12.0 s4.8 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 930 msThird-party code blocked the main thread for 290 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