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
99%
Desktop Performance
100%

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.8 s0.5 s< 2.5 s
First Input Delay780 ms20 ms< 100ms
Cumulative Layout Shift00 0.1

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

Largest Contentful Paint

MobileDesktop
Score98%100%
Timing1.8 s0.5 s

Speed Index

MobileDesktop
Score99%100%
Timing2.2 s0.7 s

Max Potential First Input Delay

MobileDesktop
Score1%100%
Timing780 ms20 ms

First Meaningful Paint

MobileDesktop
Score97%100%
Timing1.7 s0.5 s

Preload Largest Contentful Paint image

MobileDesktop
Score0%100%

Uses efficient cache policy on static assets

MobileDesktop
Score90%94%
Insight5 resources found5 resources found

Avoid an excessive DOM size

MobileDesktop
Score82%82%
Insight949 elements949 elements

Minimizes main-thread work

MobileDesktop
Score91%100%
Timing1.9 s0.5 s

Largest Contentful Paint image was not lazily loaded

MobileDesktop
GradeFailPass