First visit
CO2 1.781g
SIZE 2.13 MB
Return visit
CO2 1.686g
SIZE 2.01 MB
First visit
CO2 1.781g
SIZE 2.13 MB
Return visit
CO2 1.686g
SIZE 2.01 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
8
1.51 MB
1.261g
Script
11
573.89 KB
0.469g
Stylesheet
6
34.86 KB
0.029g
Font
1
12.2 KB
0.010g
Other
14
7.97 KB
0.007g
Document
1
7.82 KB
0.006g
180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
0.165
Cumulative Layout Shift measures the movement of visible elements within the viewport.
2.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
14 resources found
A long cache lifetime can speed up repeat visits to your page.
Potential savings of 1,200 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Root document took 200 ms
Keep the server response time for the main document short because all other requests depend on it.
2.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
1.4 s
Speed Index shows how quickly the contents of a page are visibly populated.
Potential savings of 390 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 1,085 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
0.6 s
First Meaningful Paint measures when the primary content of a page is visible.
0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
120 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
324 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Potential savings of 739 KiB
Optimized images load faster and consume less cellular data.
Potential savings of 183 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Total size was 2,179 KiB
Large network payloads cost users real money and are highly correlated with long load times.
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: