LCP
Largest Contentful Paint
4.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused JavaScript Code
How to optimize donnie.cl
Next.js SiteScore: 83/100Analyzed January 2026
Remove Unused JavaScript Code
High Impact+12 points estimated
Why It Matters
282 KiB of unused JavaScript from Clerk authentication is delaying LCP by 450ms and blocking interactivity.
How to Fix
Implement dynamic imports for Clerk components that aren't immediately needed. Use Next.js code splitting with React.lazy() to load authentication UI only when required. Configure Clerk to load only essential features on initial page load using selective imports.
0Needs Improvement
What This Score Means
A score of 83 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
71ms
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 83/100, but has room for improvement in loading speed. The biggest problem is oversized images that are wasting 350 KiB of bandwidth and delaying your Largest Contentful Paint to 4.6 seconds - images are being delivered at 640x640 pixels but only displayed at much smaller sizes like 150x150. Additionally, the site is loading 282 KiB of unused JavaScript from Clerk authentication services and legacy JavaScript polyfills that aren't needed for modern browsers. Optimizing your Next.js image components to serve properly sized images and removing unnecessary JavaScript could easily push your performance score above 90 and significantly speed up page loading.
Other Optimization Recommendations
Optimize Image Delivery and Sizing
High Impact+8 points estimatedWhy It Matters:
Images are oversized for their display dimensions, wasting 350 KiB and delaying LCP by 150ms.
How to Fix:
Update your Next.js Image component sizes prop to better match actual display dimensions. For the category images displayed at 150px, use w=256 instead of w=640 in your image URLs. Configure responsive breakpoints in next.config.js to serve appropriately sized images based on viewport.
Inline Critical CSS
Medium Impact+6 points estimatedWhy It Matters:
Render-blocking CSS files are delaying First Contentful Paint by 600ms, making the page appear slower to load.
How to Fix:
Extract critical above-the-fold CSS and inline it directly in your Next.js _document.js file. Use next-critical or a similar tool to automatically identify critical CSS. Move non-critical CSS to load asynchronously after initial render using rel='preload' with onload handler.
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
Eliminate Duplicate JavaScript Modules
175 KiB of duplicated JavaScript from Nike Design System components is loaded multiple times across bundles.
Fix LCP Image Discovery
The LCP image is not discoverable in the initial HTML, causing a 4-second resource load delay.
Remove Unused JavaScript Code
460 KiB of unused JavaScript is blocking the main thread for 7.3 seconds and delaying LCP by 2.4 seconds.
Fix Page Redirects Chain
Multiple redirects add 1.53 seconds delay before the page even starts loading, directly impacting both FCP and LCP.
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