LCP
Largest Contentful Paint
3.8s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Image Delivery and Sizing
How to optimize finisher.sigma.vercel.app
Optimize Image Delivery and Sizing
High Impact+12 points estimated
Why It Matters
Images are oversized for their display dimensions, wasting 201 KiB and delaying LCP by 300ms.
How to Fix
Configure Next.js Image component with proper responsive sizes prop. Update the CloudFront image with width=665 instead of 1920. Use Next.js built-in image optimization with format='avif' and quality=80 for automatic compression.
0Needs Improvement
What This Score Means
A score of 83 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
160ms
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 good performance with a score of 83/100, but there are several opportunities for improvement. The biggest issue is oversized images that are wasting 201 KiB of bandwidth and delaying your Largest Contentful Paint by 300ms - particularly one image that's being served at 1920x1456 pixels but only displayed at 665x1182. Additionally, there's 28 KiB of unused JavaScript code that could be removed or deferred to save another 150ms. Implementing responsive images and cleaning up unnecessary JavaScript could easily push your score into the 90s and provide a noticeably faster user experience.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+8 points estimatedWhy It Matters:
28 KiB of unused JavaScript delays LCP by 150ms and blocks page interactivity.
How to Fix:
Analyze the Next.js chunk file to identify unused components and libraries. Use dynamic imports with React.lazy() for components below the fold. Configure Next.js bundle analyzer to identify and tree-shake unused dependencies from the build.
Fix Element Render Delay
Medium Impact+6 points estimatedWhy It Matters:
LCP element has 2.9 seconds of render delay preventing fast visual completion.
How to Fix:
Remove JavaScript that queries DOM geometry after style changes to prevent forced reflows. Move animations to CSS transforms instead of changing layout properties. Ensure LCP element (NECESSIDADES span) renders without JavaScript dependencies by making it static content.
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
Fix Element Render Delay
LCP element has 2.9 seconds of render delay preventing fast visual completion.
Remove Unused JavaScript Code
28 KiB of unused JavaScript delays LCP by 150ms and blocks page interactivity.
Eliminate Render Blocking CSS
107 KiB of unused CSS and render-blocking stylesheets delay First Contentful Paint by 1.4 seconds.
Fix Critical Image Loading Issues
LCP image has lazy loading enabled and takes 2.4 seconds to discover, severely delaying page rendering.