First visit
CO2 0.012g
SIZE 37.94 KB
Return visit
CO2 0.001g
SIZE 3.87 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
Other
1
411 B
0.000g
Document
1
3.67 KB
0.001g
Stylesheet
1
4.8 KB
0.001g
Image
3
20.18 KB
0.006g
Script
2
4.06 KB
0.001g
Fetch
1
1.71 KB
0.001g
XHR
3
3.13 KB
0.001g
History
Date
CO2
Size
01.Jul.2025
0.012g
37.94 KB
01.Jul.2025
0.012g
37.94 KB
01.Jul.2025
0.012g
37.94 KB
01.Jul.2025
0.012g
37.89 KB
25.Jun.2025
0.012g
37.91 KB
25.Jun.2025
0.012g
37.93 KB
25.Jun.2025
0.012g
37.93 KB
25.Jun.2025
0.012g
37.93 KB
25.Jun.2025
0.012g
37.94 KB
24.Jun.2025
0.012g
37.92 KB
24.Jun.2025
0.012g
37.92 KB
This website has been tested 152 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.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Time to Interactive
0.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
First Contentful Paint
0.4 s
First Contentful Paint marks the time at which the first text or image is painted.
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.
Avoids an excessive DOM size
93 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
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 40 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 38 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Minimizes main-thread work
0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Network Round Trip Times
10 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.
Avoid multiple page redirects
Est savings of 230 ms
Redirects introduce additional delays before the page can be loaded.
Serve static assets with an efficient cache policy
1 resource found
A long cache lifetime can speed up repeat visits to your page.
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: