First visit
CO2 0.082g
SIZE 263.05 KB
Return visit
CO2 0.015g
SIZE 49.81 KB
First visit
CO2 0.082g
SIZE 263.05 KB
Return visit
CO2 0.015g
SIZE 49.81 KB
40%
60%
Total: per month
This is equivalent to: Driving miles in a Tesla Model S Watching hours of Netflix (in HD)
At least trees would be needed to offset the CO2 in a year
Page breakdown
Type
Requests
Size
CO2
Document
1
29.3 KB
0.009g
Stylesheet
3
57.02 KB
0.018g
Script
5
101.03 KB
0.031g
Image
13
68.46 KB
0.021g
Fetch
1
964 B
0.000g
XHR
2
6.3 KB
0.002g
History
Date
CO2
Size
17.Dec.2024
0.082g
263.05 KB
28.Nov.2024
0.092g
295.76 KB
This website has been tested 2 times**
60 ms
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
0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
17 resources found
A long cache lifetime can speed up repeat visits to your page.
0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Total size was 263 KiB
Large network payloads cost users real money and are highly correlated with long load times.
1,569 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Potential savings of 56 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
0.3 s
First Contentful Paint marks the time at which the first text or image is painted.
10 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance.
0.7 s
Speed Index shows how quickly the contents of a page are visibly populated.
0.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it.
10 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance.
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Notes
* These are assets not hosted on the same domain e.g. tracking scripts, iframe embeds, or files hosted on a CDN.
** This was only counted from 11.Apr.2021.
These measurements are for each new visitor, for returning visitors the footprint would be lower based on caching mechanisms.
Our brackets for the ratings: