First visit
CO2 2.430g
SIZE 6.47 MB
Return visit
CO2 0.238g
SIZE 649.43 KB
First visit
CO2 2.430g
SIZE 6.47 MB
Return visit
CO2 0.238g
SIZE 649.43 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
10
263.55 KB
0.097g
Stylesheet
12
180.56 KB
0.066g
Image
54
842.9 KB
0.309g
Script
68
3.8 MB
1.428g
Font
13
600.77 KB
0.220g
Other
5
5.07 KB
0.002g
XHR
29
146.81 KB
0.054g
Preflight
8
4.29 KB
0.002g
Fetch
7
687.58 KB
0.252g
560 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.007
Cumulative Layout Shift measures the movement of visible elements within the viewport.
2.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Total size was 6,624 KiB
Large network payloads cost users real money and are highly correlated with long load times.
45 resources found
A long cache lifetime can speed up repeat visits to your page.
Potential savings of 2,129 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Potential savings of 47 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
140 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.
Root document took 140 ms
Keep the server response time for the main document short because all other requests depend on it.
220 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Potential savings of 412 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
9.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
1.1 s
First Contentful Paint marks the time at which the first text or image is painted.
9.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
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.
7.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
3.9 s
Speed Index shows how quickly the contents of a page are visibly populated.
Potential savings of 276 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.
3,360 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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: