First visit
CO2 1.023g
SIZE 1.35 MB
Return visit
CO2 0.445g
SIZE 600.86 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
Script
18
578.81 KB
0.429g
Image
12
484.61 KB
0.359g
Document
5
136.19 KB
0.101g
Font
5
110.41 KB
0.082g
Stylesheet
5
43.35 KB
0.032g
Other
10
26.9 KB
0.020g
History
Date
CO2
Size
22.Sep.2022
1.023g
1.35 MB
22.Sep.2022
0.967g
1.27 MB
22.Sep.2022
0.967g
1.27 MB
This website has been tested 3 times**
Core Web Vitals
Max Potential First Input Delay
30 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
Cumulative Layout Shift
0.002
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
1.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
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.
Eliminate render-blocking resources
Potential savings of 750 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Avoids an excessive DOM size
577 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Efficiently encode images
Potential savings of 199 KiB
Optimized images load faster and consume less cellular data.
Properly size images
Potential savings of 83 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
First Meaningful Paint
1.0 s
First Meaningful Paint measures when the primary content of a page is visible.
Initial server response time was short
Root document took 460 ms
Keep the server response time for the main document short because all other requests depend on it.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 20 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers.
Avoids enormous network payloads
Total size was 1,380 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Serve images in next-gen formats
Potential savings of 289 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Minimizes main-thread work
0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Speed Index
1.0 s
Speed Index shows how quickly the contents of a page are visibly populated.
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 370 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Time to Interactive
1.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
Serve static assets with an efficient cache policy
10 resources found
A long cache lifetime can speed up repeat visits to your page.
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: