First visit
CO2 0.031g
SIZE 99.98 KB
Return visit
CO2 0.008g
SIZE 26.24 KB
First visit
CO2 0.031g
SIZE 99.98 KB
Return visit
CO2 0.008g
SIZE 26.24 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
18.71 KB
0.006g
Stylesheet
2
5.86 KB
0.002g
Script
7
47.38 KB
0.015g
Image
6
23.95 KB
0.007g
Fetch
1
976 B
0.000g
XHR
3
3.13 KB
0.001g
History
Date
CO2
Size
14.Aug.2025
0.031g
99.98 KB
01.Jul.2025
0.026g
84.97 KB
26.Oct.2023
0.026g
83.22 KB
22.Mar.2023
0.062g
84.05 KB
14.Nov.2022
0.059g
80.23 KB
08.Nov.2022
0.060g
80.44 KB
07.Nov.2022
0.067g
90.27 KB
07.Nov.2022
0.067g
90.27 KB
28.Oct.2022
0.066g
88.83 KB
28.Oct.2022
0.064g
86.14 KB
26.Oct.2022
0.095g
127.98 KB
This website has been tested 21 times**
Previous 10 test results are displayed above.
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.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
0.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
0.6 s
Speed Index shows how quickly the contents of a page are visibly populated.
13 resources found
A long cache lifetime can speed up repeat visits to your page.
316 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
0.3 s
First Contentful Paint marks the time at which the first text or image is painted.
20 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
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.
0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Total size was 100 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Root document took 50 ms
Keep the server response time for the main document short because all other requests depend on it.
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: