First visit
CO2 1.327g
SIZE 3.53 MB
Return visit
CO2 0.072g
SIZE 195.11 KB
First visit
CO2 1.327g
SIZE 3.53 MB
Return visit
CO2 0.072g
SIZE 195.11 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
5
195.11 KB
0.072g
Stylesheet
10
254.57 KB
0.093g
Script
32
2.12 MB
0.797g
Image
35
765 KB
0.281g
Font
11
133.92 KB
0.049g
Fetch
4
2.25 KB
0.001g
Preflight
2
1.03 KB
0.000g
XHR
7
93.35 KB
0.034g
History
Date
CO2
Size
10.Apr.2025
1.327g
3.53 MB
20.Jun.2023
2.024g
5.39 MB
07.Nov.2022
4.077g
4.87 MB
19.May.2022
3.534g
4.22 MB
This website has been tested 4 times**
170 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.082
Cumulative Layout Shift measures the movement of visible elements within the viewport.
0.8 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.8 s
First Contentful Paint marks the time at which the first text or image is painted.
Total size was 3,617 KiB
Large network payloads cost users real money and are highly correlated with long load times.
1.6 s
Speed Index shows how quickly the contents of a page are visibly populated.
1.6 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.
Potential savings of 201 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
4.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Root document took 10 ms
Keep the server response time for the main document short because all other requests depend on it.
497 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
2.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
450 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Potential savings of 470 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
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: