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
40%
Desktop Performance
74%

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 Paint13.1 s3.4 s< 2.5 s
First Input Delay370 ms130 ms< 100ms
Cumulative Layout Shift0.0170.057 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.

memtYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWqWuU6FxZCJgg.woff2 ~43 KB ~25 KB
memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2 ~39 KB ~22 KB
Typekit: l ~30 KB ~13 KB
Typekit: l ~27 KB ~10 KB
Typekit: l ~21 KB ~3 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
fonts.gstatic.compxiEyp8kv8JHgFVrJJfecnFHGPc.woff2
use.typekit.netl
use.typekit.netl
use.typekit.netl
fonts.gstatic.commemvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2
fonts.gstatic.commemtYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWqWuU6FxZCJgg.woff2
fonts.gstatic.comS6u9w4BMUTPHh6UVSwiPGQ3q5d0.woff2
fonts.gstatic.comS6u_w4BMUTPHjxsI5wq_Gwftx9897g.woff2
script.hotjar.comfont-hotjar_5.65042d.woff2

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
Score62%97%
Timing2.6 s0.7 s

Largest Contentful Paint

MobileDesktop
Score0%25%
Timing13.1 s3.4 s

Total Blocking Time

MobileDesktop
Score23%96%
Timing1,120 ms110 ms

Cumulative Layout Shift

MobileDesktop
Score100%98%
Timing0.0170.057

Speed Index

MobileDesktop
Score22%43%
Timing7.9 s2.5 s

Time to Interactive

MobileDesktop
Score7%68%
Timing15.3 s3.6 s

Max Potential First Input Delay

MobileDesktop
Score22%91%
Timing370 ms130 ms

First Meaningful Paint

MobileDesktop
Score79%96%
Timing2.8 s0.8 s

Eliminate render-blocking resources

MobileDesktop
Score40%67%
InsightPotential savings of 1,590 msPotential savings of 440 ms

Properly size images

MobileDesktop
Score36%49%
InsightPotential savings of 376 KiBPotential savings of 813 KiB

Reduce unused CSS

MobileDesktop
Score66%87%
InsightPotential savings of 72 KiBPotential savings of 68 KiB

Reduce unused JavaScript

MobileDesktop
Score33%71%
InsightPotential savings of 473 KiBPotential savings of 462 KiB

Serve images in next-gen formats

MobileDesktop
Score15%49%
InsightPotential savings of 752 KiBPotential savings of 947 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 1,680 msRoot document took 1,420 ms

Avoid serving legacy JavaScript to modern browsers

MobileDesktop
Score100%97%
InsightPotential savings of 47 KiBPotential savings of 47 KiB

Avoid enormous network payloads

MobileDesktop
Score85%78%
InsightTotal size was 2,857 KiBTotal size was 3,118 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score4%3%
Insight70 resources found77 resources found

Avoid an excessive DOM size

MobileDesktop
Score58%52%
Insight1,283 elements1,359 elements

JavaScript execution time

MobileDesktop
Score52%97%
Timing3.3 s0.8 s

Minimizes main-thread work

MobileDesktop
Score26%94%
Timing5.6 s1.7 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,710 msThird-party code blocked the main thread for 150 ms

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail