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
86%
Desktop Performance
96%

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.4 s0.6 s< 2.5 s
First Input Delay100 ms30 ms< 100ms
Cumulative Layout Shift0.2910.067 0.1

Tracking scripts

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

plausible.io 2 2 KB

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
ui.shld.begilroy-bold.woff2
ui.shld.begilroy-light.woff2
ui.shld.beadonis-bold.woff2
ui.shld.beadonis-regular.woff2

Speed Index

MobileDesktop
Score67%60%
Timing4.8 s2.0 s

Largest Contentful Paint

MobileDesktop
Score92%100%
Timing2.4 s0.6 s

Cumulative Layout Shift

MobileDesktop
Score41%97%
Timing0.2910.067

Max Potential First Input Delay

MobileDesktop
Score96%100%
Timing100 ms30 ms

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 1,430 msRoot document took 1,590 ms

Uses efficient cache policy on static assets

MobileDesktop
Score95%94%
Insight16 resources found22 resources found

Minimizes main-thread work

MobileDesktop
Score99%100%
Timing1.0 s0.3 s

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail