First visit
CO2 0.141g
SIZE 383.67 KB
Return visit
CO2 0.007g
SIZE 19.12 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
19.12 KB
0.007g
Font
2
112.09 KB
0.041g
Image
16
18.48 KB
0.007g
Stylesheet
1
15.06 KB
0.006g
Script
16
176.94 KB
0.065g
Fetch
6
41.32 KB
0.015g
Preflight
1
667 B
0.000g
History
Date
CO2
Size
01.Jul.2025
0.141g
383.67 KB
27.Mar.2024
0.145g
395.33 KB
26.Mar.2024
0.143g
390.79 KB
15.Mar.2024
0.148g
402.74 KB
15.Mar.2024
0.148g
403.89 KB
15.Mar.2024
0.151g
411.42 KB
13.Mar.2024
0.151g
412.88 KB
13.Mar.2024
0.150g
409.47 KB
07.Mar.2024
0.149g
406.72 KB
07.Mar.2024
0.152g
414.35 KB
29.Feb.2024
0.152g
414.85 KB
This website has been tested 35 times**
Previous 10 test results are displayed above.
Core Web Vitals
Max Potential First Input Delay
110 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.012
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
First Contentful Paint
0.3 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 190 ms
Keep the server response time for the main document short because all other requests depend on it.
JavaScript execution time
0.4 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
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.
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.
Speed Index
0.8 s
Speed Index shows how quickly the contents of a page are visibly populated.
Avoids enormous network payloads
Total size was 384 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Avoids an excessive DOM size
311 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Minimizes main-thread work
0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Total Blocking Time
50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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: