LCP
Largest Contentful Paint
15.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Layout Shift Issues
How to optimize chamfr.com
Fix Layout Shift Issues
Medium Impact+8 points estimated
Why It Matters
HubSpot chat widget and page elements cause 0.154 CLS score, creating jarring content jumps during load.
How to Fix
Add CSS min-height and width to reserve space for the HubSpot chat widget container. Set explicit dimensions on all images and ad banners. Preload critical fonts using rel='preload' in your WordPress theme's functions.php to prevent font swap layout shifts.
0Poor
What This Score Means
A score of 21 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
423ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.15
Needs Improvement
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This WordPress site has severe performance issues with a critically low score of 21/100. The biggest problem is massive, unoptimized images that are dramatically slowing down page loading - particularly a 400KB image that's twice the size it needs to be and poorly compressed, causing an estimated 600KB of wasted data transfer. The site is also plagued by excessive JavaScript execution (taking 4.8 seconds) and nearly 1.5MB of unused JavaScript code, resulting in painfully slow load times of 15.8 seconds for the largest content and 28.2 seconds to become interactive. Compressing and properly sizing images, removing unused JavaScript, and addressing render-blocking resources could potentially improve the performance score by 50+ points and transform the user experience from unusable to acceptable.
Other Optimization Recommendations
Optimize and Compress Images
High Impact+25 points estimatedWhy It Matters:
The largest image alone wastes 371KB and delays LCP by 150ms, representing a major performance bottleneck.
How to Fix:
Install ShortPixel or Imagify WordPress plugin to automatically compress all images. Resize the 768x768 banner image to its displayed 382x382 size. Convert PNG images to WebP format for 60-80% size reduction. Enable responsive images in your WordPress theme settings.
Reduce JavaScript Bundle Sizes
High Impact+20 points estimatedWhy It Matters:
Unused JavaScript consumes 1.4MB and blocks the main thread for 4.8 seconds, severely impacting user interaction.
How to Fix:
Remove or replace the heavy reCAPTCHA implementation with a lighter alternative like hCaptcha. Audit WordPress plugins and deactivate unused ones, especially WP Event Manager components. Use WP Rocket to defer non-critical scripts and enable JavaScript minification and concatenation.
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
Implement Efficient Resource Caching
Poor cache policies waste 199 KB on repeat visits, slowing return user experience.
Optimize Third-Party Script Loading
Facebook tracking scripts load 65 KB of unused JavaScript and legacy polyfills unnecessarily.
Remove Unused CSS Code
39% of your CSS (11 KB) is unused, blocking render and delaying FCP by 150ms.
Reduce JavaScript Bundle Sizes
Unused JavaScript consumes 1.4MB and blocks the main thread for 4.8 seconds, severely impacting user interaction.