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
41%
Desktop Performance
87%

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 Paint7.1 s1.6 s< 2.5 s
First Input Delay620 ms180 ms< 100ms
Cumulative Layout Shift00.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.

32FE8A_2_0.woff2 ~143 KB ~126 KB
32FE8A_3_0.woff2 ~139 KB ~122 KB
32FE8A_1_0.woff2 ~139 KB ~121 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
Score97%100%
Timing1.4 s0.4 s

Largest Contentful Paint

MobileDesktop
Score5%78%
Timing7.1 s1.6 s

Total Blocking Time

MobileDesktop
Score11%94%
Timing1,650 ms130 ms

Speed Index

MobileDesktop
Score18%44%
Timing8.4 s2.4 s

Time to Interactive

MobileDesktop
Score12%85%
Timing13.2 s2.7 s

Max Potential First Input Delay

MobileDesktop
Score3%74%
Timing620 ms180 ms

First Meaningful Paint

MobileDesktop
Score99%100%
Timing1.4 s0.4 s

Eliminate render-blocking resources

MobileDesktop
Score94%98%
InsightPotential savings of 80 msPotential savings of 20 ms

Properly size images

MobileDesktop
Score92%91%
InsightPotential savings of 37 KiBPotential savings of 214 KiB

Defer offscreen images

MobileDesktop
Score98%100%
InsightPotential savings of 72 KiB

Minify JavaScript

MobileDesktop
Score67%87%
InsightPotential savings of 79 KiBPotential savings of 79 KiB

Reduce unused CSS

MobileDesktop
Score73%93%
InsightPotential savings of 48 KiBPotential savings of 37 KiB

Reduce unused JavaScript

MobileDesktop
Score36%71%
InsightPotential savings of 357 KiBPotential savings of 371 KiB

Serve images in next-gen formats

MobileDesktop
Score93%90%
InsightPotential savings of 50 KiBPotential savings of 108 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 1,380 msRoot document took 1,220 ms

Serve static assets with an efficient cache policy

MobileDesktop
Score46%44%
Insight34 resources found36 resources found

Avoid an excessive DOM size

MobileDesktop
Score48%50%
Insight1,418 elements1,394 elements

JavaScript execution time

MobileDesktop
Score49%98%
Timing3.5 s0.7 s

Minimizes main-thread work

MobileDesktop
Score25%98%
Timing5.7 s1.3 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Minimize third-party usage

MobileDesktop
GradeFailPass
InsightThird-party code blocked the main thread for 930 msThird-party code blocked the main thread for 80 ms

Uses passive listeners to improve scrolling performance

MobileDesktop
GradeFailPass

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail