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
60%
Desktop Performance
79%

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 Paint3.3 s1.0 s< 2.5 s
First Input Delay240 ms360 ms< 100ms
Cumulative Layout Shift00.008 0.1

Tracking scripts

All the tracking scripts on the site generated ~149 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 127 KB
google-analytics.com 3 21 KB
stats.g.doubleclick.net 2 581 B
analytics.google.com 1 0 B

Opportunities

Remove autoplaying or preloaded media files

By removing 4 autoplaying or preloaded videos, roughly 1.2 KB could be removed from the page load.

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

1241167344.mp4 1 KB 0%
1241167344.mp4 0 B 0%
1241167090.mp4 0 B 0%
1241167090.mp4 0 B 0%

Optimise images

By optimising the following images, roughly 12 MB could be removed from the transfer size, about 117%. This would reduce the CO2 generated per page load from 2.33g grams to -0.4 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.
SellMyCarRecentWorkHome.png 4 MB 39% 3 MB
SellMyCarRecentWorkHome.png 4 MB 39% 3 MB
HertzRecentWorkHome.png 2 MB 24% 2 MB
HertzRecentWorkHome.png 2 MB 24% 2 MB
pano.jpg 498 KB 5% 159 KB
pano.jpg 498 KB 5% 159 KB
Testimonial-Banner_Hertz-Final.png 465 KB 4% 389 KB
cover.jpg 399 KB 4% 138 KB
cover.jpg 399 KB 4% 138 KB
paper.png 344 KB 3% 319 KB
trophy.png 175 KB 2% 156 KB
payload 40 KB 0% 17 KB
payload 32 KB 0% 15 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.
HostFont
fonts.gstatic.comS6u9w4BMUTPHh50XSwiPGQ3q5d0.woff2
fonts.gstatic.comS6uyw4BMUTPHjx4wXiWtFCc.woff2
fonts.gstatic.comS6u9w4BMUTPHh6UVSwiPGQ3q5d0.woff2
fonts.gstatic.comS6u9w4BMUTPHh7USSwiPGQ3q5d0.woff2
fonts.gstatic.comS6u8w4BMUTPHjxsAXC-qNiXg7Q.woff2
fonts.gstatic.comKFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
fonts.gstatic.comKFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
fonts.gstatic.comKFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
fonts.gstatic.comKFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
fonts.gstatic.comKFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
fonts.gstatic.comKFOlCnqEu92Fr1MmEU9fBBc4AMP6lQ.woff2
fonts.gstatic.comKFOlCnqEu92Fr1MmYUtfBBc4AMP6lQ.woff2
fonts.gstatic.comKFOlCnqEu92Fr1MmYUtfBBc4AMP6lQ.woff2

Replace jQuery and jQuery libraries with more modern code

jQuery is a popular and widely-used JavaScript library that simplifies web development by providing a set of tools and functions to interact with HTML documents, handle events, create animations, and make asynchronous HTTP requests.

In the past, jQuery was a very popular choice for web development because it simplified many common tasks and provided a consistent and cross-browser-compatible API. However, with the advancement of modern web technologies and improvements in browser capabilities, the need for jQuery has decreased.

Many modern web frameworks and libraries, such as React and Angular, provide their own set of tools for handling common tasks and interacting with the DOM, making jQuery less necessary in many cases. The Javascript engine in modern browsers have also become more consistent in the feature implementations often eliminating the need for a library like jQuery.

jQuery represents an opportunity because:

  1. Performance: While jQuery is a powerful and useful library, it can slow down website performance due to its large size and complex code. Modern browsers have also improved their native support for many of the features that jQuery provides, reducing the need for it.
  2. Maintainability: jQuery code can be difficult to maintain and update, particularly as web technologies evolve and change. This can make it harder for developers to keep up with best practices and standards for web development.
  3. Accessibility: Some jQuery plugins and features can create accessibility issues, particularly for users who rely on assistive technologies. This can make it harder for people with disabilities to use and access websites.
jquery.js 39 KB
jquery-migrate.min.js 5 KB

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
Score62%97%
Timing2.6 s0.7 s

Largest Contentful Paint

MobileDesktop
Score69%94%
Timing3.3 s1.0 s

Total Blocking Time

MobileDesktop
Score27%37%
Timing1,010 ms430 ms

Speed Index

MobileDesktop
Score35%92%
Timing6.8 s1.2 s

Time to Interactive

MobileDesktop
Score6%83%
Timing15.6 s2.8 s

Max Potential First Input Delay

MobileDesktop
Score53%23%
Timing240 ms360 ms

First Meaningful Paint

MobileDesktop
Score80%96%
Timing2.8 s0.8 s

Eliminate render-blocking resources

MobileDesktop
Score40%68%
InsightPotential savings of 1,630 msPotential savings of 420 ms

Properly size images

MobileDesktop
Score24%4%
InsightPotential savings of 618 KiBPotential savings of 5,799 KiB

Reduce unused CSS

MobileDesktop
Score48%87%
InsightPotential savings of 86 KiBPotential savings of 84 KiB

Reduce unused JavaScript

MobileDesktop
Score0%47%
InsightPotential savings of 625 KiBPotential savings of 612 KiB

Serve images in next-gen formats

MobileDesktop
Score0%0%
InsightPotential savings of 1,720 KiBPotential savings of 6,574 KiB

Avoid enormous network payloads

MobileDesktop
Score35%0%
InsightTotal size was 4,500 KiBTotal size was 10,443 KiB

Uses efficient cache policy on static assets

MobileDesktop
Score95%95%
Insight10 resources found9 resources found

Avoids an excessive DOM size

MobileDesktop
Score99%99%
Insight477 elements476 elements

Reduce JavaScript execution time

MobileDesktop
Score36%69%
Timing4.6 s2.3 s

Minimize main-thread work

MobileDesktop
Score9%59%
Timing8.0 s3.5 s

Ensure text remains visible during webfont load

MobileDesktop
GradeFailFail

Reduce the impact of third-party code

MobileDesktop
GradeFailFail
InsightThird-party code blocked the main thread for 1,350 msThird-party code blocked the main thread for 690 ms

Uses passive listeners to improve scrolling performance

MobileDesktop
GradeFailPass

Image elements do not have explicit width and height

MobileDesktop
GradeFailFail