LCP
Largest Contentful Paint
7.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Unused JavaScript Code
How to optimize good.fella.com
Next.js SiteScore: 63/100Analyzed February 2026
Eliminate Unused JavaScript Code
High Impact+25 points estimated
Why It Matters
246 KiB of unused JavaScript delays LCP by 1.2 seconds and blocks critical rendering.
How to Fix
Analyze your Next.js bundle with @next/bundle-analyzer to identify unused code. Enable tree shaking by ensuring imports use named exports instead of default exports. Use dynamic imports with next/dynamic for components not needed on initial load, especially for the large chunks like efb4f58b7bdf0ed7.js (84% unused).
0Needs Improvement
What This Score Means
A score of 63 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
459ms
Needs Improvement
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 with a score of 63/100, primarily due to excessive unused JavaScript that's wasting 246 KiB and delaying page load by 1.2 seconds. The biggest issue is an extremely slow Largest Contentful Paint of 7.4 seconds, caused by oversized images and render-blocking CSS files that prevent content from appearing quickly. Removing unused JavaScript code, optimizing the hero image (which is 102 KiB larger than needed), and deferring non-critical CSS could improve the score by 25+ points and dramatically speed up the initial page load. The site also suffers from forced reflows that cause layout shifts, adding another 400+ milliseconds of delay during user interactions.
Other Optimization Recommendations
Fix Forced Layout Reflows
High Impact+15 points estimatedWhy It Matters:
JavaScript is causing 301ms of forced reflows that block the main thread and delay interactivity.
How to Fix:
Batch DOM reads and writes to avoid layout thrashing in your React components. Use CSS transforms instead of changing layout properties like width/height. Move geometric property reads (offsetWidth, getBoundingClientRect) outside of render loops and cache the values.
Optimize Hero Image Loading
Medium Impact+10 points estimatedWhy It Matters:
The main hero image is 102KB oversized and delays LCP by 400ms with poor responsive sizing.
How to Fix:
Update your Sanity image configuration to serve properly sized images using their responsive image API. Add responsive breakpoints in your Next.js Image component with proper sizes prop. Set the hero image to priority={true} and use fill or intrinsic sizing to match display dimensions exactly.
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