Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize hermanwells.com
Layout shifts score 0.162 CLS due to unsized images and web font loading, causing content to jump and poor user experience.
Add explicit width='19' height='17' attributes to all star rating images. Implement font-display: swap for custom fonts and preload critical font files. Use CSS aspect-ratio or min-height to reserve space for dynamically loaded content.
A score of 63 falls in the "Needs Improvement" 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 website has poor performance with a score of 63/100, primarily due to excessive JavaScript blocking the main thread for nearly 7 seconds. The biggest culprit is JavaScript execution time (4.9 seconds) combined with a massive 1,684 KiB of unused JavaScript code, particularly from Google reCAPTCHA which appears to be loaded multiple times. Layout shifts caused by unsized images and web fonts are also hurting the user experience, resulting in a Time to Interactive of 33.6 seconds. Removing duplicate scripts, optimizing JavaScript delivery, and properly sizing images could dramatically improve performance and reduce the blocking time by over 1.8 seconds.
Why It Matters:
JavaScript is blocking the main thread for 6.9 seconds with 1,820ms Total Blocking Time, severely impacting user interactions and Core Web Vitals.
How to Fix:
Defer the Google reCAPTCHA script until user interaction is detected. Remove duplicate reCAPTCHA loads (appears 3 times). Use async loading for CallTrack and Facebook Pixel scripts. Consider lazy-loading non-critical third-party scripts after page interactive.
Why It Matters:
Unused CSS (37KB) and JavaScript (1.7MB) are bloating page size and slowing down loading without providing value.
How to Fix:
Use PurgeCSS to remove 88% of unused CSS from the combined stylesheet. Audit and remove unused JavaScript from third-party services. Split critical CSS and defer non-critical styles using media='print' onload technique.
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
Your LCP element has 2.8 seconds of render delay, significantly impacting user experience.
47% of your main JavaScript bundle (28KB) is unused, wasting 150ms of load time.
Critical CSS and JavaScript files are blocking page render, delaying LCP by 600ms.
40 KiB of unused CSS is adding 300ms to both FCP and LCP load times.