First visit
CO2 0.257g
SIZE 700.46 KB
Return visit
CO2 0.019g
SIZE 50.5 KB
Emissions calculator
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
48.77 KB
0.018g
Stylesheet
19
44.4 KB
0.016g
Script
21
262.39 KB
0.096g
Image
6
181.38 KB
0.067g
Font
7
159.89 KB
0.059g
Fetch
1
1.98 KB
0.001g
XHR
2
1.64 KB
0.001g
History
Date
CO2
Size
26.Dec.2024
0.257g
700.46 KB
10.Apr.2024
0.220g
599.21 KB
10.Apr.2024
0.220g
599.21 KB
This website has been tested 3 times**
Core Web Vitals
Max Potential First Input Delay
50 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
Cumulative Layout Shift
0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Reduce unused CSS
Potential savings of 31 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
First Contentful Paint
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
Serve static assets with an efficient cache policy
3 resources found
A long cache lifetime can speed up repeat visits to your page.
Reduce unused JavaScript
Potential savings of 103 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Eliminate render-blocking resources
Potential savings of 40 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Time to Interactive
1.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Network Round Trip Times
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.
Avoids enormous network payloads
Total size was 700 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Serve images in next-gen formats
Potential savings of 99 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Server Backend Latencies
0 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.
Avoids an excessive DOM size
658 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Minimizes main-thread work
0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Properly size images
Potential savings of 136 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
JavaScript execution time
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Initial server response time was short
Root document took 60 ms
Keep the server response time for the main document short because all other requests depend on it.
Speed Index
0.7 s
Speed Index shows how quickly the contents of a page are visibly populated.
Switch to green hosting
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: