First visit
CO2 0.405g
SIZE 1.27 MB
Return visit
CO2 0.078g
SIZE 249.86 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
30
636.3 KB
0.197g
Script
21
401.22 KB
0.124g
Image
14
179.2 KB
0.056g
Document
2
57.07 KB
0.018g
Font
2
20.34 KB
0.006g
Stylesheet
1
11.08 KB
0.003g
Core Web Vitals
Max Potential First Input Delay
50 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.03
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
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.
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.
First Meaningful Paint
0.5 s
First Meaningful Paint measures when the primary content of a page is visible.
First Contentful Paint
0.5 s
First Contentful Paint marks the time at which the first text or image is painted.
Time to Interactive
0.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Preload Largest Contentful Paint image
Potential savings of 240 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP.
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
310 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.
Serve static assets with an efficient cache policy
11 resources found
A long cache lifetime can speed up repeat visits to your page.
Avoids enormous network payloads
Total size was 1,305 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Reduce unused JavaScript
Potential savings of 106 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Speed Index
1.0 s
Speed Index shows how quickly the contents of a page are visibly populated.
Avoids an excessive DOM size
626 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Avoid multiple page redirects
Potential savings of 220 ms
Redirects introduce additional delays before the page can be loaded.
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.
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: