First visit
CO2 0.058g
SIZE 187.34 KB
Return visit
CO2 0.009g
SIZE 27.45 KB
First visit
CO2 0.058g
SIZE 187.34 KB
Return visit
CO2 0.009g
SIZE 27.45 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
27.45 KB
0.009g
Stylesheet
15
45.39 KB
0.014g
Image
7
17.87 KB
0.006g
Script
4
10.03 KB
0.003g
Font
3
85.63 KB
0.027g
Fetch
1
980 B
0.000g
History
Date
CO2
Size
30.May.2025
0.058g
187.34 KB
05.Jun.2024
0.057g
183.13 KB
10.Apr.2024
0.057g
182.85 KB
06.Jan.2024
0.056g
181.2 KB
06.Jan.2024
0.056g
181.21 KB
15.Dec.2023
0.056g
181.19 KB
15.Dec.2023
0.056g
181.19 KB
21.Aug.2023
0.057g
182.51 KB
31.May.2023
0.053g
172.1 KB
26.Jan.2023
0.129g
173.63 KB
12.Jan.2023
0.142g
191.92 KB
This website has been tested 21 times**
Previous 10 test results are displayed above.
30 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.013
Cumulative Layout Shift measures the movement of visible elements within the viewport.
0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
0.4 s
First Contentful Paint marks the time at which the first text or image is painted.
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.
Total size was 187 KiB
Large network payloads cost users real money and are highly correlated with long load times.
0.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
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.
Root document took 60 ms
Keep the server response time for the main document short because all other requests depend on it.
443 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Est savings of 14 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
0.5 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: