LCP
Largest Contentful Paint
12.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused JavaScript Bundles
How to optimize wefeedraw.com
Next.js SiteScore: 46/100Analyzed January 2026
Remove Unused JavaScript Bundles
High Impact+25 points estimated
Why It Matters
792 KiB of unused JavaScript delays LCP by 3.4 seconds and blocks user interactions for 2.4 seconds.
How to Fix
Implement Next.js dynamic imports for Chargebee, accessibility scripts, and other non-critical components. Use next/dynamic with ssr: false for client-only features. Split large bundles using webpack-bundle-analyzer to identify unused code paths.
0Poor
What This Score Means
A score of 46 falls in the "Poor" 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
202ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.10
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 46/100, indicating significant user experience issues. The biggest problem is excessive unused JavaScript (792 KiB of wasted code), particularly from third-party services like Chargebee and accessibility apps, which is dramatically slowing down page load times and causing a terrible Largest Contentful Paint of 12.2 seconds. The site is also serving 89 KiB of outdated JavaScript polyfills that modern browsers don't need, and has inefficient caching that could save an additional 550 KiB on repeat visits. Removing unused JavaScript, updating the build process to eliminate legacy polyfills, and implementing proper caching could potentially improve the performance score by 30+ points and reduce load times by several seconds.
Other Optimization Recommendations
Optimize Legacy JavaScript Polyfills
High Impact+18 points estimatedWhy It Matters:
89 KiB of unnecessary polyfills delays LCP by 300ms for modern browsers that support these features natively.
How to Fix:
Configure Next.js with a modern browserslist target excluding legacy browsers. Update Klaviyo and Facebook Pixel to use modern JavaScript builds. Use differential serving with Next.js to send ES6+ code to modern browsers while keeping polyfills for legacy ones only.
Add LCP Image Priority Hint
Medium Impact+8 points estimatedWhy It Matters:
Hero image lacks fetchpriority='high' attribute which could improve LCP loading performance.
How to Fix:
Add fetchpriority='high' to your Next.js Image component for the hero image. Use Next.js Image priority prop to preload critical above-the-fold images. Ensure hero images use responsive sizes prop for optimal loading across devices.
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
Add LCP Image Priority Hint
Hero image lacks fetchpriority='high' attribute which could improve LCP loading performance.
Optimize Legacy JavaScript Polyfills
89 KiB of unnecessary polyfills delays LCP by 300ms for modern browsers that support these features natively.
Optimize Image Responsive Sizing
Images are served at larger dimensions than displayed, wasting 39 KiB of bandwidth and slowing perceived load time.
Reduce Unused JavaScript Bundle
238 KiB of unused JavaScript is delaying LCP by 450ms and blocking main thread execution.
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