First visit
CO2 0.296g
SIZE 953.66 KB
Return visit
CO2 0.017g
SIZE 56.22 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
4.57 KB
0.001g
Stylesheet
2
38.4 KB
0.012g
Script
11
454.18 KB
0.141g
Image
9
56.75 KB
0.018g
Font
18
393.18 KB
0.122g
Fetch
2
403 B
0.000g
XHR
3
2.19 KB
0.001g
Other
3
3.99 KB
0.001g
Core Web Vitals
Max Potential First Input Delay
70 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
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
0.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Serve images in next-gen formats
Potential savings of 23 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
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Network Round Trip Times
10 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.
Speed Index
0.9 s
Speed Index shows how quickly the contents of a page are visibly populated.
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.
Eliminate render-blocking resources
Potential savings of 490 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Avoids enormous network payloads
Total size was 954 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Serve static assets with an efficient cache policy
5 resources found
A long cache lifetime can speed up repeat visits to your page.
Server Backend Latencies
10 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.
JavaScript execution time
0.4 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
173 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
First Meaningful Paint
0.7 s
First Meaningful Paint measures when the primary content of a page is visible.
First Contentful Paint
0.7 s
First Contentful Paint marks the time at which the first text or image is painted.
Time to Interactive
1.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Minimizes main-thread work
0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
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: