First visit
CO2 0.858g
SIZE 2.7 MB
Return visit
CO2 0.273g
SIZE 879.88 KB
First visit
CO2 0.858g
SIZE 2.7 MB
Return visit
CO2 0.273g
SIZE 879.88 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
Image
24
2.1 MB
0.666g
Script
9
387.62 KB
0.120g
Stylesheet
3
151.17 KB
0.047g
Font
3
57.19 KB
0.018g
Document
1
21.39 KB
0.007g
Other
3
2.08 KB
0.001g
100 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.001
Cumulative Layout Shift measures the movement of visible elements within the viewport.
2.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Potential savings of 1,336 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
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.
0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Potential savings of 220 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Potential savings of 1,065 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Total size was 2,766 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Potential savings of 454 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.
1.2 s
First Meaningful Paint measures when the primary content of a page is visible.
0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
684 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
310 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.4 s
Speed Index shows how quickly the contents of a page are visibly populated.
Potential savings of 186 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Potential savings of 98 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Root document took 200 ms
Keep the server response time for the main document short because all other requests depend on it.
1.2 s
First Contentful Paint marks the time at which the first text or image is painted.
24 resources found
A long cache lifetime can speed up repeat visits to your page.
1.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
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: