First visit
CO2 0.585g
SIZE 1.84 MB
Return visit
CO2 0.011g
SIZE 35.25 KB
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
18
945.29 KB
0.293g
Script
10
459.26 KB
0.143g
Font
4
188.29 KB
0.058g
Stylesheet
1
168.83 KB
0.052g
Other
11
105.97 KB
0.033g
Document
1
16.97 KB
0.005g
Core Web Vitals
Max Potential First Input Delay
210 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.107
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Reduce unused CSS
Potential savings of 161 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Time to Interactive
2.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
First Meaningful Paint
1.1 s
First Meaningful Paint measures when the primary content of a page is visible.
Minify CSS
Potential savings of 12 KiB
Minifying CSS files can reduce network payload sizes.
Reduce unused JavaScript
Potential savings of 217 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
First Contentful Paint
1.1 s
First Contentful Paint marks the time at which the first text or image is painted.
Uses efficient cache policy on static assets
3 resources found
A long cache lifetime can speed up repeat visits to your page.
Preload Largest Contentful Paint image
Potential savings of 510 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP.
Avoid an excessive DOM size
1,758 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Total Blocking Time
140 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Initial server response time was short
Root document took 90 ms
Keep the server response time for the main document short because all other requests depend on it.
Avoids enormous network payloads
Total size was 1,885 KiB
Large network payloads cost users real money and are highly correlated with long load times.
JavaScript execution time
1.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Speed Index
2.0 s
Speed Index shows how quickly the contents of a page are visibly populated.
Minimize main-thread work
2.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Eliminate render-blocking resources
Potential savings of 650 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
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: