Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize stg.homestead.staging.kinsta.cloud
Large unoptimized images waste 6.7MB and delay LCP by 1.4 seconds, making your site painfully slow.
Convert feature-text-bg.png (4.2MB) and property-map.jpg (3MB) to WebP format using ShortPixel or Imagify. Resize property-map.jpg from 2720x1768 to its displayed 1628x1058 dimensions. Add explicit width/height attributes to prevent layout shifts.
A score of 39 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 WordPress site has severe performance issues with a score of only 39/100. The biggest problem is massive unoptimized images that are wasting over 6.7 MB of data and causing extremely slow loading times - your Largest Contentful Paint takes 9.7 seconds, which is far beyond acceptable limits. The main culprits are a 4.2 MB background image and a 3 MB property map that aren't using modern formats like WebP and are much larger than needed for display. Converting these images to WebP/AVIF format and properly sizing them could save over 6 MB and improve your LCP by 1.35 seconds, potentially boosting your performance score by 30+ points.
Why It Matters:
Unused JavaScript wastes 423KB and blocks the main thread for 1.7 seconds, preventing user interactions.
How to Fix:
Use Asset CleanUp Pro to remove unused portions of app.js (60% unused). Defer Google Analytics and Maps API loading until after page interactive. Minify the remaining slider.js file to save 5KB.
Why It Matters:
CSS files block initial page rendering for 1.8 seconds, delaying when users see content.
How to Fix:
Inline critical CSS for above-the-fold content directly in WordPress theme header.php. Use WP Rocket to defer loading of Google Fonts and non-critical stylesheets. Remove unused CSS rules (40KB savings identified).
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 WordPress Speed Tests
CSS files block initial page rendering for 1.8 seconds, delaying when users see content.
Unused JavaScript wastes 423KB and blocks the main thread for 1.7 seconds, preventing user interactions.
Unused CSS (221KB) and render-blocking resources delay first paint and increase LCP by 750ms.
Layout shifts (CLS 0.405) are caused by unsized images, creating jarring user experience as content jumps during load.