First visit
CO2 6.539g
SIZE 20.58 MB
Return visit
CO2 0.030g
SIZE 96.66 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
Document
1
24.44 KB
0.008g
Stylesheet
1
53.12 KB
0.016g
Image
198
10.87 MB
3.454g
Script
11
1.02 MB
0.323g
Font
6
178.14 KB
0.055g
Other
1
414 B
0.000g
Preflight
3
1.14 KB
0.000g
XHR
3
2.43 KB
0.001g
Fetch
11
1.49 MB
0.473g
Media
20
6.95 MB
2.208g
History
Date
CO2
Size
19.Apr.2024
6.539g
20.58 MB
11.Jan.2024
7.330g
23.07 MB
This website has been tested 2 times**
Core Web Vitals
Max Potential First Input Delay
220 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
1.006
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
3.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
First Contentful Paint
0.8 s
First Contentful Paint marks the time at which the first text or image is painted.
Properly size images
Potential savings of 1,618 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Avoid enormous network payloads
Total size was 21,073 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Serve static assets with an efficient cache policy
6 resources found
A long cache lifetime can speed up repeat visits to your page.
Initial server response time was short
Root document took 470 ms
Keep the server response time for the main document short because all other requests depend on it.
Speed Index
3.1 s
Speed Index shows how quickly the contents of a page are visibly populated.
Reduce JavaScript execution time
2.4 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
Potential savings of 30 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
First Meaningful Paint
0.8 s
First Meaningful Paint measures when the primary content of a page is visible.
Minimize main-thread work
4.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Time to Interactive
4.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Serve images in next-gen formats
Potential savings of 872 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
20 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.
Avoid an excessive DOM size
1,775 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Efficiently encode images
Potential savings of 20 KiB
Optimized images load faster and consume less cellular data.
Reduce unused CSS
Potential savings of 35 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Enable text compression
Potential savings of 124 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
Total Blocking Time
710 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce unused JavaScript
Potential savings of 460 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Defer offscreen images
Potential savings of 259 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.
Server Backend Latencies
610 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.
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: