First visit

CO2 9.218g

SIZE 12.15 MB

Return visit

CO2 0.298g

SIZE 402.45 KB

Overall this web page is rated as bad 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

Media

2

7.23 MB

5.485g

Image

37

3.14 MB

2.383g

Script

87

1.38 MB

1.047g

Stylesheet

17

178.01 KB

0.132g

Font

5

163.48 KB

0.121g

Other

29

34.22 KB

0.025g

Document

4

33.65 KB

0.025g

Third Party*

177

12.11 MB

9.190g


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


100 ms

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

Cumulative Layout Shift


0.002

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

Largest Contentful Paint


4.0 s

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

Opportunities

Total Blocking Time


40 ms

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

Minify JavaScript


Potential savings of 70 KiB

Minifying JavaScript files can reduce payload sizes and script parse time.

Avoid enormous network payloads


Total size was 12,439 KiB

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

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.

Defer offscreen images


Potential savings of 153 KiB

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

First Contentful Paint


1.1 s

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

Reduce unused JavaScript


Potential savings of 583 KiB

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

Speed Index


1.6 s

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

Initial server response time was short


Root document took 120 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 490 ms

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

Minify CSS


Potential savings of 19 KiB

Minifying CSS files can reduce network payload sizes.

Enable text compression


Potential savings of 61 KiB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.

Serve static assets with an efficient cache policy


44 resources found

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

Serve images in next-gen formats


Potential savings of 250 KiB

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

First Meaningful Paint


1.1 s

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

Reduce unused CSS


Potential savings of 137 KiB

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

Properly size images


Potential savings of 88 KiB

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

Time to Interactive


3.1 s

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

Avoids an excessive DOM size


593 elements

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

Minimizes main-thread work


1.8 s

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

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