First visit
CO2 0.388g
SIZE 1.03 MB
Return visit
CO2 0.007g
SIZE 18.06 KB
First visit
CO2 0.388g
SIZE 1.03 MB
Return visit
CO2 0.007g
SIZE 18.06 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
10.8 KB
0.004g
Font
3
122.69 KB
0.045g
Stylesheet
2
25.53 KB
0.009g
Script
13
223.87 KB
0.082g
Image
14
589.32 KB
0.216g
Fetch
4
83.38 KB
0.031g
Other
1
1.26 KB
0.000g
History
Date
CO2
Size
19.Apr.2024
0.388g
1.03 MB
19.Apr.2024
0.388g
1.03 MB
14.Jan.2024
0.405g
1.08 MB
This website has been tested 3 times**
230 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
1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
1.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
0.8 s
First Meaningful Paint measures when the primary content of a page is visible.
100 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Potential savings of 157 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
0.8 s
First Contentful Paint marks the time at which the first text or image is painted.
Root document took 200 ms
Keep the server response time for the main document short because all other requests depend on it.
1 resource found
A long cache lifetime can speed up repeat visits to your page.
1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Total size was 1,057 KiB
Large network payloads cost users real money and are highly correlated with long load times.
510 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.
686 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
1.9 s
Speed Index shows how quickly the contents of a page are visibly populated.
0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
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.
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: