LCP
Largest Contentful Paint
6.3s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Render-Blocking CSS Resources
How to optimize donnie.cl
Next.js SiteScore: 69/100Analyzed January 2026
Fix Render-Blocking CSS Resources
High Impact+15 points estimated
Why It Matters
CSS files are blocking initial render for 580ms, delaying First Contentful Paint significantly.
How to Fix
Move critical CSS inline in your Next.js app using styled-jsx or CSS-in-JS solutions. Use Next.js dynamic imports for non-critical CSS with next/dynamic. Consider splitting large CSS chunks (85a6dd488e657d6f.css is 34KB) into smaller, page-specific bundles.
0Needs Improvement
What This Score Means
A score of 69 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
78ms
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 issues with a score of 69/100. The biggest problem is multiple page redirects that are adding nearly 1.7 seconds of delay before your page even starts loading, severely impacting both First Contentful Paint (2.7s) and Largest Contentful Paint (6.3s). Additionally, render-blocking CSS files are preventing the page from displaying content quickly, and oversized images are wasting 245KB of bandwidth. Fixing the redirect chain and optimizing your CSS delivery could immediately improve your Core Web Vitals by 2+ seconds and dramatically enhance user experience.
Other Optimization Recommendations
Eliminate Multiple Page Redirects
High Impact+25 points estimatedWhy It Matters:
Multiple redirects are adding 1.7 seconds to both LCP and FCP, severely impacting Core Web Vitals.
How to Fix:
Remove the Clerk authentication handshake redirect chain that's causing 3 sequential redirects. Configure Clerk to handle authentication without redirects, or implement client-side authentication flow in your Next.js app using Clerk's useAuth() hook directly.
Optimize Image Responsive Sizing
Medium Impact+8 points estimatedWhy It Matters:
Images are 245KB larger than needed due to serving oversized versions, wasting bandwidth and slowing page load.
How to Fix:
Update your Next.js Image component sizes prop to match actual display dimensions (currently serving 640x640 for 263x263 display). Use Next.js Image optimization with proper breakpoints in your srcSet. Consider using fill={true} with object-fit for responsive containers.
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