First visit
CO2 0.177g
SIZE 569.23 KB
Return visit
CO2 0.022g
SIZE 71.92 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
39.96 KB
0.012g
Script
9
180.68 KB
0.056g
Stylesheet
6
51.69 KB
0.016g
Image
7
192.84 KB
0.060g
Fetch
6
12.02 KB
0.004g
Font
4
92.04 KB
0.029g
History
Date
CO2
Size
14.Feb.2025
0.177g
569.23 KB
09.Dec.2024
0.167g
536.89 KB
05.Dec.2024
0.166g
533.57 KB
03.Dec.2024
0.165g
531.79 KB
03.Dec.2024
0.165g
532.14 KB
02.Dec.2024
0.325g
1.02 MB
15.Nov.2024
0.335g
1.05 MB
15.Nov.2024
0.335g
1.05 MB
This website has been tested 8 times**
Core Web Vitals
Max Potential First Input Delay
50 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
1.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
First Contentful Paint
0.7 s
First Contentful Paint marks the time at which the first text or image is painted.
Server Backend Latencies
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.
Avoids an excessive DOM size
489 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Network Round Trip Times
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.
Serve static assets with an efficient cache policy
15 resources found
A long cache lifetime can speed up repeat visits to your page.
Initial server response time was short
Root document took 290 ms
Keep the server response time for the main document short because all other requests depend on it.
Reduce unused JavaScript
Potential savings of 41 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Eliminate render-blocking resources
Potential savings of 400 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Time to Interactive
1.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Speed Index
0.8 s
Speed Index shows how quickly the contents of a page are visibly populated.
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Minimizes main-thread work
0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
JavaScript execution time
0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Avoids enormous network payloads
Total size was 569 KiB
Large network payloads cost users real money and are highly correlated with long load times.
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: