First visit
CO2 0.489g
SIZE 1.54 MB
Return visit
CO2 0.050g
SIZE 159.62 KB
First visit
CO2 0.489g
SIZE 1.54 MB
Return visit
CO2 0.050g
SIZE 159.62 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
17.47 KB
0.005g
Stylesheet
9
67.2 KB
0.021g
Script
9
336.42 KB
0.104g
Image
34
1.09 MB
0.346g
Font
3
35.91 KB
0.011g
XHR
3
2.26 KB
0.001g
Other
3
3.63 KB
0.001g
History
Date
CO2
Size
03.Apr.2025
0.489g
1.54 MB
27.Feb.2025
0.565g
1.78 MB
20.Jan.2025
1.058g
3.33 MB
10.Dec.2024
0.754g
2.37 MB
19.May.2022
2.166g
2.59 MB
26.Nov.2021
1.722g
2.06 MB
18.Nov.2021
2.083g
2.49 MB
This website has been tested 7 times**
180 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.011
Cumulative Layout Shift measures the movement of visible elements within the viewport.
1.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Potential savings of 410 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Potential savings of 408 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
1.2 s
Speed Index shows how quickly the contents of a page are visibly populated.
Potential savings of 44 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Potential savings of 453 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.
Potential savings of 117 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Total size was 1,577 KiB
Large network payloads cost users real money and are highly correlated with long load times.
2.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
0.7 s
First Contentful Paint marks the time at which the first text or image is painted.
150 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Potential savings of 365 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
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.
36 resources found
A long cache lifetime can speed up repeat visits to your page.
991 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Root document took 30 ms
Keep the server response time for the main document short because all other requests depend on it.
1.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
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.
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: