LCP
Largest Contentful Paint
6.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Add Explicit Image Dimensions
How to optimize coloradotest.com
Add Explicit Image Dimensions
Medium Impact+12 points estimated
Why It Matters
Unsized images cause layout shifts and contribute to the poor 1.002 CLS score affecting user experience.
How to Fix
Add width and height attributes to all img elements in your Divi modules. Update the hero image template to include dimensions. Add CSS aspect-ratio properties as fallback for older browsers to prevent content jumping.
0Poor
What This Score Means
A score of 48 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
16ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
1.00
Poor
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 48/100, primarily due to excessive web font loading that's causing severe layout shifts and slow interactivity. The biggest problem is that multiple Google Fonts and custom fonts are loading without proper optimization, creating a massive 1.002 Cumulative Layout Shift score (anything above 0.1 is considered poor) and delaying Time to Interactive to 6.9 seconds. The site could see significant improvements by optimizing font loading with font-display properties, compressing and converting images to modern formats like WebP (which could save 567KB), and removing unused CSS that's blocking the initial render. Fixing these font and image optimization issues alone could potentially improve the performance score by 30+ points and dramatically reduce the jarring visual shifts users experience while the page loads.
Other Optimization Recommendations
Optimize Web Font Loading Strategy
High Impact+25 points estimatedWhy It Matters:
Multiple web fonts cause 1.002 CLS score and 250ms FCP delay, severely impacting user experience.
How to Fix:
Add font-display: swap to all @font-face declarations in your Divi theme. Preload critical fonts like Open Sans and Source Sans Pro using <link rel='preload'> in WordPress header. Use font metric overrides to prevent layout shifts during font swapping.
Compress and Convert Images
High Impact+18 points estimatedWhy It Matters:
Images waste 567KB bandwidth and delay LCP by 1.2 seconds with poor compression and outdated formats.
How to Fix:
Install ShortPixel or Smush to automatically convert PNG images to WebP format (70% smaller). Resize the hero image from 659x672 to actual display size 649x662. Enable responsive images in WordPress to serve appropriate sizes per device.
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
Fix Placeholder Image Loading
Multiple placeholder images are loading instead of actual content, indicating a lazy loading configuration issue affecting LCP.
Optimize Elementor Performance Settings
Elementor's default configuration loads excessive CSS and JavaScript, blocking rendering and increasing load times.
Add Explicit Image Dimensions
Images without width and height attributes cause layout shifts during loading, directly harming your CLS score.
Remove Unused JavaScript Code
75% of PTGuiViewer.js (22KB) goes unused, wasting bandwidth and parse time.