First visit
CO2 0.132g
SIZE 358.85 KB
Return visit
CO2 0.027g
SIZE 72.57 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
2
65.69 KB
0.024g
Script
18
96.7 KB
0.035g
Image
31
55.43 KB
0.020g
Stylesheet
1
1.32 KB
0.000g
Fetch
5
139.44 KB
0.051g
XHR
627
284 B
0.000g
History
Date
CO2
Size
06.Feb.2025
0.132g
358.85 KB
27.Nov.2024
0.201g
547.21 KB
09.Oct.2024
0.138g
375.12 KB
31.Oct.2023
0.161g
437.83 KB
25.Oct.2023
0.161g
438 KB
01.Sep.2023
0.098g
267.06 KB
11.Jul.2023
0.042g
134.88 KB
22.Mar.2023
0.099g
133.43 KB
20.Mar.2023
0.099g
133.07 KB
20.Mar.2023
0.098g
131.63 KB
20.Mar.2023
0.097g
131.27 KB
This website has been tested 13 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.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
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.
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.
Time to Interactive
0.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
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.
Speed Index
0.6 s
Speed Index shows how quickly the contents of a page are visibly populated.
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time
0.3 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.
Avoids an excessive DOM size
509 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
First Contentful Paint
0.4 s
First Contentful Paint marks the time at which the first text or image is painted.
Initial server response time was short
Root document took 30 ms
Keep the server response time for the main document short because all other requests depend on it.
Avoids enormous network payloads
Total size was 359 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Switch to green hosting
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: