First visit
CO2 1.681g
SIZE 2.01 MB
Return visit
CO2 1.363g
SIZE 1.63 MB
Emissions calculator
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
7
1.36 MB
1.142g
Script
20
332.75 KB
0.272g
Font
4
177.67 KB
0.145g
Other
7
77.07 KB
0.063g
Stylesheet
4
41.33 KB
0.034g
Document
1
30.05 KB
0.025g
Core Web Vitals
Max Potential First Input Delay
60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
Cumulative Layout Shift
0.214
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
3.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Efficiently encode images
Potential savings of 750 KiB
Optimized images load faster and consume less cellular data.
Enable text compression
Potential savings of 23 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
Minify JavaScript
Potential savings of 6 KiB
Minifying JavaScript files can reduce payload sizes and script parse time.
JavaScript execution time
0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Eliminate render-blocking resources
Potential savings of 460 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Reduce initial server response time
Root document took 650 ms
Keep the server response time for the main document short because all other requests depend on it.
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Meaningful Paint
0.9 s
First Meaningful Paint measures when the primary content of a page is visible.
Time to Interactive
1.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
Minimizes main-thread work
0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Avoids an excessive DOM size
388 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Speed Index
1.5 s
Speed Index shows how quickly the contents of a page are visibly populated.
Serve static assets with an efficient cache policy
25 resources found
A long cache lifetime can speed up repeat visits to your page.
First Contentful Paint
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
Avoids enormous network payloads
Total size was 2,055 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Reduce unused CSS
Potential savings of 36 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Reduce unused JavaScript
Potential savings of 62 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Properly size images
Potential savings of 1,041 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Serve images in next-gen formats
Potential savings of 1,119 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Switch to green hosting
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: