First visit
CO2 0.018g
SIZE 57.53 KB
Return visit
CO2 0.003g
SIZE 10.66 KB
First visit
CO2 0.018g
SIZE 57.53 KB
Return visit
CO2 0.003g
SIZE 10.66 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
5.94 KB
0.002g
Stylesheet
1
3.2 KB
0.001g
Script
5
12.39 KB
0.004g
Image
2
20.45 KB
0.006g
Font
1
11.75 KB
0.004g
XHR
4
3.37 KB
0.001g
Preflight
1
456 B
0.000g
History
Date
CO2
Size
31.May.2024
0.018g
57.53 KB
31.May.2024
0.021g
66.86 KB
31.May.2024
0.021g
66.71 KB
18.Oct.2023
0.037g
119.31 KB
28.Mar.2022
0.022g
29.21 KB
24.Jan.2022
0.021g
28.92 KB
11.Nov.2021
0.152g
185.91 KB
08.Nov.2021
0.152g
185.68 KB
02.Nov.2021
0.173g
211.6 KB
This website has been tested 9 times**
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
0.012
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.
Total size was 58 KiB
Large network payloads cost users real money and are highly correlated with long load times.
0.3 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.
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.
0.3 s
First Meaningful Paint measures when the primary content of a page is visible.
0.9 s
Speed Index shows how quickly the contents of a page are visibly populated.
0.2 s
First Contentful Paint marks the time at which the first text or image is painted.
Root document took 400 ms
Keep the server response time for the main document short because all other requests depend on it.
0.1 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.
83 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
3 resources found
A long cache lifetime can speed up repeat visits to your page.
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: