First visit
CO2 2.021g
SIZE 5.38 MB
Return visit
CO2 1.262g
SIZE 3.36 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
2
209.63 KB
0.077g
Stylesheet
47
1.55 MB
0.580g
Font
12
347.55 KB
0.128g
Script
78
2.61 MB
0.982g
Image
15
642.9 KB
0.236g
Other
2
797 B
0.000g
XHR
7
48.47 KB
0.018g
Preflight
2
1.09 KB
0.000g
Core Web Vitals
Max Potential First Input Delay
190 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.011
Cumulative Layout Shift measures the movement of visible elements within the viewport.
Largest Contentful Paint
3.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted.
Opportunities
Speed Index
6.4 s
Speed Index shows how quickly the contents of a page are visibly populated.
First Meaningful Paint
3.3 s
First Meaningful Paint measures when the primary content of a page is visible.
First Contentful Paint
3.2 s
First Contentful Paint marks the time at which the first text or image is painted.
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.
Minimize main-thread work
3.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.
Network Round Trip Times
110 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.
Enable text compression
Potential savings of 2,358 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.
Avoid an excessive DOM size
830 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows
Server Backend Latencies
250 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.
Minify JavaScript
Potential savings of 90 KiB
Minifying JavaScript files can reduce payload sizes and script parse time.
Preload Largest Contentful Paint image
Potential savings of 490 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP.
Reduce JavaScript execution time
1.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this.
Reduce unused JavaScript
Potential savings of 1,510 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity.
Reduce initial server response time
Root document took 3,280 ms
Keep the server response time for the main document short because all other requests depend on it.
Properly size images
Potential savings of 185 KiB
Serve images that are appropriately-sized to save cellular data and improve load time.
Time to Interactive
7.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive.
Eliminate render-blocking resources
Potential savings of 1,750 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.
Avoid enormous network payloads
Total size was 5,509 KiB
Large network payloads cost users real money and are highly correlated with long load times.
Total Blocking Time
290 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Serve static assets with an efficient cache policy
82 resources found
A long cache lifetime can speed up repeat visits to your page.
Reduce unused CSS
Potential savings of 1,373 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.
Minify CSS
Potential savings of 73 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: