LCP
Largest Contentful Paint
2.8s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused JavaScript Code
How to optimize crispandnest.com
Remove Unused JavaScript Code
Medium Impact+2 points estimated
Why It Matters
81KB of unused JavaScript is being downloaded, including 39% waste in Google Analytics.
How to Fix
Use Next.js dynamic imports to code-split large components. Configure Google Analytics to load only necessary features using gtag config. Analyze bundle with @next/bundle-analyzer to identify and remove dead code.
0Good
What This Score Means
A score of 93 falls in the "Good" 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
77ms
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 performs well overall with a score of 93/100, but has room for improvement in loading speed. The biggest issue is render-blocking CSS files that are delaying page rendering by an estimated 580ms, which impacts how quickly users see content. Additionally, the site is loading 82KB of unused JavaScript (including Google Analytics code) and serving legacy JavaScript that could be modernized to save 14KB. Optimizing CSS delivery, removing unused code, and updating the JavaScript build process could make the site load noticeably faster for users.
Other Optimization Recommendations
Eliminate Render Blocking CSS
High Impact+3 points estimatedWhy It Matters:
Critical CSS files are blocking initial render and delaying LCP by 600ms.
How to Fix:
Extract above-the-fold CSS and inline it in the Next.js document head. Use next/dynamic to load non-critical CSS asynchronously. Consider splitting CSS chunks by route using Next.js automatic code splitting.
Update JavaScript Build Target
Medium Impact+2 points estimatedWhy It Matters:
Legacy JavaScript polyfills add 14KB of unnecessary code that can improve LCP by 150ms.
How to Fix:
Update your Next.js browserslist config to target modern browsers (ES2020+). Configure Babel preset-env to exclude polyfills for Array.at, Object.hasOwn, and String.trim methods. Set next.config.js to use SWC compiler with modern target.
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
Fix Layout Shift Issues
Massive layout shifts (CLS: 0.903) are caused by content jumping during load, severely impacting user experience.
Remove Unused JavaScript Bundle
372 KiB of unused JavaScript is blocking rendering and delaying LCP by 900ms.
Optimize Server Response Time
Your server takes 2.3 seconds to respond, delaying both FCP and LCP by 2.2 seconds each.
Eliminate Layout Shifts from Images
Unsized images cause a massive 0.90 CLS score, creating jarring visual instability as content loads.