First visit
CO2 0.580g
SIZE 1.54 MB
Return visit
CO2 0.116g
SIZE 315.72 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
Other
1
336 B
0.000g
Document
1
49.85 KB
0.018g
Stylesheet
5
19.33 KB
0.007g
Image
19
1.23 MB
0.464g
Script
11
156.35 KB
0.057g
Font
1
90.19 KB
0.033g
Core Web Vitals
Max Potential First Input Delay
40 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.005
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
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.
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.
Speed Index
1.8 s
Speed Index shows how quickly the contents of a page are visibly populated.
First Contentful Paint
0.6 s
First Contentful Paint marks the time at which the first text or image is painted.
Properly size images
Est savings of 324 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
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.
Avoids enormous network payloads
Total size was 1,580 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Reduce initial server response time
Root document took 1,200 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
17 resources found
A long cache lifetime can speed up repeat visits to your page.
Avoid multiple page redirects
Est savings of 200 ms
Redirects introduce additional delays before the page can be loaded.
Avoid an excessive DOM size
1,542 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Reduce unused JavaScript
Est savings of 74 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Time to Interactive
1.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
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.
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: