First visit
CO2 0.561g
SIZE 1.49 MB
Return visit
CO2 0.543g
SIZE 1.45 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
Script
26
753.1 KB
0.276g
Image
11
588.94 KB
0.216g
Font
2
82.39 KB
0.030g
Stylesheet
20
76.82 KB
0.028g
Document
1
18.43 KB
0.007g
Other
2
10.14 KB
0.004g
Core Web Vitals
Max Potential First Input Delay
70 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
Learn more about the Maximum Potential First Input Delay metric
Cumulative Layout Shift
0.065
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
1.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Reduce initial server response time
Root document took 710 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 421 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Eliminate render-blocking resources
Potential savings of 1,410 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Total Blocking Time
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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.
Minify JavaScript
Potential savings of 50 KiB
Minifying JavaScript files can reduce payload sizes and script parse time.
First Meaningful Paint
1.2 s
First Meaningful Paint measures when the primary content of a page is visible.
Serve static assets with an efficient cache policy
51 resources found
A long cache lifetime can speed up repeat visits to your page.
Avoid an excessive DOM size
933 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Reduce unused CSS
Potential savings of 31 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
First Contentful Paint
1.2 s
First Contentful Paint marks the time at which the first text or image is painted.
Time to Interactive
2.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Reduce unused JavaScript
Potential savings of 479 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Avoids enormous network payloads
Total size was 1,530 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Efficiently encode images
Potential savings of 208 KiB
Optimized images load faster and consume less cellular data.
Speed Index
7.5 s
Speed Index shows how quickly the contents of a page are visibly populated.
Properly size images
Potential savings of 246 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Minimizes main-thread work
0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
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: