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
4%
Desktop Performance
33%

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 Paint15.2 s2.9 s< 2.5 s
First Input Delay1,270 ms300 ms< 100ms
Cumulative Layout Shift1.2460.417 0.1

Tracking scripts

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

google-analytics.com 4 22 KB

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.

b86524f7-009e-4c08-a266-c43f1fb68e5e-e89ad3b7b29f8e69ec2253c3a74bdc97.woff2 ~25 KB ~7 KB
bb590848-4012-46d6-a8d5-48c9893a176b-858e8ae6d87c456ccee6f55e11f62fa9.woff2 ~25 KB ~7 KB
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjp-Ek-_EeA.woff ~22 KB ~4 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
hubcdn.arcgis.combb590848-4012-46d6-a8d5-48c9893a176b-858e8ae6d87c456ccee6f55e11f62fa9.woff2
hubcdn.arcgis.comb86524f7-009e-4c08-a266-c43f1fb68e5e-e89ad3b7b29f8e69ec2253c3a74bdc97.woff2
fonts.gstatic.comUcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjp-Ek-_EeA.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
Score0%33%
Timing10.4 s1.9 s

Largest Contentful Paint

MobileDesktop
Score0%36%
Timing15.2 s2.9 s

Total Blocking Time

MobileDesktop
Score11%50%
Timing1,700 ms350 ms

Cumulative Layout Shift

MobileDesktop
Score1%23%
Timing1.2460.417

Speed Index

MobileDesktop
Score0%0%
Timing21.5 s6.9 s

Time to Interactive

MobileDesktop
Score13%90%
Timing12.8 s2.5 s

Max Potential First Input Delay

MobileDesktop
Score0%36%
Timing1,270 ms300 ms

First Meaningful Paint

MobileDesktop
Score1%33%
Timing10.4 s1.9 s

Properly size images

MobileDesktop
Score75%93%
InsightPotential savings of 66 KiBPotential savings of 109 KiB

Reduce unused CSS

MobileDesktop
Score49%98%
InsightPotential savings of 135 KiBPotential savings of 142 KiB

Reduce unused JavaScript

MobileDesktop
Score0%48%
InsightPotential savings of 1,177 KiBPotential savings of 1,176 KiB

Serve images in next-gen formats

MobileDesktop
Score43%83%
InsightPotential savings of 257 KiBPotential savings of 257 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 1,360 msRoot document took 1,410 ms

Preload Largest Contentful Paint image

MobileDesktop
Score75%93%
InsightPotential savings of 300 msPotential savings of 80 ms

Avoids enormous network payloads

MobileDesktop
Score91%92%
InsightTotal size was 2,577 KiBTotal size was 2,557 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score22%22%
Insight4 resources found4 resources found

Avoid an excessive DOM size

MobileDesktop
Score32%32%
Insight1,687 elements1,694 elements

JavaScript execution time

MobileDesktop
Score42%95%
Timing4.1 s0.9 s

Minimizes main-thread work

MobileDesktop
Score12%95%
Timing7.3 s1.6 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Reduce the impact of third-party code

MobileDesktop
GradeFailFail
InsightThird-party code blocked the main thread for 3,300 msThird-party code blocked the main thread for 490 ms

Largest Contentful Paint image was not lazily loaded

MobileDesktop
GradeFailPass

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail