First visit
CO2 1.317g
SIZE 4.15 MB
Return visit
CO2 0.952g
SIZE 3 MB
First visit
CO2 1.317g
SIZE 4.15 MB
Return visit
CO2 0.952g
SIZE 3 MB
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
6
54.62 KB
0.017g
Stylesheet
4
51.8 KB
0.016g
Script
35
1.13 MB
0.358g
Image
39
2.81 MB
0.893g
Font
2
46.93 KB
0.015g
XHR
6
6.16 KB
0.002g
Fetch
7
47.48 KB
0.015g
Other
5
5.31 KB
0.002g
History
Date
CO2
Size
03.Apr.2025
1.317g
4.15 MB
19.May.2022
3.770g
4.5 MB
This website has been tested 2 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.003
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.
70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
40 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 2,035 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
675 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
30 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 2,166 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
41 resources found
A long cache lifetime can speed up repeat visits to your page.
Potential savings of 420 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 612 KiB
Optimized images load faster and consume less cellular data.
1.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Root document took 20 ms
Keep the server response time for the main document short because all other requests depend on it.
0.7 s
First Contentful Paint marks the time at which the first text or image is painted.
Potential savings of 10 KiB
Minifying CSS files can reduce network payload sizes.
1.1 s
Speed Index shows how quickly the contents of a page are visibly populated.
Total size was 4,245 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Potential savings of 58 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
1.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
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: