First visit
CO2 0.262g
SIZE 845.91 KB
Return visit
CO2 0.163g
SIZE 525.72 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
22.58 KB
0.007g
Stylesheet
2
109.17 KB
0.034g
Script
5
291.38 KB
0.090g
Image
20
346.5 KB
0.108g
Font
1
75.68 KB
0.023g
XHR
1
606 B
0.000g
History
Date
CO2
Size
20.Oct.2024
0.262g
845.91 KB
05.Apr.2023
1.123g
1.48 MB
This website has been tested 2 times**
Core Web Vitals
Max Potential First Input Delay
30 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
Largest Contentful Paint
0.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Initial server response time was short
Root document took 50 ms
Keep the server response time for the main document short because all other requests depend on it.
Properly size images
Potential savings of 94 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Avoids an excessive DOM size
529 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
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.
Enable text compression
Potential savings of 66 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
Speed Index
1.1 s
Speed Index shows how quickly the contents of a page are visibly populated.
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.
Time to Interactive
0.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
First Contentful Paint
0.5 s
First Contentful Paint marks the time at which the first text or image is painted.
JavaScript execution time
0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Reduce unused CSS
Potential savings of 102 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Serve static assets with an efficient cache policy
23 resources found
A long cache lifetime can speed up repeat visits to your page.
Avoids enormous network payloads
Total size was 846 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Minimizes main-thread work
0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Eliminate render-blocking resources
Potential savings of 200 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
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: