First visit
CO2 0.099g
SIZE 319.87 KB
Return visit
CO2 0.006g
SIZE 20.41 KB
Emissions calculator
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
14.93 KB
0.005g
Stylesheet
6
43.04 KB
0.013g
Script
11
91.79 KB
0.028g
Image
4
68.76 KB
0.021g
Font
3
101.02 KB
0.031g
XHR
1
338 B
0.000g
History
Date
CO2
Size
20.Feb.2025
0.099g
319.87 KB
20.Feb.2025
0.101g
326.33 KB
11.Nov.2024
0.060g
193.66 KB
08.Nov.2024
0.057g
155.89 KB
08.Nov.2024
0.059g
159.62 KB
08.Nov.2024
0.200g
544.58 KB
This website has been tested 6 times**
Core Web Vitals
Max Potential First Input Delay
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
Cumulative Layout Shift
0.003
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Serve static assets with an efficient cache policy
3 resources found
A long cache lifetime can speed up repeat visits to your page.
Time to Interactive
0.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Speed Index
2.0 s
Speed Index shows how quickly the contents of a page are visibly populated.
Reduce initial server response time
Root document took 1,610 ms
Keep the server response time for the main document short because all other requests depend on it.
First Contentful Paint
0.8 s
First Contentful Paint marks the time at which the first text or image is painted.
Server Backend Latencies
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.
Network Round Trip Times
40 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.
Avoids enormous network payloads
Total size was 320 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Avoids an excessive DOM size
186 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
JavaScript execution time
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Minimizes main-thread work
0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Eliminate render-blocking resources
Potential savings of 490 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
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: