First visit
CO2 0.249g
SIZE 803.27 KB
Return visit
CO2 0.007g
SIZE 20.98 KB
First visit
CO2 0.249g
SIZE 803.27 KB
Return visit
CO2 0.007g
SIZE 20.98 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
17.17 KB
0.005g
Image
2
374.41 KB
0.116g
Font
2
59.93 KB
0.019g
Stylesheet
2
18 KB
0.006g
Script
15
185.31 KB
0.058g
XHR
1
593 B
0.000g
Fetch
65
147.86 KB
0.046g
History
Date
CO2
Size
16.Feb.2026
0.249g
803.27 KB
13.Feb.2026
0.253g
815.82 KB
06.Feb.2026
0.235g
756.58 KB
05.Feb.2026
0.133g
428.75 KB
05.Feb.2026
0.135g
434.84 KB
05.Feb.2026
0.136g
439.21 KB
05.Feb.2026
0.136g
439.83 KB
01.Feb.2026
0.217g
698.21 KB
01.Feb.2026
0.217g
698.3 KB
01.Feb.2026
0.217g
700.19 KB
01.Feb.2026
0.256g
825.83 KB
This website has been tested 14 times**
Previous 10 test results are displayed above.
80 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.001
Cumulative Layout Shift measures the movement of visible elements within the viewport.
0.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Est savings of 27 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.
Root document took 10 ms
Keep the server response time for the main document short because all other requests depend on it.
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.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Total size was 803 KiB
Large network payloads cost users real money and are highly correlated with long load times.
1.8 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.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
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: