First visit
CO2 0.020g
SIZE 64.58 KB
Return visit
CO2 0.016g
SIZE 51.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
2.51 KB
0.001g
Stylesheet
1
2.89 KB
0.001g
Script
2
5.67 KB
0.002g
Fetch
4
3.39 KB
0.001g
XHR
3
3.13 KB
0.001g
Image
3
46.98 KB
0.015g
History
Date
CO2
Size
12.Apr.2025
0.020g
64.58 KB
26.Feb.2025
0.006g
18.68 KB
03.Feb.2025
0.020g
64.74 KB
31.Jan.2025
0.020g
65.58 KB
28.Jan.2025
0.020g
65.45 KB
28.Jan.2025
0.020g
65.46 KB
23.Jan.2025
0.008g
25.84 KB
02.Jan.2025
0.008g
25.26 KB
22.Dec.2024
0.008g
25.92 KB
13.Dec.2023
0.041g
131.89 KB
25.Oct.2023
0.017g
54.61 KB
This website has been tested 12 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
Cumulative Layout Shift
0.877
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
0.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
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.
Time to Interactive
0.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
First Contentful Paint
0.2 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.
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.
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.
Initial server response time was short
Root document took 110 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 65 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Serve static assets with an efficient cache policy
6 resources found
A long cache lifetime can speed up repeat visits to your page.
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.
Avoids an excessive DOM size
72 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
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: