Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize donnie.cl
Unused JavaScript wastes 279 KiB and delays LCP by 450ms, significantly impacting Core Web Vitals.
Configure Clerk to load only required authentication components using dynamic imports. Implement code splitting in Next.js to defer Clerk loading until authentication is needed. Use Clerk's tree-shaking friendly imports to exclude unused UI components.
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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This Next.js site has good performance with a score of 81/100, but has room for significant improvement. The biggest issue is excessive unused JavaScript from Clerk authentication services, which wastes 279 KiB and delays page interactivity to 6.8 seconds - well above the recommended 2.5 seconds. The site's Largest Contentful Paint of 4.7 seconds is also slower than ideal, partially caused by render-blocking CSS files that could save 600ms if optimized. Removing unused JavaScript code, deferring non-critical scripts, and inlining critical CSS would likely boost the performance score into the 90s and dramatically improve user experience.
Why It Matters:
Legacy polyfills add unnecessary 14 KiB and 150ms LCP delay for modern browsers that don't need them.
How to Fix:
Update your Next.js config to target modern browsers by setting 'browserslist' to exclude old browsers. Configure Babel preset-env with 'esmodules: true' to avoid transpiling modern JavaScript features. Use Next.js 13+ automatic modern/legacy build splitting.
Why It Matters:
Render-blocking CSS delays First Contentful Paint by 600ms, preventing users from seeing content quickly.
How to Fix:
Use Next.js built-in CSS optimization to automatically inline critical CSS. Move non-critical styles to load asynchronously using next/dynamic. Consider using CSS-in-JS solutions like styled-components for better code splitting.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Next.js Speed Tests
175 KiB of duplicated JavaScript from Nike Design System components is loaded multiple times across bundles.
The LCP image is not discoverable in the initial HTML, causing a 4-second resource load delay.
460 KiB of unused JavaScript is blocking the main thread for 7.3 seconds and delaying LCP by 2.4 seconds.
Multiple redirects add 1.53 seconds delay before the page even starts loading, directly impacting both FCP and LCP.
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.