First visit
CO2 0.100g
SIZE 322.49 KB
Return visit
CO2 0.024g
SIZE 76.47 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
Other
1
693 B
0.000g
Document
1
26.93 KB
0.008g
Stylesheet
1
19.68 KB
0.006g
Script
3
52.24 KB
0.016g
Font
4
42.47 KB
0.013g
Image
30
180.49 KB
0.056g
History
Date
CO2
Size
14.Jun.2025
0.100g
322.49 KB
16.Jan.2024
0.065g
209.55 KB
20.Nov.2023
0.068g
218.81 KB
04.Oct.2023
0.058g
188.21 KB
11.Aug.2023
0.066g
212.56 KB
24.Jun.2023
0.088g
284.2 KB
19.Jun.2023
0.088g
283.64 KB
16.Jun.2023
0.088g
283.85 KB
This website has been tested 8 times**
Core Web Vitals
Max Potential First Input Delay
20 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.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Avoid multiple page redirects
Est savings of 230 ms
Redirects introduce additional delays before the page can be loaded.
Properly size images
Est savings of 36 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
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.
Initial server response time was short
Root document took 250 ms
Keep the server response time for the main document short because all other requests depend on it.
Avoid an excessive DOM size
2,476 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Time to Interactive
0.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
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.
Serve static assets with an efficient cache policy
10 resources found
A long cache lifetime can speed up repeat visits to your page.
Minimizes main-thread work
0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
JavaScript execution time
0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Avoids enormous network payloads
Total size was 322 KiB
Large network payloads cost users real money and are highly correlated with long load times.
First Contentful Paint
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
Speed Index
0.7 s
Speed Index shows how quickly the contents of a page are visibly populated.
Reduce unused CSS
Est savings of 12 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
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: