First visit
CO2 5.360g
SIZE 14.27 MB
Return visit
CO2 0.009g
SIZE 24.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
24.6 KB
0.009g
Stylesheet
4
50.37 KB
0.018g
Script
7
160.42 KB
0.059g
Image
27
7.22 MB
2.712g
Font
3
68.27 KB
0.025g
Media
8
6.75 MB
2.537g
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
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
5.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Reduce unused JavaScript
Est savings of 87 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Avoid an excessive DOM size
856 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Initial server response time was short
Root document took 10 ms
Keep the server response time for the main document short because all other requests depend on it.
First Contentful Paint
0.4 s
First Contentful Paint marks the time at which the first text or image is painted.
Minimizes main-thread work
0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Speed Index
2.3 s
Speed Index shows how quickly the contents of a page are visibly populated.
Avoid enormous network payloads
Total size was 14,610 KiB
Large network payloads cost users real money and are highly correlated with long load times.
JavaScript execution time
0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Time to Interactive
5.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
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.
Avoid serving legacy JavaScript to modern browsers
Est savings of 11 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
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.
Properly size images
Est savings of 5,163 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
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.
These measurements are for each new visitor, for returning visitors the footprint would be lower based on caching mechanisms.
Our brackets for the ratings: