First visit
CO2 0.825g
SIZE 2.2 MB
Return visit
CO2 0.091g
SIZE 247.28 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
26.34 KB
0.010g
Stylesheet
28
48.87 KB
0.018g
Script
30
177.03 KB
0.065g
Image
13
1.6 MB
0.600g
Font
9
361.72 KB
0.133g
History
Date
CO2
Size
17.Jul.2025
0.825g
2.2 MB
16.Jul.2025
0.825g
2.2 MB
16.Jul.2025
1.704g
4.54 MB
16.Jul.2025
1.733g
4.61 MB
This website has been tested 4 times**
Core Web Vitals
Max Potential First Input Delay
40 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.005
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
2.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Serve static assets with an efficient cache policy
75 resources found
A long cache lifetime can speed up repeat visits to your page.
Time to Interactive
2.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Speed Index
3.1 s
Speed Index shows how quickly the contents of a page are visibly populated.
Minimizes main-thread work
1.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Avoid serving legacy JavaScript to modern browsers
Est savings of 9 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers.
Learn why most sites can deploy ES6+ code without transpiling
Avoids enormous network payloads
Total size was 2,249 KiB
Large network payloads cost users real money and are highly correlated with long load times.
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.
Eliminate render-blocking resources
Est savings of 230 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
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.
Reduce unused JavaScript
Est savings of 21 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Properly size images
Est savings of 331 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Reduce initial server response time
Root document took 1,240 ms
Keep the server response time for the main document short because all other requests depend on it.
Avoids an excessive DOM size
571 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
First Contentful Paint
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
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.
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: