First visit
CO2 4.208g
SIZE 5.03 MB
Return visit
CO2 4.200g
SIZE 5.02 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
3.99 MB
3.339g
Script
11
449.89 KB
0.368g
Other
6
298.65 KB
0.244g
Document
1
287.91 KB
0.235g
Font
2
25.78 KB
0.021g
Stylesheet
1
1.11 KB
0.001g
Core Web Vitals
Max Potential First Input Delay
390 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
Cumulative Layout Shift
0.22
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
2.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
JavaScript execution time
0.8 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
264 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Speed Index
2.4 s
Speed Index shows how quickly the contents of a page are visibly populated.
Enable text compression
Potential savings of 31 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
Initial server response time was short
Root document took 180 ms
Keep the server response time for the main document short because all other requests depend on it.
First Meaningful Paint
0.9 s
First Meaningful Paint measures when the primary content of a page is visible.
Reduce unused JavaScript
Potential savings of 167 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 3,699 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Efficiently encode images
Potential savings of 108 KiB
Optimized images load faster and consume less cellular data.
Uses efficient cache policy on static assets
2 resources found
A long cache lifetime can speed up repeat visits to your page.
Minimizes main-thread work
1.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Avoid enormous network payloads
Total size was 5,146 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Eliminate render-blocking resources
Potential savings of 410 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Serve images in next-gen formats
Potential savings of 1,825 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Time to Interactive
3.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
Total Blocking Time
410 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted.
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: