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 Paint4.7 s6.5 s< 2.5 s
First Input Delay610 ms120 ms< 100ms
Cumulative Layout Shift0.0060.003 0.1

Tracking scripts

All the tracking scripts on the site generated ~684 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 8 219 KB 4 355 KB 3 23 KB 3 80 KB 2 0 B 2 576 B 4 5 KB 1 538 B 1 557 B 3 1 KB


Optimise images14 MB3.195g

By optimising the following images, roughly 14 MB could be removed from the transfer size, about 78%. This would reduce the CO2 generated per page load from 4.12g grams to 0.93 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
GP24_002_Web_Tiles_FeaturedContent-1.jpg 603 KB 3% 514 KB
FOR-GP24-MENU-TICKETS-Park_Pass-2.png 518 KB 3% 470 KB
FOR-GP23-MENU-Access23.png 492 KB 3% 461 KB
FOR-GP24-MENU-TICKETS-Authorised_Resellers.png 477 KB 3% 443 KB
FOR-GP23-MENU-FAN_ZONE-Driver_Profiles-V2.png 475 KB 3% 438 KB
FOR-GP23-MENU-Circuit_Map.png 474 KB 3% 439 KB
FOR-GP23-MENU-EVENT-Getting_Here.png 474 KB 3% 444 KB
FOR-GP24-MENU-HOSPITALITY-Suites.png 469 KB 3% 440 KB
FOR-GP24-MENU-TICKETS-FAQs.png 468 KB 3% 437 KB
FOR-GP23-MENU-Accessibility.png 459 KB 2% 425 KB
FOR-GP24-MENU-TICKETS-Grandstand.png 458 KB 2% 424 KB
FOR-GP23-MENU-Event-On_Track.png 448 KB 2% 422 KB
FOR-GP24-MENU-HOSPITALITY-Private_and_Customised.png 446 KB 2% 420 KB
FOR-GP24-MENU-TICKETS-Hospitality-2.png 440 KB 2% 408 KB
FOR-GP-MENU-F1101.png 438 KB 2% 413 KB
FOR-MENU-F1-Experiences.png 434 KB 2% 412 KB
FOR-GP24-MENU-Accessibility.png 434 KB 2% 405 KB
FOR-GP24-MENU-Already_Booked_FAQ.png 434 KB 2% 404 KB
FOR-GP24-MENU-Tickets.png 432 KB 2% 401 KB
FOR-MENU-News.png 428 KB 2% 404 KB
FOR-GP24-MENU-Spectate_In_Style.png 421 KB 2% 402 KB
FOR-GP24-MENU-Culinary_Offering.png 414 KB 2% 391 KB
FOR-GP24-MENU-HOSPITALITY-Meetings_Events_and_Incentives.png 412 KB 2% 389 KB
FOR-GP24-MENU-TICKETS-Select_Your_Ticket.png 407 KB 2% 381 KB
FOR-GP24-MENU-FAN_ZONE-Driver_Standings.png 400 KB 2% 371 KB
FOR-MENU-Video.png 398 KB 2% 378 KB
FOR-GP23-MENU-Discover_Melbourne.png 396 KB 2% 373 KB
FOR-GP23-MENU-Event-Off_Track.png 395 KB 2% 375 KB
13341716928398768998 381 KB 2% 336 KB
FOR-GP24-MENU-TICKETS-Tips_and_Tricks.png 374 KB 2% 347 KB
FOR-GP24-HOMEPAGE-SLIDER-Remaining_Tickets.jpg 347 KB 2% 178 KB
FOR-GP23-MENU-FAN_ZONE-Season_Calendar-V2.png 347 KB 2% 323 KB
FOR-GP24-MAIN_STAGE_MUSIC.png 342 KB 2% 318 KB
FOR-GP24-HOMEPAGE-MUSIC-Headliners.gif 327 KB 2% 83 KB
FOR-GP23-MENU-Merchandise.png 280 KB 2% 263 KB
FOR-GP24-HOMEPAGE-SLIDER-Merchandise.jpg 279 KB 2% 146 KB
FOR-GP24-HOMEPAGE-TICKETS-Main-N.jpg 201 KB 1% 165 KB
FOR-GP24-HOMEPAGE-TICKETS-Park_Pass-N.jpg 77 KB 0% 61 KB
17054615262646215662 72 KB 0% 60 KB
FOR-GP24-HOMEPAGE-Motorsport_Is_Dangerous-Desktop.jpg 70 KB 0% 57 KB
FOR-GP24-HOMEPAGE-Motorsport_Is_Dangerous-Mobile.jpg 67 KB 0% 55 KB
FOR-GP24-HOMEPAGE-TICKETS-Grandstands-N.jpg 60 KB 0% 49 KB
FOR-GP24-HOMEPAGE-TICKETS-Hospitality-N.jpg 51 KB 0% 41 KB
FOR-GP24-HOMEPAGE-BUTTON-Search_Tickets-767x50-N.png 46 KB 0% 43 KB
FOR-PARTNERS-Mars-logo.png 24 KB 0% 20 KB
FOR-GP24-HOMEPAGE-ICONS-Newsletter-N.png 19 KB 0% 18 KB
FOR-GP24-PARTNERS-LOGO-Shannons_Insurance.png 15 KB 0% 11 KB
70.png 13 KB 0% 10 KB
FOR-PARTNERS-MSS-Security-Logo.png 13 KB 0% 9 KB
FOR-GP24-PARTNERS-LOGO-Bunderberg_Rum2.png 12 KB 0% 9 KB
Replace inlined font files

There is 1 inlined font that should converted to a subresource.

Subset large font files58 KB0.013g

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
rolexfont-regular-webfont.woff ~45 KB ~28 KB
Formula1-Display-Bold.woff2 ~25 KB ~8 KB
Formula1-Display-Bold.woff2 ~25 KB ~8 KB
Formula1-Display-Regular.woff2 ~25 KB ~7 KB
Formula1-Display-Regular.woff2 ~25 KB ~7 KB
Convert font files to woff222 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
rolexfont-regular-webfont.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 NaPecZTIAOhVxoMyOr9n_E7fdMPmDaZRbrw.woff2 NaPDcZTIAOhVxoMyOr9n_E7ffHjDGItzY5abuWI.woff2 NaPDcZTIAOhVxoMyOr9n_E7ffBzCGItzY5abuWI.woff2 rolexfont-regular-webfont.woff
Replace jQuery and jQuery libraries with more modern code198 KB0.04g

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.
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.9 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

Timing4.7 s6.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.

Timing2,720 ms250 ms
Speed Index

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

Timing14.8 s5.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.

Timing25.5 s6.6 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.

Timing610 ms120 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.

Timing7.3 s2.3 s