First visit
CO2 0.339g
SIZE 1.07 MB
Return visit
CO2 0.119g
SIZE 383.71 KB
First visit
CO2 0.339g
SIZE 1.07 MB
Return visit
CO2 0.119g
SIZE 383.71 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
2
228.55 KB
0.071g
Script
27
654.83 KB
0.203g
Image
41
208.64 KB
0.065g
Stylesheet
1
868 B
0.000g
70 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
1.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
0.7 s
First Meaningful Paint measures when the primary content of a page is visible.
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
Total size was 1,093 KiB
Large network payloads cost users real money and are highly correlated with long load times.
31 resources found
A long cache lifetime can speed up repeat visits to your page.
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
0.7 s
Speed Index shows how quickly the contents of a page are visibly populated.
3.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Root document took 30 ms
Keep the server response time for the main document short because all other requests depend on it.
1,183 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
170 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
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
20 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.6 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: