First visit
CO2 0.921g
SIZE 2.45 MB
Return visit
CO2 0.246g
SIZE 670.01 KB
First visit
CO2 0.921g
SIZE 2.45 MB
Return visit
CO2 0.246g
SIZE 670.01 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
12.56 KB
0.005g
Script
14
1.28 MB
0.481g
Font
2
110.79 KB
0.041g
Stylesheet
2
184.72 KB
0.068g
Image
12
702.06 KB
0.258g
XHR
2
3.01 KB
0.001g
Other
3
84.49 KB
0.031g
Fetch
12
100.84 KB
0.037g
History
Date
CO2
Size
01.Oct.2026
0.921g
2.45 MB
22.Jul.2026
0.844g
2.25 MB
22.Jul.2026
0.843g
2.24 MB
05.Mar.2026
0.630g
1.68 MB
03.Apr.2025
1.976g
5.26 MB
28.Feb.2024
0.820g
2.18 MB
19.May.2022
1.290g
1.54 MB
This website has been tested 7 times**
170 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.005
Cumulative Layout Shift measures the movement of visible elements within the viewport.
1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Est savings of 540 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
Root document took 0 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.
2.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Total size was 2,509 KiB
Large network payloads cost users real money and are highly correlated with long load times.
490 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
20 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.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
0.8 s
Speed Index shows how quickly the contents of a page are visibly populated.
1.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Est savings of 194 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
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: