First visit
CO2 1.042g
SIZE 3.28 MB
Return visit
CO2 0.810g
SIZE 2.55 MB
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
3
14.37 KB
0.004g
Stylesheet
5
23.46 KB
0.007g
Script
14
496.43 KB
0.154g
Image
13
223.94 KB
0.069g
Font
2
47.62 KB
0.015g
Media
1
2.49 MB
0.790g
XHR
1
893 B
0.000g
Fetch
5
3.24 KB
0.001g
History
Date
CO2
Size
07.Apr.2025
1.042g
3.28 MB
11.Jul.2024
1.025g
3.23 MB
24.Jun.2024
0.999g
3.14 MB
29.Aug.2023
0.218g
702.89 KB
10.Jul.2023
0.181g
582.01 KB
20.Apr.2023
0.396g
534.74 KB
16.Feb.2023
0.426g
574.37 KB
08.Jun.2022
0.278g
375.56 KB
31.May.2022
0.278g
374.85 KB
31.May.2022
6.216g
8.19 MB
31.May.2022
6.216g
8.19 MB
This website has been tested 11 times**
Previous 10 test results are displayed above.
Core Web Vitals
Max Potential First Input Delay
110 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.001
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
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.
Avoid enormous network payloads
Total size was 3,357 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 50 ms
Keep the server response time for the main document short because all other requests depend on it.
Minimizes main-thread work
0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Serve static assets with an efficient cache policy
24 resources found
A long cache lifetime can speed up repeat visits to your page.
Speed Index
0.8 s
Speed Index shows how quickly the contents of a page are visibly populated.
Eliminate render-blocking resources
Potential savings of 370 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
First Contentful Paint
0.7 s
First Contentful Paint marks the time at which the first text or image is painted.
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.
Avoids an excessive DOM size
341 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Properly size images
Potential savings of 98 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Time to Interactive
1.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Server Backend Latencies
40 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
30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce unused JavaScript
Potential savings of 195 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: