First visit
CO2 2.112g
SIZE 2.52 MB
Return visit
CO2 0.315g
SIZE 384.82 KB
First visit
CO2 2.112g
SIZE 2.52 MB
Return visit
CO2 0.315g
SIZE 384.82 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
7
1.91 MB
1.599g
Image
7
439.59 KB
0.359g
Font
6
123.83 KB
0.101g
Stylesheet
3
27.69 KB
0.023g
Other
1
18.81 KB
0.015g
Document
1
16.97 KB
0.014g
190 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
0.011
Cumulative Layout Shift measures the movement of visible elements within the viewport.
0.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Total size was 2,582 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Potential savings of 20 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Root document took 300 ms
Keep the server response time for the main document short because all other requests depend on it.
Potential savings of 111 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
0.9 s
First Meaningful Paint measures when the primary content of a page is visible.
Potential savings of 1,388 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
Potential savings of 1,266 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
2.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
0.9 s
First Contentful Paint marks the time at which the first 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.
891 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
1.8 s
Speed Index shows how quickly the contents of a page are visibly populated.
70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
16 resources found
A long cache lifetime can speed up repeat visits to your page.
Potential savings of 300 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
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.
These measurements are for each new visitor, for returning visitors the footprint would be lower based on caching mechanisms.
Our brackets for the ratings: