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 - 281KB
Total Page Requests - 36
More from GTmetrix
Additional tips and suggestions based on your page analysis.
Need help with optimization?
Find a developer with our partner Fiverr to optimize your performance
Looks like you're running WordPress
Have a look at our WP optimization tips
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
|Low||Eliminate render-blocking resources||Potential savings of 22ms|
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
|Low||Avoid an excessive DOM size||425 elements|
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows.Learn how to improve this
|Low||Avoid enormous network payloads||Total size was 281KB|
Large network payloads cost users real money and are highly correlated with long load times.Learn how to improve this
|Low||Serve static assets with an efficient cache policy||Potential savings of 1.64KB|
A long cache lifetime can speed up repeat visits to your page.Learn how to improve this
|Low||Ensure text remains visible during webfont load||1 font found|
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading.Learn how to improve this
|Low||Avoid long main-thread tasks||1 long task found|
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay.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 37.4KB|
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 27ms|
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||4 animated elements found|
Animations which are not composited can be janky and increase CLS.Learn how to improve this
|Low||Avoid chaining critical requests||17 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: 495ms
|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 377ms|
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 71.1KB|
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||Enable text compression|
|None||Use a Content Delivery Network (CDN)|
|None||Use video formats for animated content|
|None||Use passive listeners to improve scrolling performance|
|None||Properly size images|
|None||Avoid multiple page redirects|
|None||Efficiently encode images|
|None||Preconnect to required origins|
|None||Preload Largest Contentful Paint image|
|None||Serve images in next-gen formats|
|None||Defer offscreen images|
|None||Avoid large layout shifts|
|None||Combine images using CSS sprites|
|None||Preload key requests|
|None||Lazy load third-party resources with facades|
|None||Use HTTP/2 for all resources|
A request-by-request visualization of the page load. Learn how to read a waterfall chart.
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.