First visit
CO2 0.092g
SIZE 295.76 KB
Return visit
CO2 0.017g
SIZE 55.58 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
31.47 KB
0.010g
Stylesheet
3
56.96 KB
0.018g
Script
6
103.21 KB
0.032g
Image
15
96.87 KB
0.030g
Fetch
1
971 B
0.000g
XHR
2
6.3 KB
0.002g
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.
Learn more about the Maximum Potential First Input Delay metric
Largest Contentful Paint
0.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Speed Index
0.8 s
Speed Index shows how quickly the contents of a page are visibly populated.
Total Blocking Time
20 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
17 resources found
A long cache lifetime can speed up repeat visits to your page.
Avoid an excessive DOM size
1,542 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
First Contentful Paint
0.4 s
First Contentful Paint marks the time at which the first text or image is painted.
Server Backend Latencies
30 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.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Initial server response time was short
Root document took 140 ms
Keep the server response time for the main document short because all other requests depend on it.
Time to Interactive
0.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Avoids enormous network payloads
Total size was 296 KiB
Large network payloads cost users real money and are highly correlated with long load times.
JavaScript execution time
0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Network Round Trip Times
20 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.
Reduce unused JavaScript
Potential savings of 56 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Notes
* These are assets not hosted on the same domain e.g. tracking scripts, iframe embeds, or files hosted on a CDN.
These measurements are for each new visitor, for returning visitors the footprint would be lower based on caching mechanisms.
Our brackets for the ratings: