First visit
CO2 0.244g
SIZE 785.66 KB
Return visit
CO2 0.242g
SIZE 780.62 KB
First visit
CO2 0.244g
SIZE 785.66 KB
Return visit
CO2 0.242g
SIZE 780.62 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
55.25 KB
0.017g
Stylesheet
17
83.48 KB
0.026g
Script
3
120.21 KB
0.037g
Image
11
354.99 KB
0.110g
Font
4
167.25 KB
0.052g
XHR
1
4.49 KB
0.001g
History
Date
CO2
Size
15.Oct.2023
0.244g
785.66 KB
15.Oct.2023
0.244g
785.66 KB
This website has been tested 2 times**
60 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.424
Cumulative Layout Shift measures the movement of visible elements within the viewport.
0.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Potential savings of 176 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
10 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.
35 resources found
A long cache lifetime can speed up repeat visits to your page.
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
0.6 s
First Meaningful Paint measures when the primary content of a page is visible.
1,401 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Total size was 786 KiB
Large network payloads cost users real money and are highly correlated with long load times.
0.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
1.1 s
Speed Index shows how quickly the contents of a page are visibly populated.
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.
Root document took 1,080 ms
Keep the server response time for the main document short because all other requests depend on it.
Potential savings of 61 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
0.1 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.
** This was only counted from 11.Apr.2021.
These measurements are for each new visitor, for returning visitors the footprint would be lower based on caching mechanisms.
Our brackets for the ratings: