LCP
Largest Contentful Paint
4.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Unused JavaScript Code
How to optimize donnie.cl
Next.js SiteScore: 81/100Analyzed January 2026
Eliminate Unused JavaScript Code
High Impact+15 points estimated
Why It Matters
279 KiB of unused JavaScript is delaying LCP by 450ms and blocking user interactions.
How to Fix
Configure Next.js to code-split Clerk authentication components using dynamic imports with ssr: false. Audit your bundle with @next/bundle-analyzer to identify unused code. Move authentication logic to load only when needed rather than on initial page load.
0Needs Improvement
What This Score Means
A score of 81 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
88ms
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/React site has good performance with a score of 81/100, but has a critical issue with JavaScript bloat that's severely impacting user experience. The biggest problem is 279 KiB of unused JavaScript (primarily from Clerk authentication scripts), which is making the page take 7.1 seconds to become fully interactive and causing a poor 4.9-second Largest Contentful Paint. Additionally, render-blocking CSS files are delaying initial page rendering by 590ms. Removing unused JavaScript, code-splitting the authentication features, and optimizing CSS delivery could easily push this site into the 90+ performance range and dramatically improve user experience.
Other Optimization Recommendations
Optimize CSS Delivery Strategy
High Impact+12 points estimatedWhy It Matters:
Render-blocking CSS is delaying First Contentful Paint by 600ms, hurting perceived performance.
How to Fix:
Extract critical CSS for above-the-fold content and inline it in the HTML head. Use Next.js built-in CSS optimization by moving non-critical styles to load asynchronously. Consider splitting your 34KB CSS bundle into route-specific chunks using Next.js automatic CSS code splitting.
Modernize JavaScript Build Target
Medium Impact+8 points estimatedWhy It Matters:
Legacy JavaScript polyfills add unnecessary 14 KiB and reduce execution efficiency for modern browsers.
How to Fix:
Update your Next.js browserslist config to target modern browsers (>95% coverage). Remove polyfills for Array.prototype.at, Object.hasOwn, and other baseline features. Configure your build to output ES2022+ syntax while maintaining a legacy fallback only if needed.
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
Update JavaScript Build Configuration
Legacy JavaScript polyfills add 20KB of unnecessary code for modern browsers, slowing LCP by 200ms.
Eliminate Render Blocking CSS
CSS files are blocking first paint, delaying FCP by 300ms and hurting user experience.
Remove Unused JavaScript Code
35% of your JavaScript bundle (24KB) is unused, increasing LCP by 300ms and blocking page interactivity.
Optimize Decorative Images
Oversized garland images waste 1MB of bandwidth without contributing to core functionality.
Frequently Asked Questions
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