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
32%
Desktop Performance
38%

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?

MobileFail
DesktopFail

CWV Breakdown

VitalMobileDesktopTarget
Largest Contentful Paint9.3 s2.7 s< 2.5 s
First Input Delay1,110 ms350 ms< 100ms
Cumulative Layout Shift0.0010 0.1

Tracking scripts

All the tracking scripts on the site generated ~1 MB 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
googleadservices.com 3 22 KB
s.go-mpulse.net 1 53 KB
c.go-mpulse.net 1 2 KB
googletagmanager.com 4 325 KB
google-analytics.com 8 22 KB
securepubads.g.doubleclick.net 35 437 KB
c.amazon-adsystem.com 3 80 KB
config.aps.amazon-adsystem.com 1 897 B
ib.adnxs.com 34 43 KB
oajs.openx.net 2 1,023 B
prebid.adnxs.com 1 500 B
rtb.openx.net 14 7 KB
tlx.3lift.com 8 6 KB
ad.360yield.com 25 18 KB
hbopenbid.pubmatic.com 11 2 KB
htlb.casalemedia.com 11 10 KB
google-bidout-d.openx.net 1 999 B
match.adsrvr.org 14 10 KB
cm.g.doubleclick.net 30 19 KB
us-u.openx.net 25 13 KB
jp-u.openx.net 4 2 KB
secure.adnxs.com 8 10 KB
image6.pubmatic.com 11 23 KB
aud.pubmatic.com 1 162 B
googleads.g.doubleclick.net 1 2 KB
stats.g.doubleclick.net 2 575 B
google.com 11 3 KB
aax.amazon-adsystem.com 11 6 KB
analytics.google.com 1 0 B
s.amazon-adsystem.com 23 17 KB
pixel.tapad.com 13 16 KB
sync.mathtag.com 4 3 KB
pixel.rubiconproject.com 16 14 KB
ssum-sec.casalemedia.com 5 7 KB
pippio.com 2 1 KB
ads.pubmatic.com 10 140 KB
sync.1rx.io 1 322 B
s.ad.smaato.net 1 672 B
acdn.adnxs.com 1 17 KB
mailonline-uk-d.openx.net 1 951 B
eb2.3lift.com 12 9 KB
c1.adform.net 5 5 KB
x.bidswitch.net 21 10 KB
rtb.gumgum.com 1 1 KB
ms-cookie-sync.presage.io 1 292 B
u.openx.net 4 2 KB
sync-amz.ads.yieldmo.com 1 1 KB
ups.analytics.yahoo.com 4 3 KB
sync-tm.everesttech.net 4 2 KB
static.cloudflareinsights.com 1 7 KB
dsum-sec.casalemedia.com 8 8 KB
pm.w55c.net 6 4 KB
px.ads.linkedin.com 2 1 KB
cms.quantserve.com 3 2 KB
d.adroll.com 1 235 B
image8.pubmatic.com 11 9 KB
t.pubmatic.com 1 309 B
ssc-cms.33across.com 11 8 KB
p.rfihub.com 1 854 B
beacon.lynx.cognitivlabs.com 1 398 B
dis.criteo.com 1 574 B
a.tribalfusion.com 1 939 B
um.simpli.fi 4 3 KB
sync.ipredictive.com 2 1 KB
dsum.casalemedia.com 1 1,017 B
image2.pubmatic.com 12 7 KB
aax-eu.amazon-adsystem.com 1 855 B
simage2.pubmatic.com 23 13 KB
s.tribalfusion.com 1 828 B
image4.pubmatic.com 1 356 B
dpm.demdex.net 2 2 KB
bttrack.com 1 652 B
i.w55c.net 2 1 KB
sync.crwdcntrl.net 2 1 KB
match.adsby.bidtheatre.com 2 1 KB
sync.smartadserver.com 1 236 B
pubads.g.doubleclick.net 3 3 KB
ssum.casalemedia.com 1 1 KB
simage4.pubmatic.com 8 3 KB
cs.iqzone.com 2 1 KB
csync.loopme.me 2 914 B
ipac.ctnsnet.com 1 496 B
matching.truffle.bid 1 155 B
px.owneriq.net 2 1 KB
cm.adform.net 1 785 B

Opportunities

Remove autoplaying or preloaded media files3 videos5.8 MB1.33g CO2

By removing 3 autoplaying or preloaded videos, roughly 5.8 MB could be removed from the page load.

This would reduce the page transfer size by 46% and reduce the pages emissions from 2.87 grams of CO2 to 1.54 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.

Assets that need text compression enabled9 KB0.002g

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

View details
PugMaster 5 KB 4 KB
pr 3 KB 2 KB
pub 2 KB 2 KB
PugMaster 2 KB 1 KB
Subset large font files66 KB0.015g

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
woff;base64,d09GRgABAAAAALGJABMAAAABdWQAAAAAAACwSAAAAUEAAAJ8AAAAAAAAAABHUE9TAACMAAAAHdQAA… ~44 KB ~27 KB
woff;base64,d09GRgABAAAAAKUMABMAAAABYXgAAAAAAACjzAAAAUAAAAJ7AAAAAAAAAABHUE9TAACEFAAAGVwAA… ~41 KB ~24 KB
graphik-italic.woff2 ~33 KB ~16 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.
View details
i.dailymail.co.uk graphik-italic.woff2
fonts.gstatic.com ea8IacM9Wef3EJPWRrHjgE4B6CnlZxHVBg3etBD7TL5-PQE.woff2
fonts.gstatic.com ea8FacM9Wef3EJPWRrHjgE4B6CnlZxHVDv79oT3ZQZQ.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
Score69%33%
Timing2.5 s1.9 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

MobileDesktop
Score1%40%
Timing9.3 s2.7 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.

MobileDesktop
Score0%0%
Timing8,330 ms2,030 ms
Speed Index

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

MobileDesktop
Score1%0%
Timing14.5 s10.2 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.

MobileDesktop
Score0%0%
Timing55.8 s23.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.

MobileDesktop
Score0%26%
Timing1,110 ms350 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.

MobileDesktop
Score87%0%
Timing2.5 s4.4 s