First visit
CO2 0.590g
SIZE 1.57 MB
Return visit
CO2 0.521g
SIZE 1.39 MB
First visit
CO2 0.590g
SIZE 1.57 MB
Return visit
CO2 0.521g
SIZE 1.39 MB
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
9.33 KB
0.003g
Stylesheet
15
183.98 KB
0.067g
Script
14
199.64 KB
0.073g
Image
21
833.05 KB
0.306g
Font
8
382 KB
0.140g
History
Date
CO2
Size
21.Nov.2023
0.590g
1.57 MB
23.Jan.2023
0.674g
823.94 KB
23.Jan.2023
0.674g
823.83 KB
25.Apr.2022
0.845g
1.01 MB
19.Jan.2022
0.588g
718.76 KB
11.Jan.2022
0.672g
822.35 KB
07.Dec.2021
1.012g
1.21 MB
01.Dec.2021
0.915g
1.09 MB
01.Dec.2021
0.914g
1.09 MB
01.Dec.2021
1.189g
1.42 MB
30.Nov.2021
1.848g
2.21 MB
This website has been tested 29 times**
Previous 10 test results are displayed above.
40 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.027
Cumulative Layout Shift measures the movement of visible elements within the viewport.
2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
1.6 s
First Meaningful Paint measures when the primary content of a page is visible.
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Root document took 190 ms
Keep the server response time for the main document short because all other requests depend on it.
0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
227 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
20 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.
Potential savings of 618 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
4.3 s
Speed Index shows how quickly the contents of a page are visibly populated.
1.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Potential savings of 136 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Potential savings of 630 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Total size was 1,549 KiB
Large network payloads cost users real money and are highly correlated with long load times.
1.6 s
First Contentful Paint marks the time at which the first text or image is painted.
51 resources found
A long cache lifetime can speed up repeat visits to your page.
Potential savings of 1,390 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
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.
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: