First visit
CO2 0.961g
SIZE 3.02 MB
Return visit
CO2 0.235g
SIZE 756.47 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
Document
3
93.39 KB
0.029g
Stylesheet
4
254.97 KB
0.079g
Image
17
464.56 KB
0.144g
Script
23
1.97 MB
0.626g
Font
8
168.53 KB
0.052g
Preflight
3
1.52 KB
0.000g
XHR
20
94.29 KB
0.029g
History
Date
CO2
Size
13.Nov.2024
0.961g
3.02 MB
16.Feb.2024
0.935g
2.49 MB
19.May.2022
1.430g
1.71 MB
This website has been tested 3 times**
Core Web Vitals
Max Potential First Input Delay
370 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.063
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
2.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Speed Index
2.5 s
Speed Index shows how quickly the contents of a page are visibly populated.
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 149 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
19 resources found
A long cache lifetime can speed up repeat visits to your page.
Reduce unused JavaScript
Potential savings of 1,180 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Minimize main-thread work
3.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Time to Interactive
4.2 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 3,096 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Serve images in next-gen formats
Potential savings of 164 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Total Blocking Time
620 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time
2.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
First Contentful Paint
1.5 s
First Contentful Paint marks the time at which the first text or image is painted.
Avoids an excessive DOM size
526 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance.
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.
Server Backend Latencies
0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance.
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: