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
36%
Desktop Performance
65%

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 Paint5.0 s0.5 s< 2.5 s
First Input Delay580 ms110 ms< 100ms
Cumulative Layout Shift11.124 0.1

Opportunities

Replace inlined font files

There are 1 inlined fonts that should converted to subresources.

Subset large font files

Fonts should be subsetted to reduce the file size, improve performance, and reduce emissions. Subsetting a font involves removing any characters that are not needed for a particular use case, resulting in a smaller file size and faster page load times. Some specific reasons why fonts should be subsetted include:

  1. Reduced file size: Subsetting a font removes any unused characters, which can result in a smaller file size. This can help to reduce the amount of data that needs to be downloaded, leading to faster page load times and lower emissions.
  2. Improved performance: Fonts that are subsetted are faster to load and render than fonts that are not subsetted. This can help to improve the overall performance of a website, leading to a better user experience.

Overall, subsetting fonts is a good practice for anyone looking to optimize the performance and reduce the emissions of a website of a website.

x-font-ttf;charset=utf-8;base64,AAEAAAALAIAAAwAwT1MvMg8SDk4AAAC8AAAAYGNtYXBc+ChIAAA ~27 KB ~9 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
Score94%100%
Timing1.6 s0.5 s

Largest Contentful Paint

MobileDesktop
Score26%100%
Timing5.0 s0.5 s

Total Blocking Time

MobileDesktop
Score62%99%
Timing450 ms60 ms

Cumulative Layout Shift

MobileDesktop
Score2%1%
Timing11.124

Speed Index

MobileDesktop
Score7%5%
Timing10.7 s4.7 s

Time to Interactive

MobileDesktop
Score77%100%
Timing5.0 s1.2 s

Max Potential First Input Delay

MobileDesktop
Score4%93%
Timing580 ms110 ms

First Meaningful Paint

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

Eliminate render-blocking resources

MobileDesktop
Score51%85%
InsightPotential savings of 730 msPotential savings of 180 ms

Reduce unused CSS

MobileDesktop
Score75%93%
InsightPotential savings of 55 KiBPotential savings of 56 KiB

Reduce unused JavaScript

MobileDesktop
Score45%83%
InsightPotential savings of 235 KiBPotential savings of 239 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 1,650 msRoot document took 1,650 ms

Avoid serving legacy JavaScript to modern browsers

MobileDesktop
Score88%97%
InsightPotential savings of 9 KiBPotential savings of 9 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score78%82%
Insight5 resources found4 resources found

Avoid an excessive DOM size

MobileDesktop
Score59%60%
Insight1,261 elements1,256 elements

JavaScript execution time

MobileDesktop
Score92%100%
Timing1.2 s0.2 s

Minimizes main-thread work

MobileDesktop
Score87%100%
Timing2.2 s0.5 s

Does not use passive listeners to improve scrolling performance

MobileDesktop
GradeFailFail