LCP
Largest Contentful Paint
3.9s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Layout Shifts in Homepage
How to optimize cienegaspa.com
Fix Layout Shifts in Homepage
High Impact+15 points estimated
Why It Matters
Large layout shifts (CLS 0.143) cause poor user experience and hurt Core Web Vitals scoring.
How to Fix
Add explicit dimensions to the hero section div and body elements causing shifts. Set fixed heights or min-heights in CSS for the .vert_center container. Preload critical fonts to prevent font swap layout shifts. Test with slow 3G throttling to identify timing issues.
0Needs Improvement
What This Score Means
A score of 72 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
196ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.14
Needs Improvement
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This WordPress site has below-average performance with a score of 72/100, primarily hampered by layout stability and loading efficiency issues. The biggest problem is significant layout shifts (scoring 0/100) that occur as content loads, creating a jarring user experience where elements jump around the page unexpectedly. Additionally, the site is weighed down by a massive 4.7MB total payload—largely due to a 3.9MB background video file—and render-blocking CSS files that delay initial page rendering by over 1 second. The WP Smush Pro plugin is also causing forced reflows that hurt performance, and there's substantial unused JavaScript (103KB) from Google Analytics scripts that could be optimized.
Other Optimization Recommendations
Optimize WP Smush Plugin Settings
High Impact+12 points estimatedWhy It Matters:
Smush plugins are causing 150ms+ of forced reflows that block the main thread and delay interactivity.
How to Fix:
In WP Smush Pro settings, disable real-time image detection or reduce detection frequency. Move lazy loading initialization to after page load using WordPress wp_enqueue_script with 'defer' attribute. Consider switching to native browser lazy loading for better performance.
Replace Background Video with Optimized Image
High Impact+18 points estimatedWhy It Matters:
The 3.96MB mobile background video accounts for 83% of total page weight and significantly delays loading.
How to Fix:
Replace bg_final_mobile.mp4 with an optimized WebP hero image (aim for <500KB). Use CSS background-image with multiple breakpoints for responsive loading. Add the hero image with fetchpriority='high' since it's likely the LCP element. Keep video as optional enhancement loaded after page interactive.
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 Long-Term Browser Caching
Short cache lifetimes force unnecessary re-downloads of static assets, wasting 40 KiB on repeat visits.
Eliminate Unused CSS and JavaScript
99 KiB of unused CSS and 440 KiB of unused JavaScript waste bandwidth and slow down parsing.
Remove Render-Blocking JavaScript Resources
Render-blocking JavaScript is delaying LCP by 4.25 seconds, preventing critical content from displaying quickly.
Eliminate Render-Blocking Resources
Critical CSS and JavaScript files are blocking initial page render, delaying FCP by 250ms.