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
89%

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 Paint3.8 s1.2 s< 2.5 s
First Input Delay440 ms40 ms< 100ms
Cumulative Layout Shift00.099 0.1

Tracking scripts

All the tracking scripts on the site generated ~84 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 1 84 KB
google-analytics.com 1 0 B

Opportunities

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
Score34%97%
Timing3.5 s0.7 s

Largest Contentful Paint

MobileDesktop
Score56%89%
Timing3.8 s1.2 s

Total Blocking Time

MobileDesktop
Score18%100%
Timing1,300 ms0 ms

Cumulative Layout Shift

MobileDesktop
Score100%90%
Timing00.099

Speed Index

MobileDesktop
Score23%44%
Timing7.8 s2.4 s

Time to Interactive

MobileDesktop
Score60%100%
Timing6.4 s0.7 s

Max Potential First Input Delay

MobileDesktop
Score13%100%
Timing440 ms40 ms

First Meaningful Paint

MobileDesktop
Score62%97%
Timing3.5 s0.7 s

Properly size images

MobileDesktop
Score100%93%
InsightPotential savings of 8 KiBPotential savings of 52 KiB

Reduce unused JavaScript

MobileDesktop
Score49%87%
InsightPotential savings of 157 KiBPotential savings of 157 KiB

Efficiently encode images

MobileDesktop
Score67%90%
InsightPotential savings of 120 KiBPotential savings of 120 KiB

Serve images in next-gen formats

MobileDesktop
Score66%77%
InsightPotential savings of 247 KiBPotential savings of 226 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 1,290 msRoot document took 1,190 ms

Preload Largest Contentful Paint image

MobileDesktop
Score0%100%

Serve static assets with an efficient cache policy

MobileDesktop
Score68%70%
Insight28 resources found31 resources found

Avoids an excessive DOM size

MobileDesktop
Score90%90%
Insight809 elements809 elements

JavaScript execution time

MobileDesktop
Score38%99%
Timing4.4 s0.5 s

Minimizes main-thread work

MobileDesktop
Score6%99%
Timing9.2 s1.1 s

Minimize third-party usage

MobileDesktop
GradeFailPass
InsightThird-party code blocked the main thread for 930 msThird-party code blocked the main thread for 0 ms

Largest Contentful Paint image was not lazily loaded

MobileDesktop
GradeFailPass