First visit
CO2 0.065g
SIZE 208.32 KB
Return visit
CO2 0.008g
SIZE 24.4 KB
First visit
CO2 0.065g
SIZE 208.32 KB
Return visit
CO2 0.008g
SIZE 24.4 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
1
959 B
0.000g
Document
1
22.43 KB
0.007g
Stylesheet
2
6.55 KB
0.002g
Script
4
6.36 KB
0.002g
Image
7
86.86 KB
0.027g
Font
1
80.18 KB
0.025g
XHR
3
3.03 KB
0.001g
Fetch
1
1.96 KB
0.001g
20 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.036
Cumulative Layout Shift measures the movement of visible elements within the viewport.
0.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it.
0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
0.5 s
First Contentful Paint marks the time at which the first text or image is painted.
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.
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.
0.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
0.8 s
Speed Index shows how quickly the contents of a page are visibly populated.
Potential savings of 230 ms
Redirects introduce additional delays before the page can be loaded.
2 resources found
A long cache lifetime can speed up repeat visits to your page.
279 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Total size was 208 KiB
Large network payloads cost users real money and are highly correlated with long load times.
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: