
Latest Performance Report for:
http://www.stashbird.com/
GTmetrix Grade
Performance
90%Structure
91%Web Vitals
Largest Contentful PaintLCP
1.2sTotal Blocking TimeTBT
113msCumulative Layout ShiftCLS
0.08Speed Visualization
0.2s

0.3s

0.5s

0.7s

0.8s

1s

1.2s

1.3s

1.5s

1.6s

Top Issues
These audits are identified as the top issues impacting your performance.
Impact | Audit | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Med-Low | Avoid an excessive DOM size | 1,228 elements | |||||||||||||
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to improve this
|
|||||||||||||||
Med-Low | Avoid CSS @import | 1 resource found. | |||||||||||||
Using CSS @import in an external stylesheet can add additional delays during the loading of a web page. Learn how to improve this
|
|||||||||||||||
Low | Use passive listeners to improve scrolling performance | ||||||||||||||
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn how to improve this
|
|||||||||||||||
Low | Avoid large layout shifts | 5 elements found | |||||||||||||
These DOM elements contribute most to the CLS of the page. Learn how to improve this
|
|||||||||||||||
Low | Avoid enormous network payloads | Total size was 357 KiB | |||||||||||||
Large network payloads cost users real money and are highly correlated with long load times. Learn how to improve this |
Focus on these audits first
These audits likely have the largest impact on your page performance.
Structure audits do not directly affect your Performance Score, but improving the audits seen here can help as a starting point for overall performance gains.
See all Structure auditsPage Details
Your page content is broken down into the following:
1.6s
Fully Loaded Time
Total Page Size - 357KB
Total Page Requests - 24
More from GTmetrix
Additional tips and suggestions based on your page analysis.
Understand and assess Waterfall Charts
Learn to identify and point out potential issues in your page load
Tips and Tricks for using GTmetrix
Shortcuts, guides and pointers for making the most out of GTmetrix
Understand your GTmetrix Report
Learn everything you need to know about GTmetrix Reports
Test your page in multiple locations
Analyze your page globally with a free GTmetrix account
Performance Metrics
The following metrics are generated using Lighthouse Performance data.
First Contentful Paint
How quickly content like text or images are painted onto your page.
A good user experience is 0.9s or less. Learn more.
Time to Interactive
How long it takes for your page to become fully interactive.
A good user experience is 2.5s or less. Learn more.
Speed Index
How quickly the contents of your page are visibly populated.
A good user experience is 1.3s or less. Learn more.
Total Blocking Time
How much time is blocked by scripts during your page loading process.
A good user experience is 150ms or less. Learn more.
Largest Contentful Paint
How long it takes for the largest element of content (e.g. a hero image) to be painted on your page.
A good user experience is 1.2s or less. Learn more.
Cumulative Layout Shift
How much your page's layout shifts as it loads.
A good user experience is a score of 0.1 or less. Learn more.
Browser Timings
These timings are milestones reported by the browser.
Redirect Duration
Connection Duration
Backend Duration
Time to First Byte (TTFB)
DOM Interactive Time
DOM Content Loaded Time
First Paint
Onload Time
Fully Loaded Time
Impact | Audit | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Med-Low | Avoid an excessive DOM size | 1,228 elements | |||||||||||||||||||||||||||||
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to improve this
|
|||||||||||||||||||||||||||||||
Med-Low | Avoid CSS @import | 1 resource found. | |||||||||||||||||||||||||||||
Using CSS @import in an external stylesheet can add additional delays during the loading of a web page. Learn how to improve this
|
|||||||||||||||||||||||||||||||
Low | Use passive listeners to improve scrolling performance | ||||||||||||||||||||||||||||||
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn how to improve this
|
|||||||||||||||||||||||||||||||
Low | Avoid large layout shifts | 5 elements found | |||||||||||||||||||||||||||||
These DOM elements contribute most to the CLS of the page. Learn how to improve this
|
|||||||||||||||||||||||||||||||
Low | Avoid enormous network payloads | Total size was 357 KiB | |||||||||||||||||||||||||||||
Large network payloads cost users real money and are highly correlated with long load times. Learn how to improve this |
|||||||||||||||||||||||||||||||
Low | Properly size images | Potential savings of 45 KiB | |||||||||||||||||||||||||||||
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to improve this
|
|||||||||||||||||||||||||||||||
Low | Avoid multiple page redirects | Potential savings of 210 ms | |||||||||||||||||||||||||||||
Redirects introduce additional delays before the page can be loaded. Learn how to improve this
|
|||||||||||||||||||||||||||||||
Low | Avoid long main-thread tasks | 2 long tasks found | |||||||||||||||||||||||||||||
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to improve this
|
|||||||||||||||||||||||||||||||
Low | Reduce JavaScript execution time | 0.2 s | |||||||||||||||||||||||||||||
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to improve this
|
|||||||||||||||||||||||||||||||
Low | Remove unused CSS | Potential savings of 31 KiB | |||||||||||||||||||||||||||||
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn how to improve this
|
|||||||||||||||||||||||||||||||
Low | Reduce initial server response time | Root document took 190 ms | |||||||||||||||||||||||||||||
Keep the server response time for the main document short because all other requests depend on it. Learn how to improve this
|
|||||||||||||||||||||||||||||||
Low | Avoid serving legacy JavaScript to modern browsers | Potential savings of 0 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. Learn how to improve this
|
|||||||||||||||||||||||||||||||
Low | Avoid chaining critical requests | 3 chains found | |||||||||||||||||||||||||||||
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn how to improve thisMaximum critical path latency: 1.1s Initial Navigation
|
|||||||||||||||||||||||||||||||
Low | Remove unused JavaScript | Potential savings of 23 KiB | |||||||||||||||||||||||||||||
Remove unused JavaScript to reduce bytes consumed by network activity. Learn how to improve this
|
|||||||||||||||||||||||||||||||
N/A | Largest Contentful Paint element | 1 element found | |||||||||||||||||||||||||||||
This is the largest contentful element painted within the viewport.
|
|||||||||||||||||||||||||||||||
N/A | Minimize main-thread work | 0.5 s | |||||||||||||||||||||||||||||
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to improve this
|
|||||||||||||||||||||||||||||||
N/A | Replace large JavaScript libraries with smaller alternatives | 0 large libraries found | |||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
N/A | User Timing marks and measures | ||||||||||||||||||||||||||||||
No user timings and/or marks found. Learn more |
|||||||||||||||||||||||||||||||
N/A | Reduce the impact of third-party code | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
Show No Impact Audits | |||||||||||||||||||||||||||||||
None | Serve images in next-gen formats | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Enable text compression | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Use a Content Delivery Network (CDN) | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Use video formats for animated content | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Serve static assets with an efficient cache policy | 0 resources found | |||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Efficiently encode images | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Eliminate render-blocking resources | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Ensure text remains visible during webfont load | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Preconnect to required origins | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Avoid document.write() | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Defer offscreen images | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Minify CSS | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Avoid non-composited animations | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Enable Keep-Alive | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Minify JavaScript | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Remove duplicate modules in JavaScript bundles | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Combine images using CSS sprites | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Preload key requests | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
|||||||||||||||||||||||||||||||
None | Use HTTP/2 for all resources | ||||||||||||||||||||||||||||||
Nothing to do here, good job! Learn how to improve this |
What do these audits mean?
These audits are best practices established by Google to help build websites for optimal front-end performance.
Each audit is assessed based on your adherence to them and ordered by the most likely impact to your page's performance.
Note that Structure audits do not directly affect your Performance score, however addressing them can serve as good starting point to improve page load times overall. Additionally, some of the audits are correlated and thus, fixing one audit may affect others.
Learn about all the auditsNeed optimization help?
We've written various guides and articles to help you improve your page performance:
Want an expert to help?
We can recommend partners to further assist you with optimizing your site. Contact us and we'll point you in the right direction.
Waterfall Chart
A request-by-request visualization of the page load. Learn how to read a waterfall chart.

Registered users have access to Resource Usage Graphs!
See how your page utilizes system resources and add more insight to your Waterfall Chart.
A higher resolution (at least 600px wide) is required to display the Waterfall chart
Tip: rotating your device into landscape mode may give you the necessary resolution to view the waterfall.
Page Load Video

See your page load with videos
Logged in users can record a video of this page loading and pinpoint exactly where bottlenecks and stoppages occur.
Slow playback up to 4x to visualize loading behaviour
Jump to major milestones like First Paint and Onload
Download and embed videos
This page does not yet have any historical data

Historical graphs require more than one test to be generated.
Once you re-test this page, the history graphs will be displayed and will give you access to the older, archived reports.
Report data generated on Guest plans will be deleted after 1 month.
You can also monitor this page to better track and visualize page performance over time.
- Schedule a test to run daily, weekly or monthly to ensure optimal performance.
- Visualize performance with graphs of Page load time, Page size & Request counts and PageSpeed and YSlow scores.
- Annotate areas of interest on your graph and give your data context.
Monitoring only available to registered GTmetrix users.
A higher resolution (at least 840px wide) is required to display the Report History graphs
Tip: rotating your device into landscape mode may give you the necessary resolution to view the graphs.