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
Desktop Performance

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.

Largest Contentful Paint11.2 s2.3 s< 2.5 s
First Input Delay2,310 ms660 ms< 100ms
Cumulative Layout Shift0.0020.072 0.1

Tracking scripts

All the tracking scripts on the site generated ~380 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 2 173 KB 1 46 KB 1 347 B 2 116 KB 6 25 KB 3 2 KB 2 328 B 2 0 B 2 574 B 1 557 B 2 1 KB 2 2 KB 1 803 B 1 731 B 1 786 B 1 316 B 2 1 KB 2 1 KB 2 876 B 2 1 KB 1 616 B 2 1 KB 1 936 B 1 287 B 1 793 B 1 736 B 1 855 B


Assets that need text compression enabled

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

View details
/ 547 KB 451 KB
i 12 KB 10 KB
style.css 3 KB 2 KB

Optimise images

By optimising the following images, roughly 3 MB could be removed from the transfer size, about 32%. This would reduce the CO2 generated per page load from 2.35g grams to 1.6 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.
View details
outlet-mega-nav.gif 3 MB 33% 3 MB
aus-hero-1-mobile.jpg 316 KB 3% 72 KB
30603knde_navyherr_1_1500x1500.webp 299 KB 3% 55 KB

Replace inlined font files

There are 1 inlined fonts that should converted to subresources.

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 revsglobal-pr-mod.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.
Timing3.5 s0.7 s

Largest Contentful Paint

Timing11.2 s2.3 s

Total Blocking Time

Timing7,000 ms2,290 ms

Cumulative Layout Shift


Speed Index

Timing27.2 s4.2 s

Time to Interactive

Timing32.5 s7.5 s

Max Potential First Input Delay

Timing2,310 ms660 ms

First Meaningful Paint

Timing3.6 s0.7 s

Properly size images

InsightPotential savings of 5,227 KiB

Reduce unused JavaScript

InsightPotential savings of 915 KiBPotential savings of 945 KiB

Enable text compression

InsightPotential savings of 461 KiBPotential savings of 463 KiB

Reduce initial server response time

InsightRoot document took 1,780 msRoot document took 1,710 ms

Use video formats for animated content

InsightPotential savings of 3,119 KiBPotential savings of 3,119 KiB

Remove duplicate modules in JavaScript bundles

InsightPotential savings of 86 KiBPotential savings of 85 KiB

Avoid serving legacy JavaScript to modern browsers

InsightPotential savings of 82 KiBPotential savings of 64 KiB

Avoid enormous network payloads

InsightTotal size was 9,509 KiBTotal size was 10,521 KiB

Serve static assets with an efficient cache policy

Insight21 resources found49 resources found

Avoid an excessive DOM size

Insight27 elements1,405 elements

Reduce JavaScript execution time

Timing13.8 s5.1 s

Minimize main-thread work

Timing18.3 s7.5 s

Reduce the impact of third-party code

InsightThird-party code blocked the main thread for 6,160 msThird-party code blocked the main thread for 2,320 ms

Does not use passive listeners to improve scrolling performance


Avoid document.write()


Image elements do not have explicit width and height