First visit
CO2 0.133g
SIZE 427.15 KB
Return visit
CO2 0.052g
SIZE 169.03 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
Other
1
299 B
0.000g
Document
1
8.73 KB
0.003g
Script
6
162.68 KB
0.050g
Stylesheet
2
5.04 KB
0.002g
Image
21
163.39 KB
0.051g
Fetch
1
395 B
0.000g
Font
4
86.42 KB
0.027g
XHR
1
222 B
0.000g
History
Date
CO2
Size
09.Aug.2024
0.133g
427.15 KB
22.Mar.2023
0.308g
415.19 KB
27.Jan.2023
10.652g
12.72 MB
This website has been tested 3 times**
Core Web Vitals
Max Potential First Input Delay
100 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.378
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
1.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Avoids enormous network payloads
Total size was 427 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Speed Index
1.1 s
Speed Index shows how quickly the contents of a page are visibly populated.
Avoid multiple page redirects
Potential savings of 230 ms
Redirects introduce additional delays before the page can be loaded.
Server Backend Latencies
20 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.
Minimizes main-thread work
0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Avoids an excessive DOM size
318 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Time to Interactive
1.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Eliminate render-blocking resources
Potential savings of 450 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 68 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
First Meaningful Paint
0.9 s
First Meaningful Paint measures when the primary content of a page is visible.
Initial server response time was short
Root document took 110 ms
Keep the server response time for the main document short because all other requests depend on it.
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.
First Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted.
JavaScript execution time
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Total Blocking Time
70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Serve static assets with an efficient cache policy
26 resources found
A long cache lifetime can speed up repeat visits to your page.
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: