First visit
CO2 0.109g
SIZE 350.61 KB
Return visit
CO2 0.008g
SIZE 26.35 KB
First visit
CO2 0.109g
SIZE 350.61 KB
Return visit
CO2 0.008g
SIZE 26.35 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
24.34 KB
0.008g
Stylesheet
3
10.94 KB
0.003g
Script
15
111.12 KB
0.034g
Image
9
200.44 KB
0.062g
Fetch
2
2.56 KB
0.001g
XHR
1
1.21 KB
0.000g
History
Date
CO2
Size
12.Jun.2025
0.109g
350.61 KB
07.Jun.2025
0.109g
350.46 KB
07.May.2025
0.070g
225.93 KB
16.Apr.2025
0.067g
216.3 KB
16.Apr.2025
0.223g
719.54 KB
03.Apr.2025
0.062g
200.6 KB
03.Apr.2025
0.576g
1.81 MB
20.Mar.2025
0.003g
10.45 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.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Est savings of 23 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
229 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
0.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Total size was 351 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.
Est savings of 166 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
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.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
2 resources found
A long cache lifetime can speed up repeat visits to your page.
Root document took 540 ms
Keep the server response time for the main document short because all other requests depend on it.
0.9 s
Speed Index shows how quickly the contents of a page are visibly populated.
0.3 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.
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: