First visit
CO2 2.799g
SIZE 3.69 MB
Return visit
CO2 2.585g
SIZE 3.41 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
23
2.86 MB
2.171g
Script
29
601.12 KB
0.445g
Document
2
124.07 KB
0.092g
Stylesheet
7
80.91 KB
0.060g
Font
3
36.06 KB
0.027g
Other
6
5.39 KB
0.004g
Core Web Vitals
Max Potential First Input Delay
20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
Cumulative Layout Shift
0.123
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Eliminate render-blocking resources
Potential savings of 560 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
First Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted.
Time to Interactive
0.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
First Meaningful Paint
0.9 s
First Meaningful Paint measures when the primary content of a page is visible.
Reduce unused CSS
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.
Serve images in next-gen formats
Potential savings of 1,641 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Initial server response time was short
Root document took 230 ms
Keep the server response time for the main document short because all other requests depend on it.
Avoid enormous network payloads
Total size was 3,777 KiB
Large network payloads cost users real money and are highly correlated with long load times.
JavaScript execution time
0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Minimizes main-thread work
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
654 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Speed Index
0.9 s
Speed Index shows how quickly the contents of a page are visibly populated.
Properly size images
Potential savings of 2,428 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Serve static assets with an efficient cache policy
21 resources found
A long cache lifetime can speed up repeat visits to your page.
Reduce unused JavaScript
Potential savings of 307 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Efficiently encode images
Potential savings of 109 KiB
Optimized images load faster and consume less cellular data.
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: