First visit
CO2 1.009g
SIZE 1.33 MB
Return visit
CO2 0.633g
SIZE 854.26 KB
First visit
CO2 1.009g
SIZE 1.33 MB
Return visit
CO2 0.633g
SIZE 854.26 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
11
618.33 KB
0.458g
Image
22
514.49 KB
0.381g
Font
3
133.37 KB
0.099g
Stylesheet
4
76.41 KB
0.057g
Document
2
13.07 KB
0.010g
Other
5
5.5 KB
0.004g
90 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
0.072
Cumulative Layout Shift measures the movement of visible elements within the viewport.
1.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Potential savings of 420 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 70 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
1.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
Potential savings of 201 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Root document took 140 ms
Keep the server response time for the main document short because all other requests depend on it.
0.7 s
First Meaningful Paint measures when the primary content of a page is visible.
0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Potential savings of 27 KiB
Optimized images load faster and consume less cellular data.
Potential savings of 12 KiB
Minifying JavaScript files can reduce payload sizes and script parse time.
Potential savings of 159 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
13 resources found
A long cache lifetime can speed up repeat visits to your page.
1.0 s
Speed Index shows how quickly the contents of a page are visibly populated.
Total size was 1,361 KiB
Large network payloads cost users real money and are highly correlated with long load times.
20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
532 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Potential savings of 340 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
0.7 s
First Contentful Paint marks the time at which the first text or image is painted.
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: