First visit
CO2 0.661g
SIZE 1.76 MB
Return visit
CO2 0.191g
SIZE 519.45 KB
First visit
CO2 0.661g
SIZE 1.76 MB
Return visit
CO2 0.191g
SIZE 519.45 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
49.55 KB
0.018g
Stylesheet
6
24.55 KB
0.009g
Image
19
1.25 MB
0.471g
Script
11
155.92 KB
0.057g
Font
3
289.43 KB
0.106g
140 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.452
Cumulative Layout Shift measures the movement of visible elements within the viewport.
1.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Root document took 1,260 ms
Keep the server response time for the main document short because all other requests depend on it.
0 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.
Total size was 1,803 KiB
Large network payloads cost users real money and are highly correlated with long load times.
2.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
1.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
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.
300 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
2.4 s
Speed Index shows how quickly the contents of a page are visibly populated.
1,560 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Potential savings of 74 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
20 resources found
A long cache lifetime can speed up repeat visits to your page.
Potential savings of 324 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
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: