First visit
CO2 0.634g
SIZE 1.69 MB
Return visit
CO2 0.013g
SIZE 35.86 KB
First visit
CO2 0.634g
SIZE 1.69 MB
Return visit
CO2 0.013g
SIZE 35.86 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
Document
1
29.17 KB
0.011g
Font
4
571.93 KB
0.210g
Other
16
70.81 KB
0.026g
Script
46
812.34 KB
0.298g
Image
9
213.58 KB
0.078g
Fetch
12
29.55 KB
0.011g
520 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.17
Cumulative Layout Shift measures the movement of visible elements within the viewport.
2.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
0.3 s
First Contentful Paint marks the time at which the first text or image is painted.
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.
Potential savings of 83 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.
3.4 s
Speed Index shows how quickly the contents of a page are visibly populated.
Root document took 210 ms
Keep the server response time for the main document short because all other requests depend on it.
0.3 s
First Meaningful Paint measures when the primary content of a page is visible.
2.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Total size was 1,727 KiB
Large network payloads cost users real money and are highly correlated with long load times.
5.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
863 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
2.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
20 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.
1,050 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
1 resource found
A long cache lifetime can speed up repeat visits to your page.
One of the easiest things to do that instantly reduces your impact.
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: