First visit
CO2 0.739g
SIZE 1.97 MB
Return visit
CO2 0.043g
SIZE 117.37 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
111.07 KB
0.041g
Stylesheet
5
84.5 KB
0.031g
Script
15
323.7 KB
0.119g
Image
135
1.28 MB
0.482g
Fetch
1
1018 B
0.000g
XHR
6
6.94 KB
0.003g
Other
1
749 B
0.000g
Font
8
174.8 KB
0.064g
History
Date
CO2
Size
03.Nov.2024
0.739g
1.97 MB
21.Oct.2024
2.243g
7.06 MB
18.Oct.2024
0.602g
1.6 MB
14.Oct.2024
0.593g
1.58 MB
04.Jun.2024
0.770g
2.42 MB
04.Jun.2024
0.768g
2.42 MB
24.May.2024
0.625g
1.97 MB
17.May.2024
0.541g
1.7 MB
17.May.2024
0.537g
1.69 MB
08.Apr.2024
0.808g
2.15 MB
22.Feb.2024
0.603g
1.9 MB
This website has been tested 40 times**
Previous 10 test results are displayed above.
Core Web Vitals
Max Potential First Input Delay
160 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.065
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
1.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Avoid an excessive DOM size
1,625 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Initial server response time was short
Root document took 70 ms
Keep the server response time for the main document short because all other requests depend on it.
Time to Interactive
2.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
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.
Speed Index
1.5 s
Speed Index shows how quickly the contents of a page are visibly populated.
Avoids enormous network payloads
Total size was 2,015 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Serve static assets with an efficient cache policy
28 resources found
A long cache lifetime can speed up repeat visits to your page.
Reduce unused JavaScript
Potential savings of 136 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
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.
Total Blocking Time
60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Minimize main-thread work
2.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
JavaScript execution time
1.2 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
Potential savings of 220 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.6 s
First Contentful Paint marks the time at which the first text or image is painted.
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: