First visit
CO2 2.988g
SIZE 3.94 MB
Return visit
CO2 0.142g
SIZE 191.38 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
Script
5
1.44 MB
1.090g
Stylesheet
3
1.31 MB
0.991g
Font
13
922.87 KB
0.684g
Document
2
191.08 KB
0.142g
Image
6
87.71 KB
0.065g
Other
6
22.28 KB
0.017g
Third Party*
9
414.03 KB
0.307g
History
Date
CO2
Size
09.Feb.2023
2.988g
3.94 MB
08.Aug.2022
1.424g
1.88 MB
24.Apr.2022
0.063g
85.05 KB
24.Apr.2022
1.490g
1.96 MB
02.Apr.2022
1.563g
2.06 MB
31.Mar.2022
0.063g
85.24 KB
30.Mar.2022
0.063g
85.24 KB
28.Mar.2022
0.063g
85.26 KB
28.Mar.2022
0.063g
85.08 KB
28.Mar.2022
0.063g
85.26 KB
28.Mar.2022
0.063g
85.26 KB
This website has been tested 14 times**
Previous 10 test results are displayed above.
Core Web Vitals
Max Potential First Input Delay
90 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
Cumulative Layout Shift
0.483
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
4.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Reduce unused CSS
Potential savings of 1,170 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Speed Index
2.8 s
Speed Index shows how quickly the contents of a page are visibly populated.
Reduce initial server response time
Root document took 1,500 ms
Keep the server response time for the main document short because all other requests depend on it.
Minimizes main-thread work
1.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
First Meaningful Paint
0.6 s
First Meaningful Paint measures when the primary content of a page is visible.
Total Blocking Time
90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Time to Interactive
4.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
Avoid enormous network payloads
Total size was 4,032 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Enable text compression
Potential savings of 2,071 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
JavaScript execution time
0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Avoid an excessive DOM size
1,110 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Uses efficient cache policy on static assets
1 resource found
A long cache lifetime can speed up repeat visits to your page.
Eliminate render-blocking resources
Potential savings of 150 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 JavaScript
Potential savings of 932 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
First Contentful Paint
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
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: