First visit
CO2 0.017g
SIZE 46.46 KB
Return visit
CO2 0.010g
SIZE 28.41 KB
First visit
CO2 0.017g
SIZE 46.46 KB
Return visit
CO2 0.010g
SIZE 28.41 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
28.41 KB
0.010g
Stylesheet
1
8.84 KB
0.003g
Script
1
3.92 KB
0.001g
Image
4
5.3 KB
0.002g
History
Date
CO2
Size
13.Jan.2024
0.017g
46.46 KB
13.Jan.2024
0.017g
46.49 KB
12.Jan.2024
0.017g
46.49 KB
01.Jan.2024
0.017g
46.76 KB
This website has been tested 4 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.4 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.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
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.
130 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 610 ms
Keep the server response time for the main document short because all other requests depend on it.
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Total size was 46 KiB
Large network payloads cost users real money and are highly correlated with long load times.
0.4 s
First Meaningful Paint measures when the primary content of a page is visible.
0.7 s
Speed Index shows how quickly the contents of a page are visibly populated.
0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
1,371 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
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: