CO2 0.023g

SIZE 30.56 KB

Total

Overall this web page is rated as amazing when it comes to its carbon footprint

Breakdown

Type

Requests

Size

CO2

Stylesheet

2

11.87 KB

0.009g

Image

2

10.6 KB

0.008g

Document

1

5.03 KB

0.004g

Script

3

3.06 KB

0.002g

Third Party*

1

1.17 KB

0.001g

Core Web Vitals

Max Potential First Input Delay


20 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task.

Cumulative Layout Shift


0

Cumulative Layout Shift measures the movement of visible elements within the viewport.

Largest Contentful Paint


0.5 s

Largest Contentful Paint marks the time at which the largest text or image is painted.

Opportunities

Avoids an excessive DOM size


126 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows

First Meaningful Paint


0.4 s

First Meaningful Paint measures when the primary content of a page is visible.

First Contentful Paint


0.4 s

First Contentful Paint marks the time at which the first text or image is painted.

First CPU Idle


0.4 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input.

Speed Index


0.4 s

Speed Index shows how quickly the contents of a page are visibly populated.

Estimated Input Latency


10 ms

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy.

Initial server response time was short


Root document took 70 ms

Keep the server response time for the main document short because all other requests depend on it.

JavaScript execution time


0.0 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.

Minimizes main-thread work


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


0.4 s

Time to interactive is the amount of time it takes for the page to become fully interactive.

Uses efficient cache policy on static assets


5 resources found

A long cache lifetime can speed up repeat visits to your page.

Eliminate render-blocking resources


Potential savings of 110 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.

Avoids enormous network payloads


Total size was 31 KiB

Large network payloads cost users real money and are highly correlated with long load times.

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:

  • Amazing: less than 0.25g

  • Great: less than 0.5g

  • Good: less than 1g

  • OK: less than 1.5g

  • Bad: above 1.5g