Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize kavehome.com
CSS files are blocking First Contentful Paint by 2.5 seconds, delaying when users see content.
Inline critical above-the-fold CSS directly in the HTML head. Defer non-critical CSS using media='print' onload technique or loadCSS library. Remove 26KB of unused CSS rules, especially from the 0qg1muh_dzw7y.css file that's 95% unused.
A score of 29 falls in the "Poor" range (50-89). While it is better than poor (0-49), you should aim for 90+ to provide an optimal user experience and maximize SEO benefits.
This site is slower than approximately 35% of similar sites. The main issues affecting performance are image optimization, JavaScript execution time, and layout stability.
Addressing these issues could improve your conversion rate by 15-20% and boost your search engine rankings.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This Kavehome product page has severe performance issues with a critically low score of 29/100. The biggest problem is excessive JavaScript execution that's blocking the main thread for over 13 seconds, causing a devastating Total Blocking Time of 5+ seconds and making the page essentially unusable until it fully loads. The site is also suffering from massive amounts of unused JavaScript (1,729 KiB wasted) and oversized images that could be reduced by 1,383 KiB. Immediate priorities should be reducing JavaScript payloads, removing unused code, and implementing properly sized responsive images, which together could improve the score by 40+ points and dramatically enhance user experience.
Why It Matters:
JavaScript execution blocks the main thread for 9.5 seconds and causes 5,070ms of Total Blocking Time, severely impacting LCP and user interactions.
How to Fix:
Implement code splitting to break the large 195KB unused JavaScript chunks into smaller, on-demand bundles. Remove or defer third-party scripts like Facebook Pixel and Ada chat widget until after page load. Use tree-shaking to eliminate 1,729KB of unused JavaScript code.
Why It Matters:
Oversized images waste 1,383KB of bandwidth and contribute to the poor 13.9s LCP time.
How to Fix:
Resize product gallery images to match their display dimensions (412x515px instead of 1800x2250px). Implement responsive images with proper srcset attributes. Use next-gen formats like WebP through your CDN's auto-format feature.
Once your site is optimized, maintain that speed. Use DeployHQ for zero-downtime, automated deployments—so performance fixes and updates go live safely every time, without breaking your site.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Oversized images waste 1,383KB of bandwidth and contribute to the poor 13.9s LCP time.
JavaScript execution blocks the main thread for 9.5 seconds and causes 5,070ms of Total Blocking Time, severely impacting LCP and user interactions.
FontAwesome fonts cause 320ms render blocking and delay FCP by 300ms.
Oversized images waste 78 KiB and delay LCP by 300ms with poor responsive behavior.