First visit
CO2 2.024g
SIZE 5.39 MB
Return visit
CO2 0.100g
SIZE 272.98 KB
First visit
CO2 2.024g
SIZE 5.39 MB
Return visit
CO2 0.100g
SIZE 272.98 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
Script
29
3.7 MB
1.390g
Image
46
1.1 MB
0.414g
Stylesheet
10
231.39 KB
0.085g
Document
5
136.13 KB
0.050g
Font
11
133.92 KB
0.049g
Other
19
100.09 KB
0.037g
History
Date
CO2
Size
20.Jun.2023
2.024g
5.39 MB
07.Nov.2022
4.077g
4.87 MB
19.May.2022
3.534g
4.22 MB
This website has been tested 3 times**
260 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.077
Cumulative Layout Shift measures the movement of visible elements within the viewport.
0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
53 resources found
A long cache lifetime can speed up repeat visits to your page.
Potential savings of 64 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
2.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Potential savings of 190 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
0.8 s
First Contentful Paint marks the time at which the first text or image is painted.
270 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Potential savings of 272 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
5.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
680 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
1.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Root document took 60 ms
Keep the server response time for the main document short because all other requests depend on it.
Total size was 5,517 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Potential savings of 1,857 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Potential savings of 12 KiB
Minifying JavaScript files can reduce payload sizes and script parse time.
Potential savings of 593 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.
0.8 s
First Meaningful Paint measures when the primary content of a page is visible.
2.3 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: