First visit
CO2 1.105g
SIZE 3.48 MB
Return visit
CO2 0.019g
SIZE 60.71 KB
First visit
CO2 1.105g
SIZE 3.48 MB
Return visit
CO2 0.019g
SIZE 60.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
1
18.59 KB
0.006g
Stylesheet
1
20.67 KB
0.006g
Script
8
797.98 KB
0.248g
Image
43
1.38 MB
0.440g
Other
1
6.74 KB
0.002g
Font
4
232.02 KB
0.072g
XHR
4
1002.52 KB
0.311g
Fetch
1
64.47 KB
0.020g
450 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.
4.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
1.6 s
First Meaningful Paint measures when the primary content of a page is visible.
3.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Potential savings of 1,092 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
4.7 s
Speed Index shows how quickly the contents of a page are visibly populated.
1,341 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Potential savings of 132 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Potential savings of 156 KiB
Optimized images load faster and consume less cellular data.
4.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
660 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
2 resources found
A long cache lifetime can speed up repeat visits to your page.
Total size was 3,561 KiB
Large network payloads cost users real money and are highly correlated with long load times.
620 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.
2.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Potential savings of 397 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
1.6 s
First Contentful Paint marks the time at which the first text or image is painted.
Root document took 1,210 ms
Keep the server response time for the main document short because all other requests depend on it.
Potential savings of 126 KiB
Minifying JavaScript files can reduce payload sizes and script parse time.
Potential savings of 590 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 44 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
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.
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: