Latest Performance Report for:
Largest Contentful PaintLCP
Total Blocking TimeTBT
Cumulative Layout ShiftCLS
These audits are identified as the top issues impacting your performance.
Your page content is broken down into the following:
Fully Loaded Time
Total Page Size - 6.50MB
Total Page Requests - 165
More from GTmetrix
Additional tips and suggestions based on your page analysis.
Looks like you might not be using a CDN
Why should I use a CDN?
Third-party requests are affecting your performance
Learn why and potential solutions
Tips and Tricks for using GTmetrix
Shortcuts, guides and pointers for making the most out of GTmetrix
Access Analysis Options with a GTmetrix account
Block ads, capture video, change connection speeds, etc
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.
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.
These timings are milestones reported by the browser.
Time to First Byte (TTFB)
DOM Interactive Time
DOM Content Loaded Time
Fully Loaded Time
|High||Avoid enormous network payloads||Total size was 6.50MB|
Large network payloads cost users real money and are highly correlated with long load times.Learn how to improve this
|High||Properly size images||Potential savings of 3.55MB|
Serve images that are appropriately-sized to save cellular data and improve load time.Learn how to improve this
|Med-High||Avoid an excessive DOM size||5,349 elements|
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows.Learn how to improve this
|Med||Use a Content Delivery Network (CDN)||114 resources found|
CDNs can give an equally fast web experience to your users across the globe.Learn how to improve this
|Med||Serve static assets with an efficient cache policy||Potential savings of 898KB|
A long cache lifetime can speed up repeat visits to your page.Learn how to improve this
|Med||Avoid large layout shifts||5 elements found|
These DOM elements contribute most to the CLS of the page.Learn how to improve this
|Med-Low||Eliminate render-blocking resources||Potential savings of 187ms|
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Resources that may be contributing to render-blocking include:Learn how to improve this
|Med-Low||Avoid long main-thread tasks||5 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||Avoid chaining critical requests||23 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 this
Maximum critical path latency: 3.1s
|Low||Use passive listeners to improve scrolling performance||1 event listener not passive|
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance.Learn how to improve this
|Low||Ensure text remains visible during webfont load||2 fonts found|
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading.Learn how to improve this
|Low||Defer offscreen images||Potential savings of 3.82MB|
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive.Learn how to improve this
|Low||Enable text compression||Potential savings of 109KB|
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.Learn how to improve this
|Low||Serve images in next-gen formats||Potential savings of 702KB|
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption.Learn how to improve this
|Low||Avoid multiple page redirects||Potential savings of 779ms|
Redirects introduce additional delays before the page can be loaded.Learn how to improve this
|Low||Efficiently encode images||Potential savings of 11.2KB|
Optimized images load faster and consume less cellular data.Learn how to improve this
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||Reduce unused CSS||Potential savings of 74.2KB|
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity.Learn how to improve this
|Low||Reduce initial server response time||Root document took 398ms|
Keep the server response time for the main document short because all other requests depend on it.Learn how to improve this
|Low||Avoid non-composited animations||2 animated elements found|
Animations which are not composited can be janky and increase CLS.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||Main-thread busy for 1.8s|
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||Reduce the impact of third-party code||Total size was 294KB|
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading.Learn how to improve this
|N/A||User Timing marks and measures|
No user timings and/or marks found.Learn more
|Show No Impact Audits|
|None||Avoid CSS @import|
|None||Use video formats for animated content||Potential savings of 0B|
|None||Preconnect to required origins||0ms|
|None||Preload Largest Contentful Paint image||Potential savings of 0ms|
|None||Minify CSS||Potential savings of 0B|
|None||Combine images using CSS sprites|
|None||Preload key requests||0ms|
|None||Lazy load third-party resources with facades|
|None||Use HTTP/2 for all resources||Potential savings of 0ms|
A request-by-request visualization of the page load. Learn how to read a 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.
Since you do not own this report, re-testing it will not retain history data. 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.