First visit
CO2 0.134g
SIZE 431.87 KB
Return visit
CO2 0.061g
SIZE 195.97 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
6.99 KB
0.002g
Script
5
272.45 KB
0.085g
Stylesheet
1
10.88 KB
0.003g
Image
4
6.94 KB
0.002g
Font
2
133.83 KB
0.042g
Fetch
1
797 B
0.000g
History
Date
CO2
Size
21.Sep.2025
0.134g
431.87 KB
01.Jul.2025
0.131g
421.54 KB
05.Apr.2023
0.240g
324.05 KB
11.Dec.2021
0.222g
298.94 KB
07.Dec.2021
0.221g
298.89 KB
07.Dec.2021
0.321g
432.8 KB
07.Dec.2021
0.221g
298.85 KB
07.Dec.2021
0.273g
367.74 KB
07.Dec.2021
0.324g
437.18 KB
04.Dec.2021
0.312g
420.5 KB
03.Dec.2021
0.312g
420.47 KB
This website has been tested 12 times**
Previous 10 test results are displayed above.
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
0.9 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
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.
Avoids enormous network payloads
Total size was 432 KiB
Large network payloads cost users real money and are highly correlated with long load times.
First Contentful Paint
0.4 s
First Contentful Paint marks the time at which the first text or image is painted.
Reduce initial server response time
Root document took 650 ms
Keep the server response time for the main document short because all other requests depend on it.
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index
1.2 s
Speed Index shows how quickly the contents of a page are visibly populated.
Avoids an excessive DOM size
523 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Time to Interactive
0.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Reduce unused JavaScript
Est savings of 104 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Network Round Trip Times
10 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.
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 120 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.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
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: