LCP
Largest Contentful Paint
5.7s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Redirect Chain and Document Latency
How to optimize ventaassets.com
Fix Redirect Chain and Document Latency
High Impact+25 points estimated
Why It Matters
HTTP redirects and slow document response add 950ms to both LCP and FCP, severely impacting Core Web Vitals.
How to Fix
Update all internal links to point directly to https://www.ventaassets.com/ instead of the non-www version. Configure your server to serve the canonical URL without redirects. Optimize server response time by enabling compression and reviewing database queries in your Next.js API routes.
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
145ms
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 website has moderate performance issues with a score of 72/100. The biggest problem is a redirect from the non-www to www version of the site, which wastes 780ms and significantly delays both First Contentful Paint and Largest Contentful Paint (currently at a poor 5.7 seconds). Additionally, render-blocking CSS files are preventing the page from loading quickly, and there's 56KB of unused JavaScript that could be removed. Fixing the redirect issue and optimizing CSS delivery could improve the score by 15-20 points and dramatically improve the user experience, especially on mobile devices.
Other Optimization Recommendations
Eliminate Render-Blocking CSS
High Impact+20 points estimatedWhy It Matters:
Three CSS files block initial page rendering for 940ms, directly delaying LCP and FCP by nearly 1 second.
How to Fix:
Inline critical CSS for above-the-fold content directly in your Next.js pages using styled-jsx or CSS-in-JS. Use Next.js dynamic imports with ssr: false for non-critical CSS. Consider splitting large CSS bundles and loading them progressively.
Reduce Unused JavaScript
Medium Impact+12 points estimatedWhy It Matters:
70% of JavaScript (56KB) goes unused, wasting 300ms of LCP performance and increasing bundle size.
How to Fix:
Implement Next.js dynamic imports for heavy components that aren't immediately needed. Use webpack-bundle-analyzer to identify unused code in chunks/8456-75b1b6eb62e13709.js. Enable tree shaking and consider code splitting at the route level using Next.js automatic code splitting.
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
Reduce Unused JavaScript
70% of JavaScript (56KB) goes unused, wasting 300ms of LCP performance and increasing bundle size.
Optimize JavaScript Bundle Size
Unused JavaScript totals 579KB with heavy YouTube embeds causing 1.4 seconds of execution time and blocking user interactions.
Eliminate Render-Blocking CSS
Three CSS files block initial page rendering for 940ms, directly delaying LCP and FCP by nearly 1 second.
Fix Server Response Time
Root document takes 4.46 seconds to respond, blocking all other resources and severely impacting LCP by 4.35 seconds.