First visit
CO2 0.082g
SIZE 265.02 KB
Return visit
CO2 0.007g
SIZE 21.42 KB
First visit
CO2 0.082g
SIZE 265.02 KB
Return visit
CO2 0.007g
SIZE 21.42 KB
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
21.42 KB
0.007g
Other
1
439 B
0.000g
Stylesheet
2
24.89 KB
0.008g
Script
5
139.24 KB
0.043g
Image
29
79.03 KB
0.025g
History
Date
CO2
Size
25.Oct.2026
0.082g
265.02 KB
24.Oct.2026
0.082g
265.17 KB
10.Oct.2026
0.094g
301.46 KB
01.Oct.2026
0.084g
270.89 KB
22.Sep.2026
0.082g
265.21 KB
04.Aug.2026
0.087g
279.26 KB
28.Jul.2026
0.085g
272.61 KB
27.Jul.2026
0.085g
272.5 KB
27.Jul.2026
0.087g
279.06 KB
27.Jul.2026
0.101g
326.26 KB
26.Jul.2026
0.160g
515.44 KB
This website has been tested 12 times**
Previous 10 test results are displayed above.
120 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
0.066
Cumulative Layout Shift measures the movement of visible elements within the viewport.
0.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Est savings of 18 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
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.
0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Est savings of 46 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
10 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.
Root document took 10 ms
Keep the server response time for the main document short because all other requests depend on it.
30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.4 s
First Contentful Paint marks the time at which the first text or image is painted.
0.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Total size was 265 KiB
Large network payloads cost users real money and are highly correlated with long load times.
0.6 s
Speed Index shows how quickly the contents of a page are visibly populated.
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: