First visit
CO2 0.022g
SIZE 59.28 KB
Return visit
CO2 0.009g
SIZE 23.76 KB
First visit
CO2 0.022g
SIZE 59.28 KB
Return visit
CO2 0.009g
SIZE 23.76 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
23.76 KB
0.009g
Stylesheet
1
8.56 KB
0.003g
Script
1
4.01 KB
0.001g
Image
17
22.95 KB
0.008g
History
Date
CO2
Size
01.Jul.2025
0.022g
59.28 KB
13.Dec.2023
0.021g
57.17 KB
24.Nov.2023
0.020g
53.58 KB
21.Nov.2023
0.020g
53.54 KB
18.Nov.2023
0.025g
67.14 KB
06.Nov.2023
0.018g
50.34 KB
31.Oct.2023
0.018g
50.1 KB
31.Oct.2023
0.018g
49.82 KB
This website has been tested 8 times**
20 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.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Total size was 59 KiB
Large network payloads cost users real money and are highly correlated with long load times.
0 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.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
0.3 s
First Contentful Paint marks the time at which the first text or image is painted.
442 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Root document took 20 ms
Keep the server response time for the main document short because all other requests depend on it.
0.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
0.3 s
Speed Index shows how quickly the contents of a page are visibly populated.
0 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.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
One of the easiest things to do that instantly reduces your impact.
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: