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
49%
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 Paint5.2 s1.0 s< 2.5 s
First Input Delay330 ms80 ms< 100ms
Cumulative Layout Shift0.0780.002 0.1

Tracking scripts

All the tracking scripts on the site generated ~296 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.

googletagmanager.com 2 135 KB
google-analytics.com 4 21 KB
connect.facebook.net 2 138 KB
stats.g.doubleclick.net 1 581 B
facebook.com 2 656 B
in.hotjar.com 1 407 B

Opportunities

Optimise images

By optimising the following images, roughly 867 KB could be removed from the transfer size, about 36%. This would reduce the CO2 generated per page load from 0.54g grams to 0.35 grams.

Images should be optimised for the web for several reasons:

  1. Reduced file size: Optimizing images can result in a smaller file size, which can help to reduce the amount of data that needs to be downloaded. This can lead to faster page load times and improved performance.
  2. Improved user experience: Optimising images can help to improve the overall user experience, as pages with optimised images load faster and are more responsive.
  3. Lower emissions: Optimising images can help to reduce the emissions associated with data transfer, as less data needs to be transmitted over the network.
  4. Better accessibility: Optimising images can make them more accessible to users with slower connections or limited data plans.

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
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
Score83%99%
Timing2.0 s0.6 s

Largest Contentful Paint

MobileDesktop
Score24%94%
Timing5.2 s1.0 s

Total Blocking Time

MobileDesktop
Score27%100%
Timing990 ms20 ms

Cumulative Layout Shift

MobileDesktop
Score95%100%
Timing0.0780.002

Speed Index

MobileDesktop
Score29%56%
Timing7.3 s2.1 s

Time to Interactive

MobileDesktop
Score27%96%
Timing9.9 s1.9 s

Max Potential First Input Delay

MobileDesktop
Score28%99%
Timing330 ms80 ms

First Meaningful Paint

MobileDesktop
Score94%99%
Timing2.0 s0.6 s

Eliminate render-blocking resources

MobileDesktop
Score50%83%
InsightPotential savings of 760 msPotential savings of 210 ms

Properly size images

MobileDesktop
Score15%56%
InsightPotential savings of 739 KiBPotential savings of 783 KiB

Reduce unused CSS

MobileDesktop
Score100%93%
InsightPotential savings of 46 KiBPotential savings of 49 KiB

Reduce unused JavaScript

MobileDesktop
Score24%56%
InsightPotential savings of 600 KiBPotential savings of 603 KiB

Serve images in next-gen formats

MobileDesktop
Score27%65%
InsightPotential savings of 537 KiBPotential savings of 537 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 1,490 msRoot document took 1,940 ms

Avoids enormous network payloads

MobileDesktop
Score94%94%
InsightTotal size was 2,418 KiBTotal size was 2,417 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score32%32%
Insight10 resources found10 resources found

Avoid an excessive DOM size

MobileDesktop
Score24%31%
Insight1,871 elements1,717 elements

JavaScript execution time

MobileDesktop
Score69%100%
Timing2.4 s0.5 s

Minimizes main-thread work

MobileDesktop
Score32%98%
Timing5.1 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 430 msThird-party code blocked the main thread for 0 ms

Largest Contentful Paint image was not lazily loaded

MobileDesktop
GradeFailPass

Does not use passive listeners to improve scrolling performance

MobileDesktop
GradeFailFail

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail