LCP
Largest Contentful Paint
4.7s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render-Blocking CSS
How to optimize repleno.com
Eliminate Render-Blocking CSS
High Impact+15 points estimated
Why It Matters
CSS files are blocking first paint by 710ms, significantly delaying user perception of page load.
How to Fix
Inline critical CSS for above-the-fold content using Next.js styled-jsx or CSS-in-JS solutions. Use next/dynamic with ssr: false for non-critical components. Implement CSS code splitting by moving non-critical styles to component-level imports.
0Needs Improvement
What This Score Means
A score of 82 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
105ms
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 82/100, but there's significant room for improvement. The biggest issue is render-blocking CSS files that are delaying page loading by 710ms and contributing to a slow Largest Contentful Paint of 4.7 seconds. The site is also loading 69KB of unused JavaScript code, which could be eliminated through code splitting and lazy loading to improve page speed by an additional 450ms. Addressing these blocking resources and optimizing the oversized images could easily push this site into the 90+ performance range and provide a much faster user experience.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+12 points estimatedWhy It Matters:
69 KiB of unused JavaScript is delaying LCP by 450ms and blocking page interactivity.
How to Fix:
Use Next.js bundle analyzer (@next/bundle-analyzer) to identify unused code in your chunks. Implement dynamic imports for non-critical components and enable tree-shaking in your webpack config. Split large chunks using Next.js code splitting features.
Optimize Image Compression and Sizing
Medium Impact+6 points estimatedWhy It Matters:
Images are 25 KiB larger than necessary and using suboptimal compression settings.
How to Fix:
Reduce the quality parameter in your Next.js Image component from q=75 to q=50-60 for non-hero images. Ensure responsive sizing matches display dimensions by using proper sizes prop. Enable Next.js automatic WebP conversion in next.config.js.
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.
Optimize CSS Delivery Strategy
Render-blocking CSS files delay First Contentful Paint by 450ms, preventing critical content from appearing quickly.
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.