First visit
CO2 0.651g
SIZE 2.05 MB
Return visit
CO2 0.021g
SIZE 69.25 KB
First visit
CO2 0.651g
SIZE 2.05 MB
Return visit
CO2 0.021g
SIZE 69.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
Other
1
518 B
0.000g
Document
1
69.25 KB
0.021g
Font
14
740.97 KB
0.230g
Stylesheet
5
140.15 KB
0.043g
Script
8
422.82 KB
0.131g
Image
20
721.49 KB
0.224g
Fetch
2
1.53 KB
0.000g
History
Date
CO2
Size
14.Oct.2025
0.651g
2.05 MB
13.Oct.2025
0.543g
1.71 MB
13.May.2025
0.524g
1.65 MB
06.Mar.2025
0.520g
1.64 MB
15.Jan.2025
0.428g
1.35 MB
10.May.2024
0.195g
629.48 KB
10.May.2024
0.353g
1.11 MB
10.May.2024
0.354g
1.11 MB
10.May.2024
0.354g
1.11 MB
10.May.2024
0.354g
1.12 MB
10.May.2024
0.354g
1.12 MB
This website has been tested 19 times**
Previous 10 test results are displayed above.
60 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.049
Cumulative Layout Shift measures the movement of visible elements within the viewport.
2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
5.2 s
Speed Index shows how quickly the contents of a page are visibly populated.
170 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.
30 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.
Est savings of 230 ms
Redirects introduce additional delays before the page can be loaded.
Est savings of 228 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Root document took 1,580 ms
Keep the server response time for the main document short because all other requests depend on it.
Est savings of 55 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.
Est savings of 200 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
1.3 s
First Contentful Paint marks the time at which the first text or image is painted.
Est savings of 40 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP.
1.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Est savings of 140 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
1,095 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
2.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Total size was 2,097 KiB
Large network payloads cost users real money and are highly correlated with long load times.
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: