First visit
CO2 0.121g
SIZE 391.3 KB
Return visit
CO2 0.016g
SIZE 52.39 KB
First visit
CO2 0.121g
SIZE 391.3 KB
Return visit
CO2 0.016g
SIZE 52.39 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
49.65 KB
0.015g
Stylesheet
14
23.02 KB
0.007g
Script
3
26.58 KB
0.008g
Image
6
154.01 KB
0.048g
Font
6
137.22 KB
0.043g
XHR
1
847 B
0.000g
History
Date
CO2
Size
01.Mar.2025
0.121g
391.3 KB
08.Apr.2024
0.221g
602.01 KB
08.Apr.2024
0.221g
602.01 KB
This website has been tested 3 times**
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.001
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
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.6 s
First Contentful Paint marks the time at which the first text or image is painted.
4 resources found
A long cache lifetime can speed up repeat visits to your page.
Root document took 1,000 ms
Keep the server response time for the main document short because all other requests depend on it.
0 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 94 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Total size was 391 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Potential savings of 111 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
0.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
0.0 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.
0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
512 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Potential savings of 20 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP.
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: