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
52%
Desktop Performance
90%

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 Paint7.3 s1.9 s< 2.5 s
First Input Delay270 ms80 ms< 100ms
Cumulative Layout Shift0.0770.059 0.1

Tracking scripts

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

googletagmanager.com 2 159 KB
google-analytics.com 2 21 KB
snap.licdn.com 1 5 KB
connect.facebook.net 2 138 KB
analytics.google.com 1 0 B
stats.g.doubleclick.net 2 577 B
cdn.linkedin.oribi.io 1 457 B
px.ads.linkedin.com 3 3 KB
google.com 1 557 B
linkedin.com 1 2 KB
facebook.com 2 328 B
in.hotjar.com 1 407 B
pixel-geo.prfct.co 10 5 KB
secure.adnxs.com 2 2 KB
ups.analytics.yahoo.com 2 1 KB
pixel.rubiconproject.com 1 767 B
cm.g.doubleclick.net 2 2 KB
us-u.openx.net 2 887 B

Opportunities

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.

silka-bold-webfont.woff2 ~28 KB ~10 KB
silka-semibold-webfont.woff2 ~28 KB ~10 KB
silka-regular-webfont.woff2 ~26 KB ~9 KB

Largest Contentful Paint

MobileDesktop
Score5%67%
Timing7.3 s1.9 s

Total Blocking Time

MobileDesktop
Score47%100%
Timing640 ms30 ms

Cumulative Layout Shift

MobileDesktop
Score95%98%
Timing0.0770.059

Speed Index

MobileDesktop
Score32%85%
Timing7.0 s1.4 s

Time to Interactive

MobileDesktop
Score23%97%
Timing10.5 s1.8 s

Max Potential First Input Delay

MobileDesktop
Score45%98%
Timing270 ms80 ms

First Meaningful Paint

MobileDesktop
Score21%77%
Timing5.6 s1.2 s

Properly size images

MobileDesktop
Score67%90%
InsightPotential savings of 27 KiBPotential savings of 301 KiB

Defer offscreen images

MobileDesktop
Score75%100%
InsightPotential savings of 15 KiB

Reduce unused JavaScript

MobileDesktop
Score27%62%
InsightPotential savings of 394 KiBPotential savings of 393 KiB

Serve static assets with an efficient cache policy

MobileDesktop
Score44%44%
Insight9 resources found9 resources found

Avoids an excessive DOM size

MobileDesktop
Score98%98%
Insight583 elements583 elements

JavaScript execution time

MobileDesktop
Score51%97%
Timing3.4 s0.8 s

Minimize main-thread work

MobileDesktop
Score9%60%
Timing8.1 s3.5 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Largest Contentful Paint image was lazily loaded

MobileDesktop
GradeFailFail

Does not use passive listeners to improve scrolling performance

MobileDesktop
GradeFailFail

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail