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 Paint20.3 s4.0 s< 2.5 s
First Input Delay840 ms290 ms< 100ms
Cumulative Layout Shift1.0160.534 0.1

Tracking scripts

All the tracking scripts on the site generated ~65 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. 1 44 KB 2 21 KB


Optimise images

By optimising the following images, roughly 4 MB could be removed from the transfer size, about 53%. This would reduce the CO2 generated per page load from 1.99g grams to 0.94 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.
QVWC_HomePage_VenueHireTile4.jpg 1 MB 16% 1 MB
QVWC-SHOP-SisterhoodBanner_1440x400.gif 1 MB 13% 786 KB
Sisterhood_Banner_BlueBG_with-Logo.gif 636 KB 8% 392 KB
591-qvwc-iwd-0204-LowRes.jpg 402 KB 5% 229 KB
591-qvwc-iwd-0319-LowRes.jpg 311 KB 4% 171 KB
QVWC_HomePagePattern-2.jpg 289 KB 4% 242 KB
591-qvwc-iwd-0328-LowRes.jpg 244 KB 3% 121 KB
674-MAFevent-018.jpg 190 KB 2% 109 KB
collage.jpg 189 KB 2% 93 KB
674-MAFevent-078.jpg 183 KB 2% 107 KB
661-qvwc-weconnectppe-3430-LR.jpg 153 KB 2% 90 KB
559-qvwc-2020launch-5645-LowRes.jpg 149 KB 2% 89 KB
559-qvwc-2020launch-5385-LowRes.jpg 145 KB 2% 92 KB
READ+%282%29.jpg 145 KB 2% 90 KB
591-qvwc-iwd-0407-LowRes.jpg 143 KB 2% 87 KB
QVWC_HomePage_Community_Tile_Listen.jpg 110 KB 1% 57 KB
591-qvwc-iwd-1236-LowRes.jpg 105 KB 1% 62 KB
COMEDY_FEST_1000x500PX.jpg 78 KB 1% 27 KB
COMEDY_FEST_1000x500PX.jpg 74 KB 1% 27 KB
Cropped+and+Lighter.jpg 72 KB 1% 31 KB
image-asset.jpeg 43 KB 1% 17 KB
image-asset.jpeg 42 KB 1% 13 KB
image-asset.jpeg 32 KB 0% 17 KB
image-asset.jpeg 30 KB 0% 15 KB
image-asset.jpeg 26 KB 0% 11 KB
image-asset.jpeg 23 KB 0% 13 KB
image-asset.jpeg 21 KB 0% 11 KB

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.

FormulaCondensed-Regular+%281%29.otf ~26 KB ~9 KB
qkB9XvYC6trAT55ZBi1ueQVIjQTD-JrIH2G7nytkHRyQ8p4wUje6bmMorHA.woff2 ~22 KB ~4 KB
Typekit: l ~21 KB ~4 KB
Typekit: l ~21 KB ~3 KB
Typekit: l ~20 KB ~3 KB
Typekit: l ~19 KB ~2 KB

Convert font files to woff2

WOFF2 is considered to be the best font format for web use because it provides a good balance of file size and compatibility. Some specific reasons why WOFF2 is a good font format include:

  1. Small file size: WOFF2 is a compressed font format, which means that it has a smaller file size compared to other font formats like TTF or OTF. This is important for web use because smaller file sizes can help to reduce the amount of data that needs to be downloaded, leading to faster page load times.
  2. High-quality font rendering: WOFF2 provides high-quality font rendering, making it a good choice for use on the web.

It’s worth noting that WOFF2 is not the only font format that can be used on the web, and there may be cases where other formats like WOFF or TTF are more suitable, depending on the specific requirements of the website. However, for most cases, WOFF2 is considered to be the best font format for web use due to its combination of small file size, good browser support, and high-quality font rendering.


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.

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.
Timing9.5 s2.0 s

Largest Contentful Paint

Timing20.3 s4.0 s

Total Blocking Time

Timing650 ms310 ms

Cumulative Layout Shift


Speed Index

Timing14.5 s3.9 s

Time to Interactive

Timing13.7 s2.7 s

Max Potential First Input Delay

Timing840 ms290 ms

First Meaningful Paint

Timing9.6 s2.2 s

Eliminate render-blocking resources

InsightPotential savings of 8,430 msPotential savings of 1,420 ms

Properly size images

InsightPotential savings of 1,442 KiBPotential savings of 2,369 KiB

Reduce unused CSS

InsightPotential savings of 76 KiBPotential savings of 77 KiB

Reduce unused JavaScript

InsightPotential savings of 709 KiBPotential savings of 661 KiB

Efficiently encode images

InsightPotential savings of 1,352 KiBPotential savings of 1,410 KiB

Serve images in next-gen formats

InsightPotential savings of 2,837 KiBPotential savings of 2,908 KiB

Enable text compression

InsightPotential savings of 27 KiBPotential savings of 27 KiB

Reduce initial server response time

InsightRoot document took 1,050 msRoot document took 930 ms

Use video formats for animated content

InsightPotential savings of 1,122 KiBPotential savings of 1,204 KiB

Preload Largest Contentful Paint image

InsightPotential savings of 900 msPotential savings of 1,280 ms

Avoid enormous network payloads

InsightTotal size was 7,360 KiBTotal size was 7,725 KiB

Serve static assets with an efficient cache policy

Insight29 resources found39 resources found

Avoids an excessive DOM size

Insight626 elements626 elements

JavaScript execution time

Timing3.5 s1.3 s

Minimize main-thread work

Timing6.8 s2.7 s

Ensure text remains visible during webfont load


Reduce the impact of third-party code

InsightThird-party code blocked the main thread for 1,420 msThird-party code blocked the main thread for 320 ms

Image elements do not have explicit width and height