First visit
CO2 0.300g
SIZE 405.01 KB
Return visit
CO2 0.003g
SIZE 4.22 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
Stylesheet
3
250.22 KB
0.185g
Script
6
150.57 KB
0.112g
Document
1
4.22 KB
0.003g
History
Date
CO2
Size
30.Mar.2022
0.300g
405.01 KB
09.Feb.2022
0.446g
601.65 KB
09.Feb.2022
0.447g
603.02 KB
08.Feb.2022
0.352g
474.85 KB
08.Feb.2022
0.352g
475.22 KB
07.Feb.2022
0.352g
475.22 KB
07.Feb.2022
0.352g
475.22 KB
07.Feb.2022
0.665g
897.86 KB
This website has been tested 8 times**
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.
Largest Contentful Paint
0.7 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.
Eliminate render-blocking resources
Potential savings of 200 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Reduce unused CSS
Potential savings of 240 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Reduce unused JavaScript
Potential savings of 89 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 405 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Time to Interactive
0.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
JavaScript execution time
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Serve static assets with an efficient cache policy
9 resources found
A long cache lifetime can speed up repeat visits to your page.
Enable text compression
Potential savings of 313 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
Minify CSS
Potential savings of 6 KiB
Minifying CSS files can reduce network payload sizes.
Initial server response time was short
Root document took 430 ms
Keep the server response time for the main document short because all other requests depend on it.
Minimizes main-thread work
0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Speed Index
0.8 s
Speed Index shows how quickly the contents of a page are visibly populated.
First Meaningful Paint
0.7 s
First Meaningful Paint measures when the primary content of a page is visible.
Avoids an excessive DOM size
212 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.
** This was only counted from 11.Apr.2021.
These measurements are for each new visitor, for returning visitors the footprint would be lower based on caching mechanisms.
Our brackets for the ratings: