First visit
CO2 0.057g
SIZE 182.51 KB
Return visit
CO2 0.008g
SIZE 25.66 KB
First visit
CO2 0.057g
SIZE 182.51 KB
Return visit
CO2 0.008g
SIZE 25.66 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
25.66 KB
0.008g
Stylesheet
15
41.66 KB
0.013g
Image
9
21.82 KB
0.007g
Script
3
7.01 KB
0.002g
Font
3
85.63 KB
0.027g
Fetch
1
750 B
0.000g
History
Date
CO2
Size
21.Aug.2023
0.057g
182.51 KB
31.May.2023
0.053g
172.1 KB
26.Jan.2023
0.129g
173.63 KB
12.Jan.2023
0.142g
191.92 KB
12.Jan.2023
0.142g
191.93 KB
04.Dec.2022
0.127g
171.04 KB
17.Oct.2022
0.115g
155.68 KB
24.Aug.2022
0.116g
156.87 KB
21.Aug.2022
0.114g
154.14 KB
24.Jun.2022
0.113g
152.75 KB
21.Jun.2022
0.113g
152.75 KB
This website has been tested 14 times**
Previous 10 test results are displayed above.
20 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.017
Cumulative Layout Shift measures the movement of visible elements within the viewport.
0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Total size was 183 KiB
Large network payloads cost users real money and are highly correlated with long load times.
20 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.
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
0.5 s
First Contentful Paint marks the time at which the first text or image is painted.
Root document took 20 ms
Keep the server response time for the main document short because all other requests depend on it.
0.6 s
First Meaningful Paint measures when the primary content of a page is visible.
Potential savings of 14 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
120 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.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
447 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
0.5 s
Speed Index shows how quickly the contents of a page are visibly populated.
Potential savings of 60 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
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: