First visit
CO2 0.654g
SIZE 1.74 MB
Return visit
CO2 0.189g
SIZE 514.64 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
50.13 KB
0.018g
Stylesheet
4
19.16 KB
0.007g
Image
19
1.24 MB
0.465g
Script
11
155.92 KB
0.057g
Font
3
289.43 KB
0.106g
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.002
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
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.
First Contentful Paint
0.4 s
First Contentful Paint marks the time at which the first text or image is painted.
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
1.0 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 an excessive DOM size
1,548 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Avoids enormous network payloads
Total size was 1,783 KiB
Large network payloads cost users real money and are highly correlated with long load times.
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.
Reduce unused JavaScript
Potential savings of 74 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Reduce initial server response time
Root document took 1,350 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
18 resources found
A long cache lifetime can speed up repeat visits to your page.
Speed Index
1.6 s
Speed Index shows how quickly the contents of a page are visibly populated.
Properly size images
Potential savings of 306 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: