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
61%
Desktop Performance
94%

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 Paint6.9 s1.5 s< 2.5 s
First Input Delay230 ms90 ms< 100ms
Cumulative Layout Shift00.012 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.

opensans-regular-webfont.woff ~84 KB ~66 KB
4021a3b9-f782-438b-aeb4-c008109a8b64.woff ~46 KB ~29 KB
c5749443-93da-4592-b794-42f28d62ef72.woff ~38 KB ~21 KB

Convert font files to woff2

WOFF2 is considered to be the best font format for web use because it provides a good balance of file size and compatibility. Some specific reasons why WOFF2 is a good font format include:

  1. Small file size: WOFF2 is a compressed font format, which means that it has a smaller file size compared to other font formats like TTF or OTF. This is important for web use because smaller file sizes can help to reduce the amount of data that needs to be downloaded, leading to faster page load times.
  2. High-quality font rendering: WOFF2 provides high-quality font rendering, making it a good choice for use on the web.

It’s worth noting that WOFF2 is not the only font format that can be used on the web, and there may be cases where other formats like WOFF or TTF are more suitable, depending on the specific requirements of the website. However, for most cases, WOFF2 is considered to be the best font format for web use due to its combination of small file size, good browser support, and high-quality font rendering.

Fontformat
opensans-regular-webfont.woffwoff
4021a3b9-f782-438b-aeb4-c008109a8b64.woffwoff
c5749443-93da-4592-b794-42f28d62ef72.woffwoff

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
static.parastorage.comopensans-regular-webfont.woff
static.parastorage.com4021a3b9-f782-438b-aeb4-c008109a8b64.woff
static.parastorage.comc5749443-93da-4592-b794-42f28d62ef72.woff

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
Score53%97%
Timing2.9 s0.7 s

Largest Contentful Paint

MobileDesktop
Score6%79%
Timing6.9 s1.5 s

Total Blocking Time

MobileDesktop
Score67%100%
Timing400 ms40 ms

Speed Index

MobileDesktop
Score95%96%
Timing2.9 s1.1 s

Time to Interactive

MobileDesktop
Score27%94%
Timing9.9 s2.1 s

Max Potential First Input Delay

MobileDesktop
Score57%98%
Timing230 ms90 ms

First Meaningful Paint

MobileDesktop
Score77%97%
Timing2.9 s0.7 s

Reduce unused JavaScript

MobileDesktop
Score46%90%
InsightPotential savings of 138 KiBPotential savings of 127 KiB

Remove duplicate modules in JavaScript bundles

MobileDesktop
Score58%97%
InsightPotential savings of 51 KiBPotential savings of 33 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score71%72%
Insight40 resources found42 resources found

Avoids an excessive DOM size

MobileDesktop
Score99%99%
Insight540 elements500 elements

JavaScript execution time

MobileDesktop
Score76%99%
Timing2.0 s0.5 s

Minimizes main-thread work

MobileDesktop
Score61%100%
Timing3.4 s1.0 s

Minimize third-party usage

MobileDesktop
GradeFailPass
InsightThird-party code blocked the main thread for 280 msThird-party code blocked the main thread for 60 ms