Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize hermanwells.com
Multiple forced reflows are causing layout thrashing and degrading page responsiveness.
Batch DOM reads and writes to avoid repeated layout calculations. Cache geometric properties instead of repeatedly querying offsetWidth/height. Move style changes to requestAnimationFrame callbacks to align with browser paint cycles.
A score of 99 falls in the "Good" 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 achieves an excellent performance score of 99/100, indicating very fast loading times for users. The biggest optimization opportunity is reducing unused CSS, which could save 36 KiB by removing unnecessary styling rules that aren't being used on the page. Additional improvements include eliminating 62 KiB of unused JavaScript from Google Tag Manager, updating legacy JavaScript code to modern standards (saving 13 KiB), and extending cache lifetimes for third-party scripts. While these optimizations would further enhance performance, the site is already performing exceptionally well and provides an excellent user experience.
Why It Matters:
89% of your main stylesheet (36 KiB) goes unused, slowing initial page rendering unnecessarily.
How to Fix:
Use a tool like PurgeCSS to remove unused CSS rules from your stylesheets. Split critical above-the-fold CSS and inline it directly in the HTML head. Defer loading of non-critical CSS using media='print' onload='this.media="all"' technique.
Why It Matters:
42% of your GTM script (62 KiB) is unused JavaScript that delays page interactivity.
How to Fix:
Review your GTM container and remove unused tags, triggers, and variables. Split tracking into essential (load immediately) and non-essential (defer until after page load). Consider loading GTM asynchronously after the window load event for non-critical tracking.
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
42% of your GTM script (62 KiB) is unused JavaScript that delays page interactivity.
89% of your main stylesheet (36 KiB) goes unused, slowing initial page rendering unnecessarily.
60KB of unused JavaScript from Google Analytics delays LCP by 750ms and wastes bandwidth.
CSS and fonts block initial render, delaying both LCP and FCP by 350ms each.