LCP
Largest Contentful Paint
3.8s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Implement Modern Font Loading
How to optimize solares.do
Implement Modern Font Loading
Low Impact+4 points estimated
Why It Matters
Google Fonts lack font-display optimization causing text rendering delays.
How to Fix
Add font-display: swap to your Google Fonts URL parameter (&display=swap). Use Next.js built-in font optimization by importing from next/font/google instead of external CSS links. Preload critical font variants in your Next.js _document.js file.
0Needs Improvement
What This Score Means
A score of 79 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
176ms
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 decent performance with a score of 79/100, but there's significant room for improvement. The biggest problem is excessive unused JavaScript from Google Ads and analytics scripts, which is wasting 317 KB and causing a slow Time to Interactive of 9 seconds - meaning users have to wait that long before they can fully interact with the page. The site is also loading too many Google Fonts and has unused CSS that could be trimmed, but addressing the JavaScript bloat should be the top priority. Cleaning up these third-party scripts and implementing code splitting could easily push the performance score above 90 and dramatically improve user experience.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+12 points estimatedWhy It Matters:
317 KiB of unused JavaScript delays LCP by 300ms and blocks user interactions.
How to Fix:
Use Next.js dynamic imports to code-split Google Ads and GTM scripts. Move non-critical third-party scripts to useEffect hooks or load them after user interaction. Consider replacing heavy Google Ads implementation with lighter alternatives or defer until after page load.
Optimize Hero Image Compression
Medium Impact+8 points estimatedWhy It Matters:
The main hero image can be compressed further to improve LCP by 150ms.
How to Fix:
Increase Cloudinary's compression quality parameter from q_30 to q_20 for the hero image. Add responsive image breakpoints using Next.js Image component with proper sizes prop. Consider using AVIF format with WebP fallback through Cloudinary's f_auto parameter.
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
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.
Optimize Image Compression
Hero image and other assets waste 20 KiB and delay LCP by 150ms due to insufficient compression.
Remove Unused JavaScript
317 KiB of unused JavaScript delays LCP by 300ms, primarily from Google Ads and GTM scripts that aren't fully utilized.