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.

Pass or fail?


CWV Breakdown

Largest Contentful Paint5.4 s5.5 s< 2.5 s
First Input Delay4,770 ms1,390 ms< 100ms
Cumulative Layout Shift0.0480.02 0.1

Tracking scripts

All the tracking scripts on the site generated ~586 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 182 KB 3 65 KB 16 246 KB 1 197 B 3 2 KB 1 472 B 1 380 B 1 860 B 6 4 KB 4 2 KB 15 11 KB 2 1 KB 5 3 KB 2 956 B 1 691 B 2 2 KB 1 815 B 12 8 KB 7 6 KB 3 4 KB 2 12 KB 4 2 KB 6 5 KB 1 980 B 5 5 KB 2 5 KB 3 1 KB 1 467 B 2 770 B 1 640 B 3 3 KB 1 989 B 4 3 KB 1 356 B 1 855 B 5 3 KB 1 700 B 2 712 B 1 630 B 1 235 B


Remove autoplaying or preloaded media files1 video0.0 B

By removing 1 autoplaying or preloaded videos, roughly 0.0 B could be removed from the page load.

This would reduce the page transfer size by 0% and reduce the pages emissions from 1.4 grams of CO2 to 1.4 grams of CO2.

Autoplaying videos can have a negative impact on the user experience for several reasons:

  1. Increased data usage: Autoplaying videos can consume a lot of data, especially if they are set to play in high definition. This can be a problem for users with limited data plans or slow connections, who may experience slow or interrupted playback.
  2. Annoyance factor: Autoplaying videos can be annoying for users, especially if they are accompanied by sound. This can lead to a negative perception of the website and decreased engagement.
  3. Reduced accessibility: Autoplaying videos can be a problem for users with accessibility needs, such as users who are blind or have hearing difficulties.
  4. Increased page load time: Autoplaying videos can increase the overall page load time, leading to a slower user experience.
  5. Decreased battery life: Autoplaying videos can consume a lot of battery power, especially on mobile devices, leading to reduced battery life.

In order to minimise the impact of autoplaying videos on the user experience, it is recommended to use them sparingly and only when necessary. It is also important to provide users with the option to turn off autoplaying videos and to allow them to control the playback of videos on the page. Additionally, videos should be optimised for performance and should be accompanied by captions or transcripts to improve accessibility.

View details
fc74dd9d-609d-4cd5-ae69-b08bd7ddaf18 0 B 0%
Assets that need text compression enabled23 KB0.005g

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

View details
ad-tracking.js 9 KB 7 KB
ad-tracking.js 9 KB 7 KB
ad-tracking.js 9 KB 7 KB
eventtracker-snippet.js 3 KB 2 KB
pr 2 KB 1 KB
Optimise images2 MB0.446g

By optimising the following images, roughly 2 MB could be removed from the transfer size, about 32%. This would reduce the CO2 generated per page load from 1.4g grams to 0.95 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
4997763198458966905 407 KB 7% 318 KB
11844870828169595759 259 KB 4% 191 KB
5247407539673474141 252 KB 4% 196 KB
1833086610072121988 245 KB 4% 220 KB
14823162703348242362 221 KB 4% 196 KB
3774400676360965938 193 KB 3% 168 KB
11170470302353487380 170 KB 3% 147 KB
13313744088488288806 149 KB 2% 106 KB
7076880491583306224 130 KB 2% 114 KB
14840528201358298462 127 KB 2% 106 KB
7347196514229290628 124 KB 2% 105 KB
CLI_PRO_Social_Cover-threeByTwoSmallAt2X.jpg 95 KB 2% 48 KB
380078100487396290 62 KB 1% 48 KB
7371749549331346085 30 KB 0% 22 KB
12709063123019235784 18 KB 0% 13 KB
Subset large font files125 KB0.028g

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.

View details
cheltenham-text-cond-normal-700.7e78f9e7e6c2e02d82592c4466929fa3.woff2 ~29 KB ~12 KB
cheltenham-normal-700.530cfb72378419eedb60da7e266ad5f1.woff2 ~29 KB ~11 KB
cheltenham-normal-300.7ea91ebd036309e1fe756ee3aab272da.woff2 ~28 KB ~10 KB
franklin-normal-700.woff ~27 KB ~10 KB
karnak-normal-400.woff2 ~27 KB ~10 KB
cheltenham-normal-300.woff2 ~27 KB ~10 KB
franklin-normal-500.woff ~27 KB ~9 KB
imperial-normal-400.6131cd77b6e216c7693ed925f4309ffc.woff2 ~27 KB ~9 KB
cheltenham-normal-200.40ccfe2cc61a71e6617e56162d49b896.woff2 ~27 KB ~9 KB
cheltenham-small-italic-400.cdfa0ec29cca8c2d2f54c79d898e15c1.woff2 ~25 KB ~7 KB
cheltenham-small-normal-700.1a0b316424cdebd18086b8dbbc768eef.woff2 ~24 KB ~7 KB
franklin-normal-700.91eaf6b5642463af4091160b4bbfdfcb.woff2 ~21 KB ~3 KB
franklin-normal-600.75739ac267f076931c6da9740386ee6b.woff2 ~21 KB ~3 KB
NYTKarnakCondensed-Bold.woff2 ~21 KB ~3 KB
franklin-normal-700.woff2 ~20 KB ~3 KB
franklin-normal-700.woff2 ~20 KB ~3 KB
franklin-normal-500.0f4aea3d462cdb64748629efcbbf36bc.woff2 ~20 KB ~3 KB
franklin-normal-500.woff2 ~20 KB ~2 KB
Convert font files to woff28 KB

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.

View details
franklin-normal-700.woff woff
franklin-normal-500.woff woff
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 franklin-normal-700.91eaf6b5642463af4091160b4bbfdfcb.woff2 franklin-normal-500.0f4aea3d462cdb64748629efcbbf36bc.woff2 cheltenham-normal-700.530cfb72378419eedb60da7e266ad5f1.woff2 imperial-normal-400.6131cd77b6e216c7693ed925f4309ffc.woff2 cheltenham-normal-200.40ccfe2cc61a71e6617e56162d49b896.woff2 cheltenham-small-normal-700.1a0b316424cdebd18086b8dbbc768eef.woff2 cheltenham-text-cond-normal-700.7e78f9e7e6c2e02d82592c4466929fa3.woff2 cheltenham-small-italic-400.cdfa0ec29cca8c2d2f54c79d898e15c1.woff2 cheltenham-normal-300.7ea91ebd036309e1fe756ee3aab272da.woff2 franklin-normal-600.75739ac267f076931c6da9740386ee6b.woff2 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2 6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdu3cOWxw.woff2 NYTKarnakCondensed-Bold.woff2 franklin-normal-700.woff2 cheltenham-normal-300.woff2 franklin-normal-700.woff 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.woff2 karnak-normal-400.woff2 franklin-normal-500.woff franklin-normal-700.woff2 franklin-normal-500.woff2 6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7lujVj9w.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.8 s
Largest Contentful Paint

Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric

Timing5.4 s5.5 s
Total Blocking Time

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.

Timing10,830 ms3,810 ms
Cumulative Layout Shift

Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.

Speed Index

Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.

Timing20.5 s8.8 s
Time to Interactive

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Timing31.7 s10.8 s
Max Potential First Input Delay

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Timing4,770 ms1,390 ms
First Meaningful Paint

First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Timing3.5 s0.8 s
Eliminate render-blocking resources

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.

InsightPotential savings of 1,920 msPotential savings of 500 ms
Properly size images

Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.

InsightPotential savings of 118 KiB
Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.

InsightPotential savings of 123 KiBPotential savings of 87 KiB
Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

InsightPotential savings of 48 KiB
Reduce unused CSS

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

InsightPotential savings of 46 KiBPotential savings of 46 KiB
Reduce unused JavaScript

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

InsightPotential savings of 629 KiBPotential savings of 804 KiB
Efficiently encode images

Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

InsightPotential savings of 10 KiBPotential savings of 150 KiB
Serve images in next-gen formats

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.

InsightPotential savings of 104 KiBPotential savings of 1,998 KiB
Use video formats for animated content

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats

InsightPotential savings of 176 KiB
Preload Largest Contentful Paint image

If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.

InsightPotential savings of 40 ms
Avoid enormous network payloads

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

InsightTotal size was 2,951 KiBTotal size was 6,252 KiB
Serve static assets with an efficient cache policy

A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.

Insight24 resources found31 resources found
Avoid an excessive DOM size

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.

Insight1,497 elements1,975 elements
Reduce JavaScript execution time

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Timing21.8 s9.9 s
Minimize main-thread work

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Timing27.6 s15.2 s
Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more about font-display.

Reduce the impact of third-party code

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.

InsightThird-party code blocked the main thread for 2,040 msThird-party code blocked the main thread for 1,460 ms
Does not use passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.

Avoid document.write()

For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().