First visit
CO2 0.521g
SIZE 1.39 MB
Return visit
CO2 0.048g
SIZE 131.16 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
2
130.67 KB
0.048g
Font
4
98.81 KB
0.036g
Stylesheet
3
49.96 KB
0.018g
Script
23
861.15 KB
0.316g
XHR
3
3.13 KB
0.001g
Image
1
2.92 KB
0.001g
Other
1
273.02 KB
0.100g
History
Date
CO2
Size
01.Jul.2025
0.521g
1.39 MB
25.Nov.2024
0.456g
1.21 MB
24.Nov.2024
0.455g
1.21 MB
10.Oct.2024
0.454g
1.21 MB
13.Sep.2024
0.176g
480.56 KB
04.Jul.2024
0.173g
470.17 KB
29.Jun.2024
0.172g
469.88 KB
26.Jun.2024
0.173g
470.42 KB
26.Jun.2024
0.174g
473.18 KB
26.Jun.2024
0.202g
551.41 KB
26.Jun.2024
0.202g
551.44 KB
This website has been tested 29 times**
Previous 10 test results are displayed above.
Core Web Vitals
Max Potential First Input Delay
180 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.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Reduce unused JavaScript
Est savings of 326 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Network Round Trip Times
50 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.
JavaScript execution time
1.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
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.
Total Blocking Time
230 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Avoid an excessive DOM size
1,883 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Avoids enormous network payloads
Total size was 1,420 KiB
Large network payloads cost users real money and are highly correlated with long load times.
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.
Time to Interactive
2.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Minimizes main-thread work
1.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Speed Index
1.1 s
Speed Index shows how quickly the contents of a page are visibly populated.
First Contentful Paint
0.5 s
First Contentful Paint marks the time at which the first text or image is painted.
Serve static assets with an efficient cache policy
2 resources found
A long cache lifetime can speed up repeat visits to your page.
Switch to green hosting
One of the easiest things to do that instantly reduces your impact.
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: