First visit
CO2 0.068g
SIZE 218.78 KB
Return visit
CO2 0.031g
SIZE 98.95 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
19.06 KB
0.006g
Image
3
21.98 KB
0.007g
Font
3
99.28 KB
0.031g
Stylesheet
1
1.2 KB
0.000g
Script
8
77.26 KB
0.024g
History
Date
CO2
Size
16.Apr.2025
0.068g
218.78 KB
27.Mar.2025
0.068g
218.78 KB
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 8 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
Largest Contentful Paint
0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Speed Index
0.4 s
Speed Index shows how quickly the contents of a page are visibly populated.
Minimizes main-thread work
0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Network Round Trip Times
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.
Serve static assets with an efficient cache policy
13 resources found
A long cache lifetime can speed up repeat visits to your page.
Time to Interactive
0.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
First Contentful Paint
0.4 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.
Initial server response time was short
Root document took 40 ms
Keep the server response time for the main document short because all other requests depend on it.
Avoids enormous network payloads
Total size was 219 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Eliminate render-blocking resources
Potential savings of 130 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
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.
Avoids an excessive DOM size
194 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Reduce unused JavaScript
Potential savings of 53 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
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: