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
14%
Desktop Performance
31%

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 Paint20.3 s4.9 s< 2.5 s
First Input Delay3,240 ms1,150 ms< 100ms
Cumulative Layout Shift0.2970.167 0.1

Opportunities

Replace jQuery and jQuery libraries with more modern code

jQuery is a popular and widely-used JavaScript library that simplifies web development by providing a set of tools and functions to interact with HTML documents, handle events, create animations, and make asynchronous HTTP requests.

In the past, jQuery was a very popular choice for web development because it simplified many common tasks and provided a consistent and cross-browser-compatible API. However, with the advancement of modern web technologies and improvements in browser capabilities, the need for jQuery has decreased.

Many modern web frameworks and libraries, such as React and Angular, provide their own set of tools for handling common tasks and interacting with the DOM, making jQuery less necessary in many cases. The Javascript engine in modern browsers have also become more consistent in the feature implementations often eliminating the need for a library like jQuery.

jQuery represents an opportunity because:

  1. Performance: While jQuery is a powerful and useful library, it can slow down website performance due to its large size and complex code. Modern browsers have also improved their native support for many of the features that jQuery provides, reducing the need for it.
  2. Maintainability: jQuery code can be difficult to maintain and update, particularly as web technologies evolve and change. This can make it harder for developers to keep up with best practices and standards for web development.
  3. Accessibility: Some jQuery plugins and features can create accessibility issues, particularly for users who rely on assistive technologies. This can make it harder for people with disabilities to use and access websites.
jquery-3.6.0.min.js 88 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
Score32%96%
Timing3.6 s0.8 s

Largest Contentful Paint

MobileDesktop
Score0%9%
Timing20.3 s4.9 s

Total Blocking Time

MobileDesktop
Score0%0%
Timing13,800 ms2,140 ms

Cumulative Layout Shift

MobileDesktop
Score40%71%
Timing0.2970.167

Speed Index

MobileDesktop
Score3%10%
Timing12.4 s4.0 s

Time to Interactive

MobileDesktop
Score0%17%
Timing31.5 s7.0 s

Max Potential First Input Delay

MobileDesktop
Score0%0%
Timing3,240 ms1,150 ms

First Meaningful Paint

MobileDesktop
Score60%96%
Timing3.6 s0.8 s

Eliminate render-blocking resources

MobileDesktop
Score39%75%
InsightPotential savings of 1,700 msPotential savings of 310 ms

Minify CSS

MobileDesktop
Score88%100%
InsightPotential savings of 16 KiBPotential savings of 16 KiB

Minify JavaScript

MobileDesktop
Score88%100%
InsightPotential savings of 36 KiBPotential savings of 36 KiB

Reduce unused CSS

MobileDesktop
Score67%97%
InsightPotential savings of 56 KiBPotential savings of 61 KiB

Reduce unused JavaScript

MobileDesktop
Score0%47%
InsightPotential savings of 909 KiBPotential savings of 910 KiB

Enable text compression

MobileDesktop
Score43%90%
InsightPotential savings of 236 KiBPotential savings of 236 KiB

Avoid serving legacy JavaScript to modern browsers

MobileDesktop
Score88%93%
InsightPotential savings of 73 KiBPotential savings of 73 KiB

Avoid enormous network payloads

MobileDesktop
Score75%39%
InsightTotal size was 3,229 KiBTotal size was 4,369 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score3%3%
Insight45 resources found45 resources found

Avoid an excessive DOM size

MobileDesktop
Score0%12%
Insight5,273 elements2,246 elements

Reduce JavaScript execution time

MobileDesktop
Score0%23%
Timing25.7 s6.2 s

Minimize main-thread work

MobileDesktop
Score0%9%
Timing31.8 s8.1 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Minimize third-party usage

MobileDesktop
GradeFailPass
InsightThird-party code blocked the main thread for 1,300 msThird-party code blocked the main thread for 100 ms

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail