First visit
CO2 0.220g
SIZE 600.16 KB
Return visit
CO2 0.017g
SIZE 46.58 KB
First visit
CO2 0.220g
SIZE 600.16 KB
Return visit
CO2 0.017g
SIZE 46.58 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
44.86 KB
0.016g
Stylesheet
15
34.21 KB
0.013g
Script
21
257.61 KB
0.095g
Image
5
109.89 KB
0.040g
Font
7
151.97 KB
0.056g
Fetch
2
771 B
0.000g
XHR
1
886 B
0.000g
History
Date
CO2
Size
09.Apr.2024
0.220g
600.16 KB
09.Apr.2024
0.220g
600.16 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.02
Cumulative Layout Shift measures the movement of visible elements within the viewport.
2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
1.0 s
First Meaningful Paint measures when the primary content of a page is visible.
1.0 s
First Contentful Paint marks the time at which the first text or image is painted.
643 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Potential savings of 105 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
40 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.
3 resources found
A long cache lifetime can speed up repeat visits to your page.
1.1 s
Speed Index shows how quickly the contents of a page are visibly populated.
1.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Potential savings of 90 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Total size was 600 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Root document took 70 ms
Keep the server response time for the main document short because all other requests depend on it.
Potential savings of 270 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP.
Potential savings of 30 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
220 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.
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.
** 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: