First visit
CO2 0.155g
SIZE 500.41 KB
Return visit
CO2 0.029g
SIZE 94.56 KB
First visit
CO2 0.155g
SIZE 500.41 KB
Return visit
CO2 0.029g
SIZE 94.56 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
Other
1
300 B
0.000g
Document
1
6.55 KB
0.002g
Font
2
42.54 KB
0.013g
Script
4
169.65 KB
0.053g
Stylesheet
2
15.32 KB
0.005g
Image
3
257.33 KB
0.080g
XHR
2
7.93 KB
0.002g
Fetch
1
808 B
0.000g
History
Date
CO2
Size
19.Sep.2025
0.155g
500.41 KB
18.Aug.2025
0.154g
496.04 KB
13.Aug.2025
0.154g
497.25 KB
01.Jul.2025
0.154g
495.01 KB
27.May.2025
0.152g
490.14 KB
20.Dec.2024
0.147g
472.17 KB
20.Dec.2024
0.161g
518.71 KB
20.Dec.2024
0.006g
18.99 KB
This website has been tested 8 times**
30 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.004
Cumulative Layout Shift measures the movement of visible elements within the viewport.
0.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Total size was 500 KiB
Large network payloads cost users real money and are highly correlated with long load times.
0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Est savings of 240 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Est savings of 190 ms
Redirects introduce additional delays before the page can be loaded.
153 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
Root document took 20 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.
60 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.
Est savings of 53 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
9 resources found
A long cache lifetime can speed up repeat visits to your page.
2.0 s
Speed Index shows how quickly the contents of a page are visibly populated.
0.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
0.1 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: