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
38%
Desktop Performance
78%

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 Paint9.0 s2.5 s< 2.5 s
First Input Delay920 ms80 ms< 100ms
Cumulative Layout Shift0.0190.003 0.1

Opportunities

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.

vic-bold-webfont.woff2 ~19 KB ~2 KB
vic-medium-webfont.woff2 ~19 KB ~2 KB
vic-regular-webfont.woff2 ~19 KB ~1 KB
vic-semibold-webfont.woff2 ~19 KB ~1 KB

Remove third party font files

Font files should be loaded from the same hosting as the website because

  1. Increased loading time: Third-party sub-resources, such as scripts, fonts, or images, need to be downloaded from a separate server before they can be displayed on the website. This can increase the overall loading time of the page, leading to a slower user experience.
  2. Dependence on external servers: The loading of third-party subresources is dependent on the availability and performance of the external servers that host them. If these servers are slow or unavailable, it can result in slow page loading times or even errors.
  3. Increased risk of security threats: Third-party subresources can introduce security risks to a website, as they can contain malicious code or be used to track user activity.
HostFont
script.hotjar.comfont-hotjar_5.65042d.woff2

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.3.1.min.js 30 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
Score78%99%
Timing2.2 s0.6 s

Largest Contentful Paint

MobileDesktop
Score1%46%
Timing9.0 s2.5 s

Total Blocking Time

MobileDesktop
Score13%100%
Timing1,530 ms20 ms

Speed Index

MobileDesktop
Score11%14%
Timing9.5 s3.7 s

Time to Interactive

MobileDesktop
Score15%98%
Timing12.2 s1.7 s

Max Potential First Input Delay

MobileDesktop
Score0%98%
Timing920 ms80 ms

First Meaningful Paint

MobileDesktop
Score92%99%
Timing2.2 s0.6 s

Eliminate render-blocking resources

MobileDesktop
Score47%77%
InsightPotential savings of 1,010 msPotential savings of 280 ms

Properly size images

MobileDesktop
Score88%80%
InsightPotential savings of 61 KiBPotential savings of 244 KiB

Defer offscreen images

MobileDesktop
Score46%100%
InsightPotential savings of 274 KiB

Reduce unused CSS

MobileDesktop
Score100%93%
InsightPotential savings of 58 KiBPotential savings of 66 KiB

Reduce unused JavaScript

MobileDesktop
Score39%83%
InsightPotential savings of 304 KiBPotential savings of 316 KiB

Efficiently encode images

MobileDesktop
Score38%77%
InsightPotential savings of 395 KiBPotential savings of 395 KiB

Serve images in next-gen formats

MobileDesktop
Score24%67%
InsightPotential savings of 603 KiBPotential savings of 603 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 2,280 msRoot document took 2,320 ms

Avoid serving legacy JavaScript to modern browsers

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

Avoids enormous network payloads

MobileDesktop
Score99%99%
InsightTotal size was 1,830 KiBTotal size was 1,854 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score67%66%
Insight15 resources found15 resources found

Avoid an excessive DOM size

MobileDesktop
Score41%41%
Insight1,527 elements1,527 elements

JavaScript execution time

MobileDesktop
Score55%100%
Timing3.1 s0.4 s

Minimizes main-thread work

MobileDesktop
Score29%100%
Timing5.3 s0.9 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,220 msThird-party code blocked the main thread for 0 ms

Does not use passive listeners to improve scrolling performance

MobileDesktop
GradeFailFail

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail