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
56%
Desktop Performance
79%

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 Paint10.1 s2.3 s< 2.5 s
First Input Delay110 ms20 ms< 100ms
Cumulative Layout Shift00 0.1

Tracking scripts

All the tracking scripts on the site generated ~204 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 1 44 KB
google-analytics.com 2 21 KB
stats.g.doubleclick.net 1 568 B
connect.facebook.net 2 138 KB
facebook.com 3 984 B

Opportunities

Optimise images

By optimising the following images, roughly 662 KB could be removed from the transfer size, about 37%. This would reduce the CO2 generated per page load from 0.47g grams to 0.3 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.
GOA-FreezeRents.jpg 267 KB 15% 222 KB
home-grid-1.png 187 KB 10% 169 KB
2021-Mosaic-GOA.jpg 158 KB 9% 44 KB
home-grid-2.png 114 KB 6% 100 KB
home-grid-update3.png 109 KB 6% 93 KB
YpXYmMlj1QY.jpg 56 KB 3% 25 KB
GOA-No-More-Coal-Gas-Thumb.jpg 29 KB 2% 9 KB

Replace icon font files

Font icons can have a negative impact on performance and emissions because they can increase the size of the page and the amount of data that needs to be downloaded. Some specific reasons why font icons can be bad for performance and emissions include:

  1. Increased file size: Font icons are typically included as part of a web font, which can be a large file that needs to be downloaded. This can increase the overall size of the page, leading to slower load times and higher emissions.
  2. Inefficient rendering: Web fonts are sometimes loaded and rendered inefficiently, which can result in slow performance and higher emissions.
  3. Unused icons: Font icons often include a large number of icons that may not be used on a particular page, increasing the file size and leading to inefficient use of resources.

While icon fonts are still widely used on the web, and they can be a useful tool for adding icons to a website. it is a dated practice when there are better options such as SVG icons, which can be more efficient and have a lower impact on performance and emissions.

FontSize
fa-solid-900.woff2147 KB
fa-brands-400.woff2105 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
fonts.gstatic.compe0qMImSLYBIv1o4X1M8cce9I9tAcVwo.woff2
fonts.gstatic.comieVi2ZhZI2eCN5jzbjEETS9weq8-32meGCQYb9lecyU.woff2
fonts.gstatic.com1Ptgg87LROyAm3Kz-C8CSKlv.woff2
fonts.gstatic.comieVl2ZhZI2eCN5jzbjEETS9weq8-19K7DQk6YvM.woff2
fonts.gstatic.compe03MImSLYBIv1o4X1M8cc8aBc5tU1ECVZl_.woff2
fonts.gstatic.compe03MImSLYBIv1o4X1M8cc9iB85tU1ECVZl_.woff2
fonts.gstatic.compe03MImSLYBIv1o4X1M8cc8GBs5tU1ECVZl_.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
Score19%89%
Timing4.2 s1.0 s

Largest Contentful Paint

MobileDesktop
Score0%54%
Timing10.1 s2.3 s

Total Blocking Time

MobileDesktop
Score98%100%
Timing100 ms0 ms

Speed Index

MobileDesktop
Score2%11%
Timing13.1 s3.9 s

Time to Interactive

MobileDesktop
Score30%100%
Timing9.5 s1.0 s

Max Potential First Input Delay

MobileDesktop
Score94%100%
Timing110 ms20 ms

First Meaningful Paint

MobileDesktop
Score44%89%
Timing4.2 s1.0 s

Eliminate render-blocking resources

MobileDesktop
Score22%59%
InsightPotential savings of 3,130 msPotential savings of 590 ms

Properly size images

MobileDesktop
Score57%78%
InsightPotential savings of 273 KiBPotential savings of 308 KiB

Minify JavaScript

MobileDesktop
Score100%97%
InsightPotential savings of 5 KiBPotential savings of 5 KiB

Reduce unused CSS

MobileDesktop
Score75%93%
InsightPotential savings of 40 KiBPotential savings of 26 KiB

Reduce unused JavaScript

MobileDesktop
Score54%90%
InsightPotential savings of 135 KiBPotential savings of 135 KiB

Efficiently encode images

MobileDesktop
Score86%87%
InsightPotential savings of 153 KiBPotential savings of 153 KiB

Serve images in next-gen formats

MobileDesktop
Score50%74%
InsightPotential savings of 300 KiBPotential savings of 662 KiB

Enable text compression

MobileDesktop
Score93%100%
InsightPotential savings of 10 KiBPotential savings of 10 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 850 msRoot document took 730 ms

Avoids enormous network payloads

MobileDesktop
Score100%99%
InsightTotal size was 1,399 KiBTotal size was 1,808 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score13%12%
Insight169 resources found172 resources found

Avoids an excessive DOM size

MobileDesktop
Score96%96%
Insight650 elements650 elements

JavaScript execution time

MobileDesktop
Score96%100%
Timing0.9 s0.1 s

Minimizes main-thread work

MobileDesktop
Score75%100%
Timing2.8 s0.7 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail