LCP
Largest Contentful Paint
6.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce JavaScript Main Thread Blocking
How to optimize clover.security
Reduce JavaScript Main Thread Blocking
High Impact+20 points estimated
Why It Matters
4.5 seconds of main thread work with 560ms TBT prevents user interactions and delays page responsiveness.
How to Fix
Defer HubSpot forms JavaScript (518KB unused) until user interaction using WP Rocket's JavaScript optimization. Remove legacy polyfills from third-party scripts (48KB savings). Minify your custom script.js file to save 5KB.
0Needs Improvement
What This Score Means
A score of 51 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
294ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.06
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This WordPress site has poor performance with a score of 51/100. The biggest problem is excessive JavaScript processing that's blocking the main thread for 4.5 seconds, causing an extremely slow Time to Interactive of 16.6 seconds and a poor Largest Contentful Paint of 6.6 seconds. The site is also loading oversized images (saving 786 KiB possible) and render-blocking CSS that delays initial page rendering by over 2 seconds. Reducing JavaScript payloads, optimizing images to appropriate sizes, and deferring non-critical scripts could improve the score by 30+ points and dramatically enhance user experience.
Other Optimization Recommendations
Optimize Background Images Delivery
High Impact+25 points estimatedWhy It Matters:
Oversized hero image (285KB waste) delays LCP by 2.45 seconds and significantly impacts loading performance.
How to Fix:
Resize the decorative background image from 2880x4643 to actual display dimensions (766x1235). Use WordPress responsive images or install Smush plugin for automatic sizing. Add explicit width='766' height='1235' attributes to prevent layout shifts.
Eliminate Render Blocking CSS
High Impact+15 points estimatedWhy It Matters:
Critical CSS blocks first paint by 2.25 seconds, significantly delaying when users see content.
How to Fix:
Use Autoptimize or WP Rocket to inline critical above-the-fold CSS. Remove 87% unused CSS rules from your minified stylesheet. Defer non-critical CSS loading using media='print' onload technique in your WordPress theme.
Keep Your Site Fast After Optimization
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.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More WordPress Speed Tests
WordPress Performance Resources
Remove Unused CSS Rules
Your stylesheet contains 10 KiB of completely unused CSS that increases parsing time and network overhead.
Implement Responsive Image Sizing
Images are oversized for their display dimensions, wasting 32 KiB of bandwidth and potentially impacting LCP timing.
Optimize Font Loading Strategy
Critical font resources in your dependency chain are blocking render and extending LCP by creating a 7.3-second loading bottleneck.
Compress and Modernize Images
Images waste 588 KiB of bandwidth and slow LCP by 550ms due to poor compression and oversized dimensions.