First visit
CO2 0.158g
SIZE 510.63 KB
Return visit
CO2 0.026g
SIZE 83.79 KB
First visit
CO2 0.158g
SIZE 510.63 KB
Return visit
CO2 0.026g
SIZE 83.79 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
16.64 KB
0.005g
Stylesheet
10
38.45 KB
0.012g
Script
15
272.5 KB
0.085g
Image
13
45.53 KB
0.014g
Font
4
134.44 KB
0.042g
Fetch
2
2.4 KB
0.001g
Preflight
1
696 B
0.000g
80 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.083
Cumulative Layout Shift measures the movement of visible elements within the viewport.
0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Potential savings of 62 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
0.7 s
Speed Index shows how quickly the contents of a page are visibly populated.
550 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.
357 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Root document took 50 ms
Keep the server response time for the main document short because all other requests depend on it.
Total size was 511 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Potential savings of 14 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
35 resources found
A long cache lifetime can speed up repeat visits to your page.
1.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
0.6 s
First Meaningful Paint measures when the primary content of a page is visible.
0.2 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: