First visit

CO2 1.424g

SIZE 1.88 MB

Return visit

CO2 1.292g

SIZE 1.7 MB

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

This website is hosted using renewable energy or carbon offsets.

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

Image

25

1.13 MB

0.861g

Font

5

303.85 KB

0.225g

Script

28

302.17 KB

0.224g

Stylesheet

32

117.86 KB

0.087g

Document

1

35.68 KB

0.026g

Other

4

828 B

0.001g

Third Party*

5

133.73 KB

0.099g

History

Date

CO2

Size

08.Aug.2022

1.424g

1.88 MB

24.Apr.2022

0.063g

85.05 KB

24.Apr.2022

1.490g

1.96 MB

02.Apr.2022

1.563g

2.06 MB

31.Mar.2022

0.063g

85.24 KB

30.Mar.2022

0.063g

85.24 KB

28.Mar.2022

0.063g

85.26 KB

28.Mar.2022

0.063g

85.08 KB

28.Mar.2022

0.063g

85.26 KB

28.Mar.2022

0.063g

85.26 KB

21.Mar.2022

0.063g

85.3 KB

This website has been tested 13 times**

Previous 10 test results are displayed above.


Book a 30 minute review?

Book a 30 minute review and call with Aline to help work out your next steps in lowering these emissions.


Core Web Vitals

Max Potential First Input Delay


140 ms

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

Cumulative Layout Shift


0.005

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

Largest Contentful Paint


1.6 s

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

Opportunities

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.

Avoids enormous network payloads


Total size was 1,922 KiB

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

Reduce unused CSS


Potential savings of 65 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.

Total Blocking Time


80 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time


0.5 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


1.6 s

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

Defer offscreen images


Potential savings of 139 KiB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.

First Contentful Paint


0.4 s

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

Time to Interactive


1.8 s

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

First Meaningful Paint


0.6 s

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

Speed Index


1.9 s

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

Reduce unused JavaScript


Potential savings of 29 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 368 KiB

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.

Avoids an excessive DOM size


713 elements

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

Properly size images


Potential savings of 638 KiB

Serve images that are appropriately-sized to save cellular data and improve load time.

Efficiently encode images


Potential savings of 117 KiB

Optimized images load faster and consume less cellular data.

Serve static assets with an efficient cache policy


88 resources found

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

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:

  • Amazing: less than 0.25g

  • Great: less than 0.5g

  • Good: less than 1g

  • OK: less than 1.5g

  • Bad: above 1.5g