First visit
CO2 2.166g
SIZE 2.59 MB
Return visit
CO2 1.345g
SIZE 1.61 MB
First visit
CO2 2.166g
SIZE 2.59 MB
Return visit
CO2 1.345g
SIZE 1.61 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
Image
36
1.48 MB
1.241g
Script
8
520.38 KB
0.425g
Stylesheet
8
474.68 KB
0.388g
Document
1
94.02 KB
0.077g
Font
3
36.18 KB
0.030g
Other
5
6.86 KB
0.006g
History
Date
CO2
Size
19.May.2022
2.166g
2.59 MB
26.Nov.2021
1.722g
2.06 MB
18.Nov.2021
2.083g
2.49 MB
This website has been tested 3 times**
60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
0.285
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.
1.3 s
Speed Index shows how quickly the contents of a page are visibly populated.
Potential savings of 487 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Potential savings of 687 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
1.4 s
First Meaningful Paint measures when the primary content of a page is visible.
1.3 s
First Contentful Paint marks the time at which the first text or image is painted.
Potential savings of 741 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
Potential savings of 232 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Potential savings of 107 KiB
Minifying JavaScript files can reduce payload sizes and script parse time.
Potential savings of 112 KiB
Optimized images load faster and consume less cellular data.
Root document took 50 ms
Keep the server response time for the main document short because all other requests depend on it.
50 resources found
A long cache lifetime can speed up repeat visits to your page.
Total size was 2,650 KiB
Large network payloads cost users real money and are highly correlated with long load times.
1,027 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
2.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
Potential savings of 900 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Potential savings of 395 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
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: