Archived 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 - 5.09MB
Total Page Requests - 225
More from GTmetrix
Additional tips and suggestions based on your page analysis.
Looks like you're running WordPress
Have a look at our WP optimization tips
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
Test your page in multiple locations
Analyze your page globally with a free GTmetrix account
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
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
|Med-High||Avoid chaining critical requests||7 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: 8.1s
|Med-High||Avoid long main-thread tasks||20 long tasks found|
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay.Learn how to improve this
|Med||Serve static assets with an efficient cache policy||95 resources found|
A long cache lifetime can speed up repeat visits to your page.Learn how to improve this
|Med||Use a Content Delivery Network (CDN)||86 resources found|
CDNs can give an equally fast web experience to your users across the globe.Learn how to improve this
|Med-Low||Avoid large layout shifts||5 elements found|
These DOM elements contribute most to the CLS of the page.Learn how to improve this
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds.Learn how to improve this
|Low||Preload key requests||Potential savings of 290 ms|
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load.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||Preconnect to required origins||Potential savings of 110 ms|
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins.Learn how to improve this
|Low||Avoid an excessive DOM size||684 elements|
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows.Learn how to improve this
|Low||Serve images in next-gen formats||Potential savings of 237 KiB|
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||Enable text compression||Potential savings of 5 KiB|
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes.Learn how to improve this
|Low||Avoid enormous network payloads||Total size was 1,755 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 62 KiB|
Serve images that are appropriately-sized to save cellular data and improve load time.Learn how to improve this
|Low||Efficiently encode images||Potential savings of 6 KiB|
Optimized images load faster and consume less cellular data.Learn how to improve this
|Low||Remove unused CSS||Potential savings of 63 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 30 ms|
Keep the server response time for the main document short because all other requests depend on it.Learn how to improve this
|Low||Defer offscreen images||Potential savings of 35 KiB|
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||Avoid non-composited animations||46 animated elements found|
Animations which are not composited can be janky and increase CLS.Learn how to improve this
|Low||Use HTTP/2 for all resources||26 requests not served via HTTP/2|
HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push.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||13.4 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||Reduce the impact of third-party code||Third-party code blocked the main thread for 250 ms|
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|
|None||Avoid multiple page redirects|
|None||Eliminate render-blocking resources|
|None||Ensure text remains visible during webfont load|
|None||Combine images using CSS sprites|
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
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.