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
54%
Desktop Performance
29%

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 Paint1.6 s5.2 s< 2.5 s
First Input Delay1,250 ms370 ms< 100ms
Cumulative Layout Shift0.1530.248 0.1

Tracking scripts

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

googletagmanager.com 3 179 KB
google-analytics.com 4 65 KB
secure-ds.serving-sys.com 2 23 KB
connect.facebook.net 2 137 KB
10826750.fls.doubleclick.net 2 2 KB
googleads.g.doubleclick.net 8 7 KB
static.doubleclick.net 4 3 KB
facebook.com 2 328 B
stats.g.doubleclick.net 1 586 B
google.com 1 557 B

Opportunities

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.gstatic.comKFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
fonts.gstatic.comKFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
fonts.gstatic.comKFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
fonts.gstatic.comKFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
fonts.gstatic.comKFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
fonts.gstatic.comKFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
fonts.gstatic.comKFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
fonts.gstatic.comKFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2

Largest Contentful Paint

MobileDesktop
Score99%7%
Timing1.6 s5.2 s

Total Blocking Time

MobileDesktop
Score0%11%
Timing6,880 ms770 ms

Cumulative Layout Shift

MobileDesktop
Score75%50%
Timing0.1530.248

Speed Index

MobileDesktop
Score0%10%
Timing15.5 s4.0 s

Time to Interactive

MobileDesktop
Score0%21%
Timing33.8 s6.6 s

Max Potential First Input Delay

MobileDesktop
Score0%22%
Timing1,250 ms370 ms

Eliminate render-blocking resources

MobileDesktop
Score97%100%
InsightPotential savings of 40 msPotential savings of 0 ms

Properly size images

MobileDesktop
Score100%97%
InsightPotential savings of 43 KiB

Defer offscreen images

MobileDesktop
Score46%100%
InsightPotential savings of 257 KiB

Reduce unused CSS

MobileDesktop
Score45%83%
InsightPotential savings of 69 KiBPotential savings of 64 KiB

Reduce unused JavaScript

MobileDesktop
Score0%21%
InsightPotential savings of 2,403 KiBPotential savings of 2,393 KiB

Serve images in next-gen formats

MobileDesktop
Score75%93%
InsightPotential savings of 103 KiBPotential savings of 137 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 1,880 msRoot document took 1,990 ms

Preload Largest Contentful Paint image

MobileDesktop
Score0%100%

Avoid enormous network payloads

MobileDesktop
Score26%25%
InsightTotal size was 4,857 KiBTotal size was 4,946 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score12%9%
Insight18 resources found19 resources found

Avoids an excessive DOM size

MobileDesktop
Score94%94%
Insight719 elements719 elements

Reduce JavaScript execution time

MobileDesktop
Score4%60%
Timing13.3 s2.8 s

Minimize main-thread work

MobileDesktop
Score0%49%
Timing17.5 s4.0 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Reduce the impact of third-party code

MobileDesktop
GradeFailFail
InsightThird-party code blocked the main thread for 8,950 msThird-party code blocked the main thread for 1,340 ms

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

MobileDesktop
GradeFailFail
Insight1 facade alternative available1 facade alternative available

Largest Contentful Paint image was not lazily loaded

MobileDesktop
GradeFailPass

Does not use passive listeners to improve scrolling performance

MobileDesktop
GradeFailFail

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail