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
81%
Desktop Performance
91%

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.0 s1.4 s< 2.5 s
First Input Delay140 ms40 ms< 100ms
Cumulative Layout Shift0.1330.046 0.1

Opportunities

Optimise images

By optimising the following images, roughly 45 KB could be removed from the transfer size, about 6%. This would reduce the CO2 generated per page load from 0.17g grams to 0.16 grams.

Images should be optimised for the web for several reasons:

  1. Reduced file size: Optimizing images can result in a smaller file size, which can help to reduce the amount of data that needs to be downloaded. This can lead to faster page load times and improved performance.
  2. Improved user experience: Optimising images can help to improve the overall user experience, as pages with optimised images load faster and are more responsive.
  3. Lower emissions: Optimising images can help to reduce the emissions associated with data transfer, as less data needs to be transmitted over the network.
  4. Better accessibility: Optimising images can make them more accessible to users with slower connections or limited data plans.
banner.png 276 KB 36% 32 KB

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
Score95%100%
Timing1.6 s0.5 s

Largest Contentful Paint

MobileDesktop
Score79%85%
Timing3.0 s1.4 s

Total Blocking Time

MobileDesktop
Score85%100%
Timing240 ms0 ms

Cumulative Layout Shift

MobileDesktop
Score81%99%
Timing0.1330.046

Speed Index

MobileDesktop
Score58%53%
Timing5.3 s2.2 s

Time to Interactive

MobileDesktop
Score78%100%
Timing4.9 s0.5 s

Max Potential First Input Delay

MobileDesktop
Score86%100%
Timing140 ms40 ms

First Meaningful Paint

MobileDesktop
Score99%100%
Timing1.6 s0.5 s

Eliminate render-blocking resources

MobileDesktop
Score55%86%
InsightPotential savings of 660 msPotential savings of 160 ms

Reduce unused CSS

MobileDesktop
Score75%97%
InsightPotential savings of 60 KiBPotential savings of 53 KiB

Reduce unused JavaScript

MobileDesktop
Score45%90%
InsightPotential savings of 177 KiBPotential savings of 154 KiB

Serve images in next-gen formats

MobileDesktop
Score100%87%
InsightPotential savings of 13 KiBPotential savings of 282 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 1,770 msRoot document took 1,810 ms

Preload Largest Contentful Paint image

MobileDesktop
Score0%100%

Serve static assets with an efficient cache policy

MobileDesktop
Score86%74%
Insight8 resources found9 resources found

JavaScript execution time

MobileDesktop
Score96%100%
Timing0.9 s0.2 s

Minimizes main-thread work

MobileDesktop
Score78%100%
Timing2.6 s0.8 s

Largest Contentful Paint image was not lazily loaded

MobileDesktop
GradeFailPass

Uses passive listeners to improve scrolling performance

MobileDesktop
GradeFailPass

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail