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

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 Paint12.1 s2.1 s< 2.5 s
First Input Delay2,490 ms240 ms< 100ms
Cumulative Layout Shift00 0.1

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.comHTxqL289NzCGg4MzN6KJ7eW6CYyF_jzx13E.woff2
use.typekit.netl
use.typekit.netl
use.typekit.netl
use.typekit.netl
use.typekit.netl
use.typekit.netl

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
Score23%86%
Timing4.0 s1.0 s

Largest Contentful Paint

MobileDesktop
Score0%59%
Timing12.1 s2.1 s

Total Blocking Time

MobileDesktop
Score1%83%
Timing3,820 ms190 ms

Speed Index

MobileDesktop
Score12%57%
Timing9.5 s2.1 s

Time to Interactive

MobileDesktop
Score15%95%
Timing12.3 s2.1 s

Max Potential First Input Delay

MobileDesktop
Score0%52%
Timing2,490 ms240 ms

First Meaningful Paint

MobileDesktop
Score49%86%
Timing4.0 s1.0 s

Eliminate render-blocking resources

MobileDesktop
Score46%86%
InsightPotential savings of 1,120 msPotential savings of 170 ms

Reduce unused CSS

MobileDesktop
Score67%93%
InsightPotential savings of 112 KiBPotential savings of 116 KiB

Reduce unused JavaScript

MobileDesktop
Score24%72%
InsightPotential savings of 580 KiBPotential savings of 492 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 790 msRoot document took 880 ms

Uses efficient cache policy on static assets

MobileDesktop
Score10%100%
Insight5 resources found3 resources found

JavaScript execution time

MobileDesktop
Score22%100%
Timing6.3 s0.4 s

Minimizes main-thread work

MobileDesktop
Score4%99%
Timing9.9 s1.0 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Minimize third-party usage

MobileDesktop
GradeFailPass
InsightThird-party code blocked the main thread for 5,660 msThird-party code blocked the main thread for 170 ms

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail