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
48%

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 Paint7.4 s3.0 s< 2.5 s
First Input Delay1,050 ms280 ms< 100ms
Cumulative Layout Shift0.0110.003 0.1

Tracking scripts

All the tracking scripts on the site generated ~387 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 246 KB
connect.facebook.net 2 92 KB
google-analytics.com 2 21 KB
analytics.google.com 1 0 B
stats.g.doubleclick.net 2 578 B
js.adsrvr.org 2 4 KB
facebook.com 1 328 B
vc.hotjar.io 1 339 B
content.hotjar.io 1 205 B
js-agent.newrelic.com 1 16 KB
insight.adsrvr.org 1 443 B
match.adsrvr.org 2 2 KB
bam.nr-data.net 1 488 B
cm.g.doubleclick.net 2 2 KB
pixel.rubiconproject.com 1 0 B
ups.analytics.yahoo.com 3 2 KB

Opportunities

Assets that need text compression enabled84 KB0.022g

By enabling text compression on 1 items, , roughly 84.4 KB could be removed from the page load.

View details
/ 113 KB 84 KB
Subset large font files61 KB0.016g

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.

View details
Typekit: l ~30 KB ~13 KB
Typekit: l ~30 KB ~12 KB
Typekit: l ~30 KB ~12 KB
Typekit: l ~29 KB ~12 KB
Typekit: l ~29 KB ~12 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.
View details
use.typekit.net l
use.typekit.net l
use.typekit.net l
use.typekit.net l
use.typekit.net l
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
Score16%13%
Timing4.4 s2.5 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
Score4%34%
Timing7.4 s3.0 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%40%
Timing2,370 ms410 ms
Speed Index

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

MobileDesktop
Score1%9%
Timing15.2 s4.1 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
Score0%23%
Timing26.2 s6.3 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%41%
Timing1,050 ms280 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
Score28%13%
Timing5.1 s2.5 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
Score55%80%
InsightPotential savings of 780 msPotential savings of 270 ms
Properly size images

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

MobileDesktop
Score32%100%
InsightPotential savings of 573 KiBPotential savings of 25 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
Score28%100%
InsightPotential savings of 880 KiBPotential savings of 30 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
Score57%100%
InsightPotential savings of 69 KiBPotential savings of 69 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
Score10%51%
InsightPotential savings of 917 KiBPotential savings of 805 KiB
Serve images in next-gen formats

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.

MobileDesktop
Score12%58%
InsightPotential savings of 1,351 KiBPotential savings of 599 KiB
Enable text compression

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.

MobileDesktop
Score57%67%
InsightPotential savings of 84 KiBPotential savings of 84 KiB
Reduce initial server response time

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

MobileDesktop
GradeFailFail
InsightRoot document took 1,890 msRoot document took 1,900 ms
Avoid serving legacy JavaScript to modern browsers

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript

MobileDesktop
Score75%100%
InsightPotential savings of 31 KiBPotential savings of 31 KiB
Avoid 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
Score51%85%
InsightTotal size was 3,937 KiBTotal size was 2,869 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
Score52%52%
Insight12 resources found12 resources found
Avoids 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%94%
Insight713 elements713 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
Score33%89%
Timing4.9 s1.3 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
Score6%80%
Timing9.1 s2.5 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 2,020 msThird-party code blocked the main thread for 320 ms
Does not use passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.

MobileDesktop
GradeFailFail
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
GradeFailFail