First visit
CO2 1.900g
SIZE 5.06 MB
Return visit
CO2 0.074g
SIZE 200.34 KB
First visit
CO2 1.900g
SIZE 5.06 MB
Return visit
CO2 0.074g
SIZE 200.34 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
2
194.61 KB
0.071g
Stylesheet
9
104.32 KB
0.038g
Script
17
362.32 KB
0.133g
Image
307
3.77 MB
1.418g
XHR
16
17.79 KB
0.007g
Fetch
1
713 B
0.000g
Font
20
632.25 KB
0.232g
Other
2
1.05 KB
0.000g
Preflight
1
671 B
0.000g
History
Date
CO2
Size
04.Feb.2026
1.900g
5.06 MB
20.Aug.2025
1.790g
4.77 MB
26.Feb.2025
0.781g
2.08 MB
11.Jan.2025
0.539g
1.44 MB
11.Dec.2024
0.958g
2.55 MB
02.Dec.2024
1.484g
3.95 MB
20.Nov.2024
0.810g
2.16 MB
03.Nov.2024
0.739g
1.97 MB
21.Oct.2024
2.243g
7.06 MB
18.Oct.2024
0.602g
1.6 MB
14.Oct.2024
0.593g
1.58 MB
This website has been tested 47 times**
Previous 10 test results are displayed above.
130 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.387
Cumulative Layout Shift measures the movement of visible elements within the viewport.
1.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
0.8 s
First Contentful Paint marks the time at which the first text or image is painted.
Est savings of 12 KiB
Minifying JavaScript files can reduce payload sizes and script parse time.
1.9 s
Speed Index shows how quickly the contents of a page are visibly populated.
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.
3.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Root document took 640 ms
Keep the server response time for the main document short because all other requests depend on it.
70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
2.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
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.
1.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Total size was 5,178 KiB
Large network payloads cost users real money and are highly correlated with long load times.
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: