First visit
CO2 1.137g
SIZE 3.58 MB
Return visit
CO2 0.798g
SIZE 2.51 MB
First visit
CO2 1.137g
SIZE 3.58 MB
Return visit
CO2 0.798g
SIZE 2.51 MB
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
14.55 KB
0.005g
Stylesheet
5
10.59 KB
0.003g
Script
16
675.28 KB
0.210g
Image
21
365.77 KB
0.113g
Media
1
2.49 MB
0.790g
Font
3
47.71 KB
0.015g
Fetch
7
4.43 KB
0.001g
History
Date
CO2
Size
16.Sep.2026
1.137g
3.58 MB
07.Apr.2025
1.042g
3.28 MB
11.Jul.2024
1.025g
3.23 MB
24.Jun.2024
0.999g
3.14 MB
29.Aug.2023
0.218g
702.89 KB
10.Jul.2023
0.181g
582.01 KB
20.Apr.2023
0.396g
534.74 KB
16.Feb.2023
0.426g
574.37 KB
08.Jun.2022
0.278g
375.56 KB
31.May.2022
0.278g
374.85 KB
31.May.2022
6.216g
8.19 MB
This website has been tested 12 times**
Previous 10 test results are displayed above.
140 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.008
Cumulative Layout Shift measures the movement of visible elements within the viewport.
0.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
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.
0.7 s
First Contentful Paint marks the time at which the first text or image is painted.
Root document took 20 ms
Keep the server response time for the main document short because all other requests depend on it.
Total size was 3,665 KiB
Large network payloads cost users real money and are highly correlated with long load times.
0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
50 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.
60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
1.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
0.7 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: