First visit
CO2 0.565g
SIZE 1.78 MB
Return visit
CO2 0.073g
SIZE 234.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
1
17.1 KB
0.005g
Stylesheet
8
66.37 KB
0.021g
Script
9
331.93 KB
0.103g
Image
32
1.33 MB
0.424g
Font
3
35.91 KB
0.011g
XHR
3
2.26 KB
0.001g
Other
3
3.35 KB
0.001g
History
Date
CO2
Size
27.Feb.2025
0.565g
1.78 MB
20.Jan.2025
1.058g
3.33 MB
10.Dec.2024
0.754g
2.37 MB
19.May.2022
2.166g
2.59 MB
26.Nov.2021
1.722g
2.06 MB
18.Nov.2021
2.083g
2.49 MB
This website has been tested 6 times**
Core Web Vitals
Max Potential First Input Delay
330 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
2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
First Contentful Paint
0.7 s
First Contentful Paint marks the time at which the first text or image is painted.
Defer offscreen images
Potential savings of 495 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.
Speed Index
1.6 s
Speed Index shows how quickly the contents of a page are visibly populated.
Avoids enormous network payloads
Total size was 1,822 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Serve static assets with an efficient cache policy
36 resources found
A long cache lifetime can speed up repeat visits to your page.
JavaScript execution time
0.5 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 420 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Minimizes main-thread work
1.4 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 44 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Reduce unused JavaScript
Potential savings of 114 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Serve images in next-gen formats
Potential savings of 476 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
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.
Avoid an excessive DOM size
957 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
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.
Minify JavaScript
Potential savings of 33 KiB
Minifying JavaScript files can reduce payload sizes and script parse time.
Properly size images
Potential savings of 447 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Total Blocking Time
360 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Initial server response time was short
Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it.
Time to Interactive
2.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
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: