https://osstudios.gg

The Index

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
94%
Desktop Performance
99%

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
DesktopPass

CWV Breakdown

VitalMobileDesktopTarget
Largest Contentful Paint2.7 s0.7 s< 2.5 s
First Input Delay100 ms130 ms< 100ms
Cumulative Layout Shift00 0.1

Tracking scripts

All the tracking scripts on the site generated ~257 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
googletagmanager.com 2 256 KB
google-analytics.com 1 796 B

Opportunities

Remove autoplaying or preloaded media files2 videos0.0 B

By removing 2 autoplaying or preloaded videos, roughly 0.0 B could be removed from the page load.

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

View details
fOS-X-Nomobo-4k-2_1.mp4 0 B 0%
fOS-X-Nomobo-4k-2_1.mp4 0 B 0%
Optimise images2 KB0g

By optimising the following images, roughly 2 KB could be removed from the transfer size, about 0%. This would reduce the CO2 generated per page load from 0.18g grams to 0.18 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
Screenshot-2026-02-18-at-2.35.19-PM-1024x562.png 246 KB 12% 2 KB
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
Score85%99%
Timing2.7 s0.7 s
Speed Index

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

MobileDesktop
Score78%95%
Timing4.2 s1.1 s
Forced reflow

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

MobileDesktop
Score0%0%
LCP request discovery

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

MobileDesktop
Score0%0%
Network dependency tree

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

MobileDesktop
Score0%0%
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
Score89%99%
Timing3.9 s1.4 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
Score97%90%
Timing100 ms130 ms