First visit
CO2 1.459g
SIZE 3.88 MB
Return visit
CO2 1.215g
SIZE 3.23 MB
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
4
127.28 KB
0.047g
Stylesheet
44
1.47 MB
0.552g
Font
10
274.23 KB
0.101g
Script
80
1.86 MB
0.699g
Image
10
154.12 KB
0.057g
XHR
5
11.25 KB
0.004g
Preflight
1
673 B
0.000g
Core Web Vitals
Max Potential First Input Delay
70 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task.
Learn more about the Maximum Potential First Input Delay metric
Cumulative Layout Shift
0.031
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
5.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Serve static assets with an efficient cache policy
79 resources found
A long cache lifetime can speed up repeat visits to your page.
Minify JavaScript
Potential savings of 90 KiB
Minifying JavaScript files can reduce payload sizes and script parse time.
First Meaningful Paint
3.1 s
First Meaningful Paint measures when the primary content of a page is visible.
Total Blocking Time
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Preload Largest Contentful Paint image
Potential savings of 990 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP.
JavaScript execution time
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 2,232 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
Properly size images
Potential savings of 104 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
First Contentful Paint
3.1 s
First Contentful Paint marks the time at which the first text or image is painted.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 89 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers.
Minimizes main-thread work
1.4 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 97 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.
Network Round Trip Times
120 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 CSS
Potential savings of 1,297 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Initial server response time was short
Root document took 230 ms
Keep the server response time for the main document short because all other requests depend on it.
Minify CSS
Potential savings of 73 KiB
Minifying CSS files can reduce network payload sizes.
Speed Index
3.8 s
Speed Index shows how quickly the contents of a page are visibly populated.
Server Backend Latencies
910 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.
Time to Interactive
3.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Avoids an excessive DOM size
509 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Reduce unused JavaScript
Potential savings of 911 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Avoid enormous network payloads
Total size was 3,969 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Eliminate render-blocking resources
Potential savings of 1,730 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
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: