First visit
CO2 0.726g
SIZE 888.5 KB
Return visit
CO2 0.194g
SIZE 236.86 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
Image
16
333.39 KB
0.273g
Script
7
318.43 KB
0.260g
Font
4
143.34 KB
0.117g
Stylesheet
2
47.46 KB
0.039g
Other
5
26.99 KB
0.022g
Document
1
18.89 KB
0.015g
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.002
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
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.
Serve images in next-gen formats
Potential savings of 99 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Avoids enormous network payloads
Total size was 888 KiB
Large network payloads cost users real money and are highly correlated with long load times.
First Contentful Paint
0.8 s
First Contentful Paint marks the time at which the first text or image is painted.
Reduce unused CSS
Potential savings of 42 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Eliminate render-blocking resources
Potential savings of 540 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 JavaScript
Potential savings of 159 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Avoids an excessive DOM size
591 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Speed Index
1.0 s
Speed Index shows how quickly the contents of a page are visibly populated.
Time to Interactive
1.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive.
First Meaningful Paint
1.1 s
First Meaningful Paint measures when the primary content of a page is visible.
Serve static assets with an efficient cache policy
20 resources found
A long cache lifetime can speed up repeat visits to your page.
Initial server response time was short
Root document took 310 ms
Keep the server response time for the main document short because all other requests depend on it.
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.
Enable text compression
Potential savings of 140 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
Minify CSS
Potential savings of 11 KiB
Minifying CSS files can reduce network payload sizes.
Switch to green hosting
One of the easiest things to do that instantly reduces your impact.
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: