First visit
CO2 0.498g
SIZE 1.33 MB
Return visit
CO2 0.007g
SIZE 19.25 KB
First visit
CO2 0.498g
SIZE 1.33 MB
Return visit
CO2 0.007g
SIZE 19.25 KB
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
12.14 KB
0.004g
Stylesheet
2
9.61 KB
0.004g
Script
18
244.5 KB
0.090g
Image
21
885.59 KB
0.325g
Font
2
185.27 KB
0.068g
XHR
5
5.42 KB
0.002g
Other
5
13.83 KB
0.005g
Fetch
1
855 B
0.000g
History
Date
CO2
Size
30.Oct.2024
0.498g
1.33 MB
08.Oct.2024
0.470g
1.25 MB
26.Sep.2024
0.470g
1.25 MB
05.Feb.2024
0.454g
1.21 MB
25.Jan.2024
0.438g
1.17 MB
02.Nov.2023
0.300g
816.95 KB
04.Oct.2023
0.291g
792.74 KB
08.Sep.2023
0.295g
804.91 KB
22.Aug.2023
0.295g
804.76 KB
10.May.2023
0.687g
840.09 KB
04.May.2023
0.687g
840.13 KB
This website has been tested 21 times**
Previous 10 test results are displayed above.
70 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
0.355
Cumulative Layout Shift measures the movement of visible elements within the viewport.
1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
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.
1.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Potential savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers.
378 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Root document took 480 ms
Keep the server response time for the main document short because all other requests depend on it.
Potential savings of 75 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
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.
2 resources found
A long cache lifetime can speed up repeat visits to your page.
Total size was 1,357 KiB
Large network payloads cost users real money and are highly correlated with long load times.
40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
1.7 s
Speed Index shows how quickly the contents of a page are visibly populated.
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: