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
40%
Desktop Performance
58%

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 Paint4.9 s2.8 s< 2.5 s
First Input Delay1,020 ms330 ms< 100ms
Cumulative Layout Shift0.0760.048 0.1

Tracking scripts

All the tracking scripts on the site generated ~457 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.

idgets.outbrain.com 9 104 KB
googletagmanager.com 1 44 KB
google-analytics.com 1 20 KB
idget-pixels.outbrain.com 1 577 B
odb.outbrain.com 1 6 KB
mv.outbrain.com 1 4 KB
ib.adnxs.com 5 4 KB
match.adsrvr.org 3 2 KB
beacon.krxd.net 2 888 B
aa.agkn.com 1 857 B
x.bidswitch.net 3 2 KB
dis.criteo.com 1 432 B
cm.g.doubleclick.net 7 6 KB
ps.eyeota.net 3 2 KB
loadus.exelator.com 3 3 KB
ssum-sec.casalemedia.com 2 2 KB
image8.pubmatic.com 3 3 KB
u.openx.net 2 1 KB
ups.analytics.yahoo.com 3 2 KB
cs.emxdgt.com 1 131 B
ice.360yield.com 2 1 KB
s.ad.smaato.net 1 909 B
ssbsync.smartadserver.com 1 469 B
c.bing.com 2 2 KB
sync.technoratimedia.com 1 412 B
pixel-sync.sitescout.com 2 1 KB
cms.quantserve.com 1 840 B
bh.contextweb.com 1 1 KB
sync.outbrain.com 17 2 KB
eventlog.outbrain.com 1 258 B
hbopenbid.pubmatic.com 1 198 B
microsoft-aunz-d.openx.net 1 809 B
tlx.3lift.com 1 792 B
htlb.casalemedia.com 1 777 B
partner.googleadservices.com 1 778 B
adservice.google.com 1 642 B
googleads.g.doubleclick.net 1 700 B
pippio.com 4 2 KB
sync.taboola.com 1 486 B
image2.pubmatic.com 1 397 B
secure.adnxs.com 4 5 KB
nine-a.p.adnxs.com 1 848 B
image4.pubmatic.com 1 541 B
assets.adobedtm.com 4 48 KB
connect.facebook.net 2 138 KB
facebook.com 2 656 B
sync.search.spotxchange.com 4 4 KB
usermatch.krxd.net 2 714 B
m.adnxs.com 3 3 KB
dpm.demdex.net 1 944 B
cm.everesttech.net 1 565 B
sync-tm.everesttech.net 2 1 KB
image5.pubmatic.com 1 543 B
cms.analytics.yahoo.com 1 1 KB
dmpsync.3lift.com 2 1 KB
zn1y2ema5tlxxjvbo-nineresearch.siteintercept.qualtrics.com 1 4 KB
siteintercept.qualtrics.com 2 22 KB

Opportunities

Optimise images

By optimising the following images, roughly 2 MB could be removed from the transfer size, about 29%. This would reduce the CO2 generated per page load from 1.51g grams to 1.07 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.
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F70e97ddf-c92b-4ca2-ae2e-4215f4c048e7 725 KB 11% 481 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F000068a9-a5ce-4a40-86fc-c08acbb242b8 721 KB 11% 635 KB
terrain_radar_071_960x720.jpg 165 KB 2% 116 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fbd68b6b0-c6e3-4f2d-8d14-6d971970ae0c 100 KB 1% 83 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Ff0fb609f-b71d-4b77-b4ca-763d452e3d9e 72 KB 1% 63 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Faac53c04-3721-43c0-9e9d-ea9a2e6335dd 70 KB 1% 20 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fa01d4d84-e057-42a3-9016-3bcfe4c63165 64 KB 1% 56 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F2a408d6e-3e88-4ceb-be74-a20860cc0ad1 64 KB 1% 56 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fafbd37f6-a576-4c55-96d4-3f9f022b02bf 62 KB 1% 18 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F6bfd23fc-8582-4873-9975-0bd8c7954aba 62 KB 1% 55 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fac831e38-a7c4-4dbb-a547-ff8ac2cd3af5 56 KB 1% 50 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fbc9903d3-29fb-478a-ac5d-95b053c1f193 56 KB 1% 16 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F8ed18fce-0b6a-4400-b2ff-4cd6674e7255 55 KB 1% 49 KB
image.jpg 53 KB 1% 32 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Facd0bd7f-1ace-4806-b94e-e38630b371f8 53 KB 1% 17 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F9ef58032-ca7b-4a39-a4f7-aa4f76990ff3 51 KB 1% 18 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F916bf8f9-7ed0-4a79-a6f2-8ed719da02c8 51 KB 1% 16 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F7ad46c41-5d70-42e0-b3d6-b22b61bf49c6 50 KB 1% 17 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F1700c703-10f2-4bcf-9d43-e06d0050b154 46 KB 1% 42 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F55e05412-04e8-408d-be16-9a77d105b87e 43 KB 1% 15 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F5f808834-b23b-4bb1-b60d-352d0683a522 41 KB 1% 15 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F3de9b31a-08c0-46eb-b41b-26cc6ee8bc59 39 KB 1% 14 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F7ae4504c-f5e3-4545-8b1e-7aa017bfe216 33 KB 0% 13 KB
2018412392.jpg 32 KB 0% 19 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2F1b25a4b5-4b11-4cb7-8227-c1823d6fea13 25 KB 0% 12 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fed8933ca-0263-410c-83c0-23790775a4e2 22 KB 0% 20 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fc45cccf9-2d50-4a6a-a0d4-574ae0170ab0 22 KB 0% 19 KB
https%3A%2F%2Fprod.static9.net.au%2Ffs%2Fed8933ca-0263-410c-83c0-23790775a4e2 17 KB 0% 15 KB
aca.676e2610.png 13 KB 0% 10 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.

hurme-black.woff ~31 KB ~13 KB
proximanova-bold.woff ~28 KB ~10 KB
proximanova-medium.woff ~27 KB ~10 KB
proximanova-semibold.woff ~27 KB ~10 KB
proximanova-regular.woff ~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.

Fontformat
proximanova-bold.woffwoff
proximanova-semibold.woffwoff
hurme-black.woffwoff
proximanova-medium.woffwoff

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
omny.fmopen-sans-latin-600-normal.0270e39b.woff2
omny.fmopen-sans-latin-400-normal.abd3eb12.woff2
fonts.gstatic.com6xK3dSBYKcSV-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.
MobileDesktop
Score78%91%
Timing2.2 s0.9 s

Largest Contentful Paint

MobileDesktop
Score29%38%
Timing4.9 s2.8 s

Total Blocking Time

MobileDesktop
Score4%48%
Timing2,460 ms360 ms

Cumulative Layout Shift

MobileDesktop
Score95%99%
Timing0.0760.048

Speed Index

MobileDesktop
Score0%5%
Timing18.8 s4.6 s

Time to Interactive

MobileDesktop
Score0%23%
Timing38.7 s6.3 s

Max Potential First Input Delay

MobileDesktop
Score0%29%
Timing1,020 ms330 ms

First Meaningful Paint

MobileDesktop
Score92%72%
Timing2.2 s1.2 s

Properly size images

MobileDesktop
Score50%80%
InsightPotential savings of 144 KiBPotential savings of 268 KiB

Defer offscreen images

MobileDesktop
Score36%87%
InsightPotential savings of 856 KiBPotential savings of 167 KiB

Reduce unused CSS

MobileDesktop
Score75%97%
InsightPotential savings of 34 KiBPotential savings of 25 KiB

Reduce unused JavaScript

MobileDesktop
Score0%36%
InsightPotential savings of 1,288 KiBPotential savings of 1,267 KiB

Efficiently encode images

MobileDesktop
Score75%90%
InsightPotential savings of 52 KiBPotential savings of 63 KiB

Serve images in next-gen formats

MobileDesktop
Score0%48%
InsightPotential savings of 1,604 KiBPotential savings of 1,508 KiB

Reduce initial server response time

MobileDesktop
GradeFailFail
InsightRoot document took 2,450 msRoot document took 980 ms

Use video formats for animated content

MobileDesktop
Score29%69%
InsightPotential savings of 507 KiBPotential savings of 507 KiB

Avoid serving legacy JavaScript to modern browsers

MobileDesktop
Score88%100%
InsightPotential savings of 50 KiBPotential savings of 50 KiB

Avoid enormous network payloads

MobileDesktop
Score3%4%
InsightTotal size was 6,995 KiBTotal size was 6,773 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score4%4%
Insight94 resources found95 resources found

Avoid an excessive DOM size

MobileDesktop
Score22%24%
Insight1,929 elements1,864 elements

Reduce JavaScript execution time

MobileDesktop
Score7%65%
Timing10.9 s2.5 s

Minimize main-thread work

MobileDesktop
Score0%30%
Timing17.7 s5.2 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Minimize third-party usage

MobileDesktop
GradeFailPass
InsightThird-party code blocked the main thread for 1,730 msThird-party code blocked the main thread for 170 ms

Avoid document.write()

MobileDesktop
GradeFailFail

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail