First visit
CO2 1.100g
SIZE 1.45 MB
Return visit
CO2 0.908g
SIZE 1.2 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
5
1.07 MB
0.812g
Font
3
224.3 KB
0.166g
Script
2
112.66 KB
0.083g
Stylesheet
2
37.1 KB
0.027g
Document
1
14.57 KB
0.011g
Other
1
660 B
0.000g
Core Web Vitals
Max Potential First Input Delay
110 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
Cumulative Layout Shift
0
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
First Meaningful Paint
0.4 s
First Meaningful Paint measures when the primary content of a page is visible.
Reduce unused JavaScript
Potential savings of 80 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,484 KiB
Large network payloads cost users real money and are highly correlated with long load times.
First Contentful Paint
0.4 s
First Contentful Paint marks the time at which the first text or image is painted.
Total Blocking Time
40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Properly size images
Potential savings of 783 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Eliminate render-blocking resources
Potential savings of 40 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Speed Index
0.4 s
Speed Index shows how quickly the contents of a page are visibly populated.
Reduce unused CSS
Potential savings of 29 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Serve static assets with an efficient cache policy
11 resources found
A long cache lifetime can speed up repeat visits to your page.
Minimizes main-thread work
0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Initial server response time was short
Root document took 100 ms
Keep the server response time for the main document short because all other requests depend on it.
Time to Interactive
0.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
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.
Serve images in next-gen formats
Potential savings of 1,003 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Avoids an excessive DOM size
446 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
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: