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
29%
Desktop Performance
67%

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.

Pass or fail?

MobileFail
DesktopFail

CWV Breakdown

VitalMobileDesktopTarget
Largest Contentful Paint9.0 s1.5 s< 2.5 s
First Input Delay850 ms230 ms< 100ms
Cumulative Layout Shift0.0780.066 0.1

Tracking scripts

All the tracking scripts on the site generated ~274 KB of data

A tracking script is a code snippet designed to track the flow of visitors who visit a website. Media, advertising, and analytics organisations will provide a script to add to your website that sends data directly to their servers. This data can then be used to measure goals and conversions, analyse user behaviour, and influence advertising campaigns.

Consider how much of this data you actually need and use? How often do you review the analytics data, and does this inform genuine change? Are you actively running social media campaigns? Consider pausing or removing tracking scripts that aren’t being actively used.

View details
googletagmanager.com 3 234 KB
bat.bing.com 3 15 KB
google-analytics.com 3 21 KB
unpkg.com 1 3 KB
analytics.google.com 1 0 B
stats.g.doubleclick.net 2 572 B
google.com 1 557 B

Opportunities

Replace inlined font files

There is 1 inlined font that should converted to a subresource.

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.
View details
at.alicdn.com font_1404888168_2057645.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
Score12%91%
Timing4.7 s0.9 s
Largest Contentful Paint

Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric

MobileDesktop
Score1%80%
Timing9.0 s1.5 s
Total Blocking Time

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.

MobileDesktop
Score5%30%
Timing2,410 ms490 ms
Cumulative Layout Shift

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.

MobileDesktop
Score95%97%
Timing0.0780.066
Speed Index

Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.

MobileDesktop
Score24%45%
Timing7.7 s2.4 s
Time to Interactive

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

MobileDesktop
Score27%66%
Timing10.0 s3.7 s
Max Potential First Input Delay

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

MobileDesktop
Score0%57%
Timing850 ms230 ms
First Meaningful Paint

First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

MobileDesktop
Score14%84%
Timing6.2 s1.1 s
Eliminate render-blocking resources

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.

MobileDesktop
Score44%100%
InsightPotential savings of 1,120 ms
Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

MobileDesktop
Score4%100%
InsightPotential savings of 2,175 KiBPotential savings of 13 KiB
Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.

MobileDesktop
Score100%96%
InsightPotential savings of 33 KiB
Reduce unused CSS

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

MobileDesktop
Score76%100%
InsightPotential savings of 32 KiB
Reduce unused JavaScript

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

MobileDesktop
Score60%86%
InsightPotential savings of 218 KiBPotential savings of 179 KiB
Avoid multiple page redirects

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

MobileDesktop
Score38%100%
InsightPotential savings of 1,410 ms
Preload Largest Contentful Paint image

If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.

MobileDesktop
Score24%100%
InsightPotential savings of 2,540 ms
Avoids enormous network payloads

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

MobileDesktop
Score20%100%
InsightTotal size was 5,195 KiBTotal size was 1,440 KiB
Serve static assets with an efficient cache policy

A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.

MobileDesktop
Score56%45%
Insight13 resources found27 resources found
Avoid an excessive DOM size

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.

MobileDesktop
Score94%59%
Insight724 elements1,260 elements
Reduce JavaScript execution time

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

MobileDesktop
Score48%83%
Timing3.6 s1.6 s
Minimize main-thread work

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

MobileDesktop
Score5%64%
Timing9.5 s3.3 s
Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.

MobileDesktop
GradeFailFail
Reduce the impact of third-party code

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.

MobileDesktop
GradeFailFail
InsightThird-party code blocked the main thread for 1,430 msThird-party code blocked the main thread for 360 ms
Image elements do not have explicit width and height

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

MobileDesktop
GradePassFail