First visit
CO2 0.902g
SIZE 1.08 MB
Return visit
CO2 0.603g
SIZE 737.03 KB
First visit
CO2 0.902g
SIZE 1.08 MB
Return visit
CO2 0.603g
SIZE 737.03 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
Image
10
480.15 KB
0.393g
Font
20
274.06 KB
0.224g
Script
26
178.13 KB
0.146g
Stylesheet
10
60.64 KB
0.050g
Other
2
58.11 KB
0.048g
Document
1
51.61 KB
0.042g
60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
0.003
Cumulative Layout Shift measures the movement of visible elements within the viewport.
1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Total size was 1,103 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Potential savings of 45 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
12 resources found
A long cache lifetime can speed up repeat visits to your page.
Potential savings of 104 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
First Meaningful Paint measures when the primary content of a page is visible.
Potential savings of 294 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
0.7 s
First Contentful Paint marks the time at which the first 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.
0.9 s
Speed Index shows how quickly the contents of a page are visibly populated.
0.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
1,013 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Potential savings of 183 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Potential savings of 10 KiB
Minifying CSS files can reduce network payload sizes.
Root document took 180 ms
Keep the server response time for the main document short because all other requests depend on it.
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: