First visit
CO2 0.292g
SIZE 940.58 KB
Return visit
CO2 0.233g
SIZE 752.16 KB
First visit
CO2 0.292g
SIZE 940.58 KB
Return visit
CO2 0.233g
SIZE 752.16 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
32.65 KB
0.010g
Font
8
189.38 KB
0.059g
Stylesheet
26
85.81 KB
0.027g
Script
29
357.24 KB
0.111g
Image
10
273.74 KB
0.085g
Fetch
1
790 B
0.000g
XHR
1
1008 B
0.000g
History
Date
CO2
Size
16.Jan.2025
0.292g
940.58 KB
26.Mar.2024
0.367g
1.16 MB
21.Mar.2024
0.367g
1.16 MB
16.Feb.2023
0.446g
601.96 KB
15.Feb.2023
0.446g
602 KB
20.Jan.2023
0.440g
594.34 KB
19.Jan.2023
0.440g
594.31 KB
10.Jan.2023
0.553g
746.87 KB
05.Jan.2023
0.551g
743.63 KB
This website has been tested 9 times**
60 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.001
Cumulative Layout Shift measures the movement of visible elements within the viewport.
1.2 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.
Potential savings of 82 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Potential savings of 90 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
68 resources found
A long cache lifetime can speed up repeat visits to your page.
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.
2.7 s
Speed Index shows how quickly the contents of a page are visibly populated.
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 360 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Potential savings of 25 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Total size was 941 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Root document took 1,600 ms
Keep the server response time for the main document short because all other requests depend on it.
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes.
566 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
0.7 s
First Contentful Paint marks the time at which the first text or image is painted.
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: