First visit
CO2 0.557g
SIZE 1.75 MB
Return visit
CO2 0.068g
SIZE 220.6 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
4
20.27 KB
0.006g
Stylesheet
2
40.76 KB
0.013g
Script
17
1.27 MB
0.402g
Image
13
206.25 KB
0.064g
Font
4
222.17 KB
0.069g
Fetch
8
5.36 KB
0.002g
XHR
2
5.69 KB
0.002g
History
Date
CO2
Size
10.Nov.2024
0.557g
1.75 MB
10.Nov.2024
0.557g
1.75 MB
This website has been tested 2 times**
Core Web Vitals
Max Potential First Input Delay
370 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
Total Blocking Time
340 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index
2.6 s
Speed Index shows how quickly the contents of a page are visibly populated.
Initial server response time was short
Root document took 150 ms
Keep the server response time for the main document short because all other requests depend on it.
Serve static assets with an efficient cache policy
2 resources found
A long cache lifetime can speed up repeat visits to your page.
First Contentful Paint
1.0 s
First Contentful Paint marks the time at which the first text or image is painted.
Reduce unused JavaScript
Potential savings of 382 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Minimizes main-thread work
2.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 1,797 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Time to Interactive
2.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
JavaScript execution time
1.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
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.
Avoid an excessive DOM size
1,300 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Eliminate render-blocking resources
Potential savings of 760 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Serve images in next-gen formats
Potential savings of 30 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
10 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.
Properly size images
Potential savings of 94 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
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: