First visit
CO2 0.149g
SIZE 480.98 KB
Return visit
CO2 0.006g
SIZE 17.71 KB
First visit
CO2 0.149g
SIZE 480.98 KB
Return visit
CO2 0.006g
SIZE 17.71 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
14.15 KB
0.004g
Stylesheet
5
53 KB
0.016g
Script
12
134.81 KB
0.042g
Image
6
256.02 KB
0.079g
Font
1
22.26 KB
0.007g
Fetch
1
750 B
0.000g
History
Date
CO2
Size
16.Nov.2023
0.149g
480.98 KB
14.Nov.2023
0.149g
480.97 KB
12.Nov.2023
0.149g
481.04 KB
06.Nov.2023
0.151g
486.7 KB
02.Nov.2023
0.280g
903.42 KB
02.Nov.2023
0.280g
903.42 KB
13.Oct.2023
0.345g
1.09 MB
08.Aug.2023
0.348g
1.1 MB
09.Sep.2022
0.587g
792.11 KB
09.Sep.2022
0.597g
805.04 KB
09.Sep.2022
0.597g
805.29 KB
This website has been tested 12 times**
Previous 10 test results are displayed above.
120 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.002
Cumulative Layout Shift measures the movement of visible elements within the viewport.
1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
0.8 s
First Contentful Paint marks the time at which the first text or image is painted.
567 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Total size was 481 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Potential savings of 320 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
1 resource found
A long cache lifetime can speed up repeat visits to your page.
Potential savings of 49 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
970 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.
0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
0.8 s
First Meaningful Paint measures when the primary content of a page is visible.
1.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Root document took 180 ms
Keep the server response time for the main document short because all other requests depend on it.
Potential savings of 44 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
1.1 s
Speed Index shows how quickly the contents of a page are visibly populated.
60 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: