First visit
CO2 0.803g
SIZE 2.53 MB
Return visit
CO2 0.249g
SIZE 801.06 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
22.88 KB
0.007g
Stylesheet
3
155.49 KB
0.048g
Script
9
389.54 KB
0.121g
Image
26
1.9 MB
0.605g
Font
4
68.76 KB
0.021g
Preflight
1
734 B
0.000g
XHR
2
1.46 KB
0.000g
Core Web Vitals
Max Potential First Input Delay
60 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.031
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
2.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Defer offscreen images
Potential savings of 298 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.
Efficiently encode images
Potential savings of 347 KiB
Optimized images load faster and consume less cellular data.
Speed Index
1.4 s
Speed Index shows how quickly the contents of a page are visibly populated.
Properly size images
Potential savings of 965 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 220 ms
Keep the server response time for the main document short because all other requests depend on it.
First Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted.
Minimizes main-thread work
0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Server Backend Latencies
390 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.
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.
Reduce unused CSS
Potential savings of 148 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Eliminate render-blocking resources
Potential savings of 490 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Serve static assets with an efficient cache policy
22 resources found
A long cache lifetime can speed up repeat visits to your page.
Reduce unused JavaScript
Potential savings of 180 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
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.
Avoids an excessive DOM size
774 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Time to Interactive
1.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Avoids enormous network payloads
Total size was 2,588 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 1,208 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
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: