First visit
CO2 0.095g
SIZE 304.88 KB
Return visit
CO2 0.013g
SIZE 42.2 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
23.04 KB
0.007g
Other
1
700 B
0.000g
Stylesheet
1
9.4 KB
0.003g
Script
3
124.01 KB
0.038g
Image
6
54.9 KB
0.017g
Fetch
2
1.66 KB
0.001g
Font
4
90.85 KB
0.028g
XHR
1
339 B
0.000g
History
Date
CO2
Size
01.Jul.2025
0.095g
304.88 KB
29.May.2025
0.094g
303.02 KB
14.Feb.2025
0.177g
569.23 KB
09.Dec.2024
0.167g
536.89 KB
05.Dec.2024
0.166g
533.57 KB
03.Dec.2024
0.165g
531.79 KB
03.Dec.2024
0.165g
532.14 KB
02.Dec.2024
0.325g
1.02 MB
15.Nov.2024
0.335g
1.05 MB
15.Nov.2024
0.335g
1.05 MB
This website has been tested 10 times**
Core Web Vitals
Max Potential First Input Delay
50 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
Cumulative Layout Shift
0.004
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
0.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Time to Interactive
0.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Avoids enormous network payloads
Total size was 305 KiB
Large network payloads cost users real money and are highly correlated with long load times.
First Contentful Paint
0.3 s
First Contentful Paint marks the time at which the first text or image is painted.
Speed Index
0.4 s
Speed Index shows how quickly the contents of a page are visibly populated.
Network Round Trip 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.
Initial server response time was short
Root document took 80 ms
Keep the server response time for the main document short because all other requests depend on it.
Serve static assets with an efficient cache policy
11 resources found
A long cache lifetime can speed up repeat visits to your page.
Minimizes main-thread work
0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Server Backend Latencies
40 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.
Avoids an excessive DOM size
270 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
JavaScript execution time
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: