First visit
CO2 0.073g
SIZE 234.21 KB
Return visit
CO2 0.020g
SIZE 65.51 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
15.95 KB
0.005g
Image
11
16.84 KB
0.005g
Stylesheet
2
23.38 KB
0.007g
Script
6
99.73 KB
0.031g
Font
5
78.3 KB
0.024g
History
Date
CO2
Size
25.Aug.2025
0.073g
234.21 KB
12.May.2025
0.315g
1014.73 KB
This website has been tested 2 times**
Core Web Vitals
Max Potential First Input Delay
60 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.139
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
0.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
JavaScript execution time
0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
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.
First Contentful Paint
0.5 s
First Contentful Paint marks the time at which the first text or image is painted.
Initial server response time was short
Root document took 10 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 234 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Reduce unused JavaScript
Est savings of 21 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Network Round Trip Times
20 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.
Total Blocking Time
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index
0.5 s
Speed Index shows how quickly the contents of a page are visibly populated.
Avoids an excessive DOM size
559 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
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.
Eliminate render-blocking resources
Est savings of 240 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
0.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Serve static assets with an efficient cache policy
3 resources found
A long cache lifetime can speed up repeat visits to your page.
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: