First visit
CO2 0.310g
SIZE 997.45 KB
Return visit
CO2 0.033g
SIZE 106.23 KB
First visit
CO2 0.310g
SIZE 997.45 KB
Return visit
CO2 0.033g
SIZE 106.23 KB
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
23
648.74 KB
0.201g
Script
19
262.31 KB
0.081g
Document
1
35.74 KB
0.011g
Font
3
30.39 KB
0.009g
Stylesheet
1
11.09 KB
0.003g
Image
2
9.18 KB
0.003g
40 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
0.257
Cumulative Layout Shift measures the movement of visible elements within the viewport.
1.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Root document took 100 ms
Keep the server response time for the main document short because all other requests depend on it.
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
780 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.
0.6 s
First Meaningful Paint measures when the primary content of a page is visible.
0.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Potential savings of 33 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Total size was 997 KiB
Large network payloads cost users real money and are highly correlated with long load times.
9 resources found
A long cache lifetime can speed up repeat visits to your page.
0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
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.
534 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Potential savings of 230 ms
Redirects introduce additional delays before the page can be loaded.
0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
0.8 s
Speed Index shows how quickly the contents of a page are visibly populated.
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: