First visit
CO2 0.046g
SIZE 149.38 KB
Return visit
CO2 0.014g
SIZE 46.55 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
44.98 KB
0.014g
Font
2
29.2 KB
0.009g
Stylesheet
1
6.38 KB
0.002g
Script
5
40.55 KB
0.013g
Image
5
25.23 KB
0.008g
XHR
3
3.03 KB
0.001g
History
Date
CO2
Size
30.Sep.2024
0.046g
149.38 KB
22.Aug.2024
0.043g
140.03 KB
25.Jan.2024
0.041g
132.7 KB
25.Oct.2023
0.032g
104.21 KB
07.Jul.2023
0.032g
102.88 KB
07.Jul.2023
0.030g
95.74 KB
06.Apr.2022
0.057g
76.49 KB
29.Mar.2022
0.085g
114.38 KB
29.Jan.2022
0.060g
81.14 KB
21.Jan.2022
0.067g
89.94 KB
12.Nov.2021
0.065g
88.36 KB
This website has been tested 13 times**
Previous 10 test results are displayed above.
Core Web Vitals
Max Potential First Input Delay
50 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
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
0.5 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
666 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
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.
Avoids enormous network payloads
Total size was 149 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Initial server response time was short
Root document took 30 ms
Keep the server response time for the main document short because all other requests depend on it.
Preload Largest Contentful Paint image
Potential savings of 30 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP.
First Contentful Paint
0.4 s
First Contentful Paint marks the time at which the first text or image is painted.
Speed Index
0.9 s
Speed Index shows how quickly the contents of a page are visibly populated.
Time to Interactive
0.8 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
1 resource found
A long cache lifetime can speed up repeat visits to your page.
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.
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: