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
Desktop Performance

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.

Largest Contentful Paint3.5 s1.0 s< 2.5 s
First Input Delay140 ms50 ms< 100ms
Cumulative Layout Shift0.0030.003 0.1


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.

WorkSans-Regular.woff2 ~65 KB ~47 KB
Raleway-Regular.woff2 ~63 KB ~45 KB
PolySans-Median.woff2 ~22 KB ~4 KB
PolySans-Neutral.woff2 ~22 KB ~4 KB
PolySans-Slim.woff2 ~22 KB ~4 KB

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.min.js 32 KB
jquery-migrate.min.js 5 KB

Largest Contentful Paint

Timing3.5 s1.0 s

Total Blocking Time

Timing130 ms0 ms

Speed Index

Timing4.1 s1.5 s

Time to Interactive

Timing3.5 s0.7 s

Max Potential First Input Delay

Timing140 ms50 ms

Properly size images

InsightPotential savings of 26 KiBPotential savings of 349 KiB

Reduce initial server response time

InsightRoot document took 950 msRoot document took 980 ms

Serve static assets with an efficient cache policy

Insight25 resources found27 resources found

Avoids an excessive DOM size

Insight497 elements497 elements

JavaScript execution time

Timing2.5 s0.9 s

Minimizes main-thread work

Timing5.4 s2.0 s

Largest Contentful Paint image was lazily loaded