LCP
Largest Contentful Paint
15.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize LCP Image Discovery
How to optimize accademiaconsulenzaimmagine.com
Optimize LCP Image Discovery
High Impact+25 points estimated
Why It Matters
The LCP element isn't discoverable from the initial HTML, adding significant delay to your largest contentful paint.
How to Fix
Add fetchpriority='high' to your hero background image in the Elementor carousel. Ensure the background image URL is directly in the HTML rather than loaded via JavaScript. Consider converting the background image to an IMG tag with proper priority hints.
0Poor
What This Score Means
A score of 25 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
204ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.32
Poor
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 score of 25/100. The biggest problem is an extremely slow Largest Contentful Paint of 15.6 seconds, caused by poor resource discovery and inefficient caching that's delaying critical content loading by over 1.7 seconds. The site also suffers from major layout shifts (0.316 CLS) primarily due to a cookie popup appearing after page load, and excessive JavaScript execution time of 3.9 seconds from heavy reCAPTCHA and jQuery scripts. Immediate fixes should focus on optimizing image delivery, implementing proper caching headers (could save 351 KiB), and reducing unused CSS/JavaScript (could save over 700 KiB combined) to dramatically improve load times and user experience.
Other Optimization Recommendations
Implement Effective Caching Strategy
High Impact+20 points estimatedWhy It Matters:
Poor cache lifetimes are costing 1.75 seconds on LCP with 351 KiB of re-downloaded resources on repeat visits.
How to Fix:
Configure your hosting/CDN to cache JavaScript files for at least 1 year (max-age=31536000). Set proper cache headers for cookie management scripts and Facebook Pixel. Use WP Rocket or W3 Total Cache to automatically handle WordPress-specific caching rules.
Fix Cookie Popup Layout Shift
High Impact+15 points estimatedWhy It Matters:
The cookie consent popup causes a massive 0.316 CLS score, severely impacting user experience and Core Web Vitals.
How to Fix:
Modify the IUSCookie popup to use position: fixed instead of pushing content down. Reserve space in the layout before the popup appears, or implement the popup as an overlay. Update the plugin settings to prevent layout displacement during load.
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 Cookie Popup Layout Shift
The cookie consent popup causes a massive 0.316 CLS score, severely impacting user experience and Core Web Vitals.
Implement Effective Caching Strategy
Poor cache lifetimes are costing 1.75 seconds on LCP with 351 KiB of re-downloaded resources on repeat visits.
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.