First visit
CO2 0.537g
SIZE 1.69 MB
Return visit
CO2 0.144g
SIZE 464.59 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
23.62 KB
0.007g
Stylesheet
2
154.02 KB
0.048g
Script
9
389.89 KB
0.121g
Image
37
1.08 MB
0.343g
Font
3
57.19 KB
0.018g
Preflight
1
732 B
0.000g
XHR
2
619 B
0.000g
Core Web Vitals
Max Potential First Input Delay
110 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.134
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
2.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Minimizes main-thread work
0.9 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,732 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Time to Interactive
1.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
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.
Serve images in next-gen formats
Potential savings of 526 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Properly size images
Potential savings of 400 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Avoid an excessive DOM size
1,325 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 210 ms
Keep the server response time for the main document short because all other requests depend on it.
Eliminate render-blocking resources
Potential savings of 450 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
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.
Speed Index
1.4 s
Speed Index shows how quickly the contents of a page are visibly populated.
Server Backend Latencies
430 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.
Total Blocking Time
30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Meaningful Paint
1.1 s
First Meaningful Paint measures when the primary content of a page is visible.
First Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted.
JavaScript execution time
0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
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.
Serve static assets with an efficient cache policy
34 resources found
A long cache lifetime can speed up repeat visits to your page.
Defer offscreen images
Potential savings of 116 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.
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: