Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize hermanwells.com
JavaScript execution takes 5.1 seconds blocking the main thread and preventing user interactions.
Defer reCAPTCHA loading until user interaction with contact forms. Remove or replace heavy third-party scripts from ClickCease and CallTrack with lighter alternatives. Minify custom JavaScript files (slick.js, main.js) to save 9KB and improve parsing time.
A score of 52 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 52/100, indicating significant issues that affect user experience. The biggest problem is massive layout shifts (3 found) that cause content to jump around as the page loads, particularly from the home banner section and web fonts loading late. Additionally, the site is severely slowed down by render-blocking CSS files that delay page rendering by 1.7 seconds and an extremely slow Time to Interactive of 30.2 seconds due to heavy JavaScript processing. Immediate fixes should include optimizing CSS delivery, reducing unused JavaScript (1.7MB can be eliminated), and addressing the layout shift issues by properly sizing elements and optimizing font loading.
Why It Matters:
Layout shifts score 0.162 causing poor user experience as elements move during page load.
How to Fix:
Add explicit dimensions to the home-page-banner ::after pseudo-element causing the largest shift (0.161 score). Preload critical web fonts (Athelas-Bold.woff2, Athelas-Regular.woff2) using <link rel='preload'> to prevent font-swap layout shifts. Set font-display: swap in CSS for better loading behavior.
Why It Matters:
CSS files are blocking initial page render and delaying LCP by 1.75 seconds.
How to Fix:
Defer non-critical CSS like dashicons.min.css (35KB, 100% unused) and animate.min.css until after page load. Inline critical above-the-fold CSS from main.css directly in HTML head. Use WordPress plugins like Autoptimize to automatically optimize CSS delivery and remove unused code.
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.