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
50%
Desktop Performance
55%

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 Paint23.0 s4.4 s< 2.5 s
First Input Delay270 ms210 ms< 100ms
Cumulative Layout Shift0.0870.213 0.1

Tracking scripts

All the tracking scripts on the site generated ~453 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
googletagmanager.com 3 334 KB
secure-ds.serving-sys.com 1 0 B
connect.facebook.net 2 87 KB
google-analytics.com 2 22 KB
analytics.google.com 1 814 B
stats.g.doubleclick.net 1 0 B
td.doubleclick.net 2 2 KB
google.com 1 0 B
10826750.fls.doubleclick.net 2 2 KB
ad.doubleclick.net 1 3 KB
googleads.g.doubleclick.net 1 890 B
static.doubleclick.net 1 749 B
facebook.com 1 447 B
play.google.com 4 0 B

Opportunities

Assets that need text compression enabled7 KB0.002g

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

View details
message.js 10 KB 7 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.
View details
fonts.gstatic.com KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
fonts.gstatic.com KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
fonts.gstatic.com KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
fonts.gstatic.com KFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
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%13%
Timing23.0 s4.4 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
Score52%81%
Timing570 ms190 ms
Cumulative Layout Shift

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.

MobileDesktop
Score93%58%
Timing0.0870.213
Speed Index

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

MobileDesktop
Score16%25%
Timing8.8 s3.1 s
Layout shift culprits

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

MobileDesktop
Score0%0%
Optimize DOM size

A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size.

MobileDesktop
Score0%100%
LCP request discovery

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

MobileDesktop
Score0%0%
Third parties

Third party code can significantly impact load performance. Reduce and defer loading of third party code to prioritize your page's content.

MobileDesktop
Score0%0%
Optimize viewport for mobile

Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.

MobileDesktop
Score0%100%
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%47%
Timing24.6 s4.6 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
Score45%65%
Timing270 ms210 ms