LCP
Largest Contentful Paint
6.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize CSS Delivery Strategy
How to optimize repleno.com
Optimize CSS Delivery Strategy
Medium Impact+6 points estimated
Why It Matters
Render-blocking CSS files delay First Contentful Paint by 450ms, preventing critical content from appearing quickly.
How to Fix
Inline critical above-the-fold CSS directly in the Next.js page head using styled-jsx or CSS-in-JS. Defer non-critical CSS using Next.js dynamic imports or the 'media' attribute trick. Split your 41KB CSS bundle into critical and non-critical parts to reduce render blocking.
0Needs Improvement
What This Score Means
A score of 67 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
182ms
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 poor performance with a score of 67/100, struggling significantly with Core Web Vitals. The biggest problem is an extremely slow Largest Contentful Paint of 6.5 seconds, caused by multiple issues including render-blocking CSS files that waste 450ms, a redirect from the root domain adding 750ms delay, and 69KB of unused JavaScript code. The site also suffers from long network dependency chains and poor interactivity with a 6.5-second Time to Interactive. Fixing the redirect, optimizing CSS delivery, and removing unused JavaScript could dramatically improve loading speed and user experience by several seconds.
Other Optimization Recommendations
Eliminate URL Redirect Chain
High Impact+12 points estimatedWhy It Matters:
The redirect from repleno.com to repleno.com/de adds 750ms delay to both LCP and FCP, severely impacting Core Web Vitals.
How to Fix:
Configure your Next.js server or CDN to serve the German version directly without redirects. Use Next.js middleware to handle locale routing at the edge. Set up proper DNS/server configuration to avoid the initial redirect chain.
Remove Unused JavaScript Code
High Impact+8 points estimatedWhy It Matters:
69KB of unused JavaScript delays LCP by 450ms and blocks critical rendering with unnecessary polyfills.
How to Fix:
Update your Next.js build target to exclude legacy polyfills for modern browsers by setting 'browserslist' to remove IE support. Use Next.js bundle analyzer to identify and remove unused dependencies. Configure webpack to exclude unnecessary polyfills like Array.at() and Object.fromEntries() for modern browser targets.
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 Image Compression and Sizing
Images are 25 KiB larger than necessary and using suboptimal compression settings.
Eliminate Render-Blocking CSS
CSS files are blocking first paint by 710ms, significantly delaying user perception of page load.
Remove Unused JavaScript Code
69 KiB of unused JavaScript is delaying LCP by 450ms and blocking page interactivity.
Eliminate URL Redirect Chain
The redirect from repleno.com to repleno.com/de adds 750ms delay to both LCP and FCP, severely impacting Core Web Vitals.