First visit
CO2 0.149g
SIZE 406.39 KB
Return visit
CO2 0.026g
SIZE 71.04 KB
First visit
CO2 0.149g
SIZE 406.39 KB
Return visit
CO2 0.026g
SIZE 71.04 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
71.04 KB
0.026g
Stylesheet
2
18.01 KB
0.007g
Script
6
52.04 KB
0.019g
Image
6
77.35 KB
0.028g
Font
3
186 KB
0.068g
Fetch
1
1.95 KB
0.001g
History
Date
CO2
Size
12.Mar.2025
0.149g
406.39 KB
10.Mar.2025
0.149g
406.5 KB
10.Mar.2025
0.150g
407.59 KB
10.Mar.2025
0.149g
406.65 KB
07.Mar.2025
0.156g
425.48 KB
07.Mar.2025
0.156g
425.48 KB
07.Mar.2025
0.156g
425.47 KB
23.Jan.2025
0.332g
904.97 KB
23.Jan.2025
0.332g
905.22 KB
12.Dec.2024
0.330g
900.05 KB
02.Dec.2024
0.350g
955.06 KB
This website has been tested 14 times**
Previous 10 test results are displayed above.
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.007
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.
10 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.5 s
Speed Index shows how quickly the contents of a page are visibly populated.
363 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
0.5 s
First Contentful Paint marks the time at which the first text or image is painted.
Total size was 406 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Potential savings of 9 KiB
Minifying JavaScript files can reduce payload sizes and script parse time.
0.0 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.
0.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Root document took 40 ms
Keep the server response time for the main document short because all other requests depend on it.
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: