First visit
CO2 0.074g
SIZE 239.57 KB
Return visit
CO2 0.017g
SIZE 55.74 KB
Emissions calculator
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
55.36 KB
0.017g
Font
1
29.53 KB
0.009g
Other
1
433 B
0.000g
Script
25
89.3 KB
0.028g
Stylesheet
6
40.28 KB
0.012g
Image
15
24 KB
0.007g
Fetch
1
699 B
0.000g
History
Date
CO2
Size
02.Jul.2026
0.074g
239.57 KB
30.Apr.2026
0.073g
234.09 KB
20.Nov.2025
0.073g
233.79 KB
21.Sep.2025
0.073g
234.19 KB
14.Aug.2025
0.073g
234.3 KB
01.Jul.2025
0.073g
234.29 KB
01.Jun.2025
0.075g
242.08 KB
22.Jan.2025
0.075g
242.48 KB
04.Oct.2024
0.073g
236.76 KB
29.Jun.2024
0.073g
236.33 KB
28.May.2024
0.074g
237.76 KB
This website has been tested 50 times**
Previous 10 test results are displayed above.
Core Web Vitals
Max Potential First Input Delay
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
Largest Contentful Paint
0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Time to Interactive
0.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
JavaScript execution time
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
First Contentful Paint
0.3 s
First Contentful Paint marks the time at which the first text or image is painted.
Avoids enormous network payloads
Total size was 240 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Speed Index
0.4 s
Speed Index shows how quickly the contents of a page are visibly populated.
Initial server response time was short
Root document took 10 ms
Keep the server response time for the main document short because all other requests depend on it.
Network Round Trip Times
60 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.
Minimizes main-thread work
0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Server Backend Latencies
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.
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: