LCP
Largest Contentful Paint
8.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Page Redirects Chain
How to optimize deskfunnel.online
Eliminate Page Redirects Chain
Medium Impact+12 points estimated
Why It Matters
Multiple redirects from deskfunnel.online to www.deskfunnel.online waste 780ms before content loads.
How to Fix
Configure server to serve content directly from www.deskfunnel.online without redirects. Update all internal links to use the canonical www version. Set up proper DNS CNAME records to avoid the redirect chain entirely.
0Needs Improvement
What This Score Means
A score of 70 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
120ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.09
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js site has poor performance with a score of 70/100, primarily due to an extremely slow Time to Interactive of 8.6 seconds. The biggest issue is a redirect chain that's wasting 780ms before the page even starts loading, combined with inefficient caching that could save 336 KiB of data transfer. The site is also serving oversized images (96 KiB wasted) and has 386 KiB of unused JavaScript code that's blocking the page load. Fixing the redirect, implementing proper cache headers, and optimizing image sizes could improve the score by 15-20 points and dramatically reduce load times. The LCP image also needs to be made discoverable in the initial HTML to avoid discovery delays.
Other Optimization Recommendations
Fix Image Discovery and Sizing
High Impact+25 points estimatedWhy It Matters:
LCP image is not discoverable in HTML and lacks proper dimensions, delaying page load by 8.5 seconds.
How to Fix:
Add the main image directly to HTML instead of client-side rendering. Set explicit width and height attributes on the image element. Apply fetchpriority='high' to the LCP image. Use Next.js Image component with proper priority prop for automatic optimization.
Remove Unused JavaScript Code
High Impact+20 points estimatedWhy It Matters:
386 KiB of unused JavaScript is blocking page load and delaying LCP by 2.25 seconds.
How to Fix:
Use Next.js bundle analyzer to identify unused code in chunks 482.dd415727fffeb357.js and 0e9f781b-9dd9df1add80d972.js. Implement dynamic imports for non-critical components. Split vendor bundles and lazy load Facebook tracking scripts after page interaction.
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
Add Explicit Image Dimensions
Missing width/height attributes on images can cause layout shifts during loading.
Remove Unused JavaScript Bundle
386 KiB of unused JavaScript delays page interactivity by 1.8 seconds.
Fix LCP Image Loading
Your LCP image takes 7.5 seconds to load, causing the worst Core Web Vital score.
Remove Unused JavaScript Bundles
386KB of unused JavaScript code increases bundle size and delays interactivity by over 2 seconds.