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 - 89.0KB
Total Page Requests - 10
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
Tips and Tricks for using GTmetrix
Shortcuts, guides and pointers for making the most out of GTmetrix
Understand and assess Waterfall Charts
Learn to identify and point out potential issues in your page load
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
|Low||Use a Content Delivery Network (CDN)||4 resources found|
CDNs can give an equally fast web experience to your users across the globe.Learn how to improve this
|Low||Avoid enormous network payloads LCP||Total size was 89.0KB|
Large network payloads cost users real money and are highly correlated with long load times.Learn how to improve this
|Low||Avoid multiple page redirects FCP LCP||Potential savings of 27ms|
Redirects introduce additional delays before the page can be loaded.Learn how to improve this
|Low||Ensure text remains visible during webfont load FCP LCP||2 fonts found|
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading.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 FCP LCP||Root document took 97ms|
Keep the server response time for the main document short because all other requests depend on it.Learn how to improve this
|Low||Avoid chaining critical requests FCP LCP||4 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: 272ms
|N/A||Avoid an excessive DOM size TBT||36 elements|
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows.Learn how to improve this
|N/A||Largest Contentful Paint element LCP||1 element found|
This is the largest contentful element painted within the viewport.
|N/A||Avoid large layout shifts CLS||1 element found|
These DOM elements contribute most to the CLS of the page.Learn how to improve this
|N/A||Minimize main-thread work TBT||Main-thread busy for 142ms|
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 TBT|
|Show No Impact Audits|
|None||Avoid CSS @import FCP LCP|
|None||Enable text compression FCP LCP|
|None||Use a <meta name="viewport"> tag with width or initial-scale TBT|
|None||Use video formats for animated content LCP|
|None||Use passive listeners to improve scrolling performance|
|None||Properly size images|
|None||Don't lazy load Largest Contentful Paint image||LCP was lazy loaded|
|None||Serve static assets with an efficient cache policy||0 resources found|
|None||Efficiently encode images|
|None||Eliminate render-blocking resources FCP LCP|
|None||Preconnect to required origins FCP LCP|
|None||Avoid long main-thread tasks TBT|
|None||Preload Largest Contentful Paint image LCP|
|None||Reduce unused CSS FCP LCP|
|None||Serve images in next-gen formats|
|None||Defer offscreen images|
|None||Minify CSS FCP LCP|
|None||Avoid non-composited animations CLS|
|None||Enable Keep-Alive FCP LCP|
|None||Avoid unload event listeners|
|None||Combine images using CSS sprites FCP LCP|
|None||Preload key requests FCP LCP|
|None||Lazy load third-party resources with facades TBT|
|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 series of graphs to keep track of your page performance over time. Learn how to use the History Graphs.
Page sizes and request counts
This history graph has more reports available
Get more data points in your history when you log in.
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.