First visit
CO2 2.635g
SIZE 3.15 MB
Return visit
CO2 2.233g
SIZE 2.67 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
76
2.2 MB
1.838g
Script
14
754.37 KB
0.617g
Document
6
120.51 KB
0.099g
Stylesheet
6
88.6 KB
0.072g
Font
1
5.96 KB
0.005g
Other
6
4.65 KB
0.004g
Core Web Vitals
Max Potential First Input Delay
50 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
Cumulative Layout Shift
0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
2.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
First Contentful Paint
0.7 s
First Contentful Paint marks the time at which the first text or image is painted.
Minimizes main-thread work
1.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Speed Index
2.1 s
Speed Index shows how quickly the contents of a page are visibly populated.
Avoid enormous network payloads
Total size was 3,222 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Eliminate render-blocking resources
Potential savings of 140 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Time to Interactive
0.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
Reduce unused CSS
Potential savings of 52 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 35 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers.
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.
Reduce unused JavaScript
Potential savings of 400 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Enable text compression
Potential savings of 160 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
Avoids an excessive DOM size
350 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Reduce initial server response time
Root document took 620 ms
Keep the server response time for the main document short because all other requests depend on it.
Serve images in next-gen formats
Potential savings of 937 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
First Meaningful Paint
0.7 s
First Meaningful Paint measures when the primary content of a page is visible.
Serve static assets with an efficient cache policy
11 resources found
A long cache lifetime can speed up repeat visits to your page.
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: