LCP
Largest Contentful Paint
5.3s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Image Compression
How to optimize solares.do
Optimize Image Compression
Medium Impact+8 points estimated
Why It Matters
Hero image and other assets waste 20 KiB and delay LCP by 150ms due to insufficient compression.
How to Fix
Since you're using Cloudinary, optimize the compression settings by reducing q_30 to q_20 for non-hero images and ensure proper responsive sizing. Use Next.js Image component with proper sizes prop and consider using f_auto instead of f_avif for better browser compatibility.
0Needs Improvement
What This Score Means
A score of 75 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
124ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js site has moderate performance issues with a score of 75/100. The biggest problem is a redirect chain that's wasting 780ms and significantly slowing down both First Contentful Paint and Largest Contentful Paint, which currently takes 5.3 seconds to load. Additionally, the site is loading 317 KiB of unused JavaScript from Google Ads and analytics scripts, further delaying interactivity to 9.2 seconds. Fixing the redirect issue and removing unused JavaScript could improve the performance score by 15-20 points and dramatically enhance user experience.
Other Optimization Recommendations
Fix Redirect Chain Issue
High Impact+12 points estimatedWhy It Matters:
The redirect from solares.do to www.solares.do adds 780ms delay to both LCP and FCP, significantly impacting page load time.
How to Fix:
Update your Next.js configuration to redirect at the edge using middleware or configure your DNS/hosting to serve www.solares.do directly. In next.config.js, add a redirect rule or ensure your canonical domain is properly configured to avoid the redirect chain.
Remove Unused JavaScript
High Impact+10 points estimatedWhy It Matters:
317 KiB of unused JavaScript delays LCP by 300ms, primarily from Google Ads and GTM scripts that aren't fully utilized.
How to Fix:
Audit your Google Tag Manager container to remove unused tags and triggers. Implement code splitting in Next.js using dynamic imports for non-critical components. Consider loading Google Ads scripts only when needed using next/script with strategy='lazyOnload'.
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 Next.js Speed Tests
Next.js Performance Resources
Implement Modern Font Loading
Google Fonts lack font-display optimization causing text rendering delays.
Optimize Hero Image Compression
The main hero image can be compressed further to improve LCP by 150ms.
Remove Unused JavaScript Code
317 KiB of unused JavaScript delays LCP by 300ms and blocks user interactions.
Remove Unused JavaScript
317 KiB of unused JavaScript delays LCP by 300ms, primarily from Google Ads and GTM scripts that aren't fully utilized.