First visit
CO2 0.141g
SIZE 455.79 KB
Return visit
CO2 0.019g
SIZE 60.11 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
1
58.54 KB
0.018g
Font
2
74.14 KB
0.023g
Stylesheet
2
7.97 KB
0.002g
Script
19
312.11 KB
0.097g
XHR
3
3.03 KB
0.001g
History
Date
CO2
Size
26.Jun.2024
0.141g
455.79 KB
26.Jun.2024
0.141g
455.77 KB
23.Apr.2024
0.170g
548.96 KB
This website has been tested 3 times**
Core Web Vitals
Max Potential First Input Delay
500 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
Largest Contentful Paint
0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
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.
Avoids enormous network payloads
Total size was 456 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Serve static assets with an efficient cache policy
1 resource found
A long cache lifetime can speed up repeat visits to your page.
First Contentful Paint
0.3 s
First Contentful Paint marks the time at which the first text or image is painted.
JavaScript execution time
0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Minimizes main-thread work
1.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Reduce unused JavaScript
Potential savings of 65 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Time to Interactive
1.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Total Blocking Time
540 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Avoid an excessive DOM size
1,463 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
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.
Speed Index
1.9 s
Speed Index shows how quickly the contents of a page are visibly populated.
First Meaningful Paint
0.3 s
First Meaningful Paint measures when the primary content of a page is visible.
Reduce initial server response time
Root document took 680 ms
Keep the server response time for the main document short because all other requests depend on it.
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: