First visit

CO2 0.152g

SIZE 490.14 KB

Return visit

CO2 0.029g

SIZE 94.38 KB

Overall this web page has been graded A when it comes to its carbon footprint

This website is hosted using renewable energy or carbon offsets.

Find out more about grades

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

6.77 KB

0.002g

Font

2

42.37 KB

0.013g

Script

4

159.45 KB

0.049g

Stylesheet

2

15.33 KB

0.005g

Image

3

257.5 KB

0.080g

XHR

2

7.93 KB

0.002g

Fetch

1

804 B

0.000g

History

Date

CO2

Size

27.May.2025

0.152g

490.14 KB

20.Dec.2024

0.147g

472.17 KB

20.Dec.2024

0.161g

518.71 KB

20.Dec.2024

0.006g

18.99 KB

This website has been tested 4 times**

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.

Cumulative Layout Shift


0.004

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

Largest Contentful Paint


0.7 s

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

Opportunities

Speed Index


1.0 s

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

Avoids an excessive DOM size


153 elements

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

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.

Avoids enormous network payloads


Total size was 490 KiB

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

First Contentful Paint


0.6 s

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

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 JavaScript


Est savings of 51 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.

Serve static assets with an efficient cache policy


9 resources found

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

Initial server response time was short


Root document took 100 ms

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

Server Backend Latencies


110 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.

Minimizes main-thread work


0.3 s

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

Eliminate render-blocking resources


Est savings of 340 ms

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

Time to Interactive


0.7 s

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

Notes

* These are assets not hosted on the same domain e.g. tracking scripts, iframe embeds, or files hosted on a CDN.

** This was only counted from 11.Apr.2021.

These measurements are for each new visitor, for returning visitors the footprint would be lower based on caching mechanisms.

Our brackets for the ratings:

  • A+: less than 0.095g

  • A: less than 0.185g

  • B: less than 0.34g

  • C: less than 0.49g

  • D: less than 0.65g

  • E: less than 0.85g

  • F: above 0.85