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 - 360KB
Total Page Requests - 27
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
Understand your GTmetrix Report
Learn everything you need to know about GTmetrix Reports
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
|Med||Eliminate render-blocking resources||Potential savings of 470 ms|
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles.Learn how to improve this
|Med-Low||Use a Content Delivery Network (CDN)||19 resources found|
CDNs can give an equally fast web experience to your users across the globe.Learn how to improve this
|Med-Low||Preload key requests||Potential savings of 370 ms|
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load.Learn how to improve this
|Low||Remove unused CSS||Potential savings of 69 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||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: 2.2s
|Low||Avoid an excessive DOM size||241 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 360 KiB|
Large network payloads cost users real money and are highly correlated with long load times.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 initial server response time||Root document took 310 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 large layout shifts||5 elements found|
These DOM elements contribute most to the CLS of the page.Learn how to improve this
|Low||Avoid non-composited animations||1 animated element 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||1.1 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||User Timing marks and measures|
No user timings and/or marks found.Learn more
|N/A||Reduce the impact of third-party code|
|Show No Impact Audits|
|None||Avoid CSS @import|
|None||Serve images in next-gen formats|
|None||Enable text compression|
|None||Use video formats for animated content|
|None||Use passive listeners to improve scrolling performance|
|None||Properly size images|
|None||Serve static assets with an efficient cache policy||0 resources found|
|None||Avoid multiple page redirects|
|None||Efficiently encode images|
|None||Ensure text remains visible during webfont load|
|None||Preconnect to required origins|
|None||Defer offscreen images|
|None||Combine images using CSS sprites|
|None||Use HTTP/2 for all resources|
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.