First visit
CO2 0.075g
SIZE 242.48 KB
Return visit
CO2 0.018g
SIZE 57.71 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
56.16 KB
0.017g
Font
1
29.76 KB
0.009g
Other
1
454 B
0.000g
Script
25
86.61 KB
0.027g
Stylesheet
6
41.65 KB
0.013g
Image
15
27.19 KB
0.008g
XHR
1
690 B
0.000g
History
Date
CO2
Size
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
29.Jan.2024
0.071g
227.81 KB
14.Jan.2024
0.070g
226.39 KB
02.Jan.2024
0.070g
224.53 KB
02.Jan.2024
0.070g
224.62 KB
26.Dec.2023
0.070g
224.5 KB
14.Dec.2023
0.070g
224.14 KB
01.Dec.2023
0.073g
236.75 KB
This website has been tested 43 times**
Previous 10 test results are displayed above.
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
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.
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.
First Contentful Paint
0.4 s
First Contentful Paint marks the time at which the first text or image is painted.
Avoid an excessive DOM size
963 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Network Round Trip Times
100 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 160 ms
Keep the server response time for the main document short because all other requests depend on it.
Minimizes main-thread work
0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
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.
Serve static assets with an efficient cache policy
2 resources found
A long cache lifetime can speed up repeat visits to your page.
Speed Index
0.5 s
Speed Index shows how quickly the contents of a page are visibly populated.
Avoids enormous network payloads
Total size was 242 KiB
Large network payloads cost users real money and are highly correlated with long load times.
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: