First visit
CO2 0.376g
SIZE 1.18 MB
Return visit
CO2 0.004g
SIZE 14.37 KB
First visit
CO2 0.376g
SIZE 1.18 MB
Return visit
CO2 0.004g
SIZE 14.37 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
13.42 KB
0.004g
Stylesheet
3
40.4 KB
0.013g
Script
11
782.85 KB
0.243g
Fetch
3
1.56 KB
0.000g
Font
2
371.55 KB
0.115g
Image
1
1.14 KB
0.000g
History
Date
CO2
Size
23.Feb.2025
0.376g
1.18 MB
23.Feb.2025
0.376g
1.18 MB
23.Feb.2025
0.376g
1.18 MB
This website has been tested 3 times**
90 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
Cumulative Layout Shift measures the movement of visible elements within the viewport.
1.6 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.
Potential savings of 376 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Potential savings of 790 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
1.5 s
First Contentful Paint marks the time at which the first text or image is painted.
Total size was 1,211 KiB
Large network payloads cost users real money and are highly correlated with long load times.
212 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
1 resource found
A long cache lifetime can speed up repeat visits to your page.
0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
1.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
20 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.
1.5 s
Speed Index shows how quickly the contents of a page are visibly populated.
Root document took 40 ms
Keep the server response time for the main document short because all other requests depend on it.
0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Potential savings of 34 KiB
Minifying JavaScript files can reduce payload sizes and script parse time.
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: