LCP
Largest Contentful Paint
18.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Layout Shift from Images
How to optimize zeeetrading.com
Fix Layout Shift from Images
High Impact+20 points estimated
Why It Matters
Your CLS score of 1.082 is primarily caused by unsized images in the footer causing massive layout shifts.
How to Fix
Add explicit width and height props to all Next.js Image components, especially the footer logo and payment images. Use the Next.js Image component instead of regular img tags to automatically prevent layout shifts. Set proper aspect ratios in CSS for background images like the banner hero image.
0Poor
What This Score Means
A score of 12 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
495ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
1.08
Poor
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js e-commerce site has severe performance issues with a critically low score of 12/100. The biggest problem is an extremely slow Largest Contentful Paint of 18 seconds, caused primarily by multiple page redirects (wasting over 1 second) and a massive 6-second delay in loading the main banner image. The site also suffers from excessive unused CSS (310 KiB that could be removed), significant layout shifts (1.08 CLS score), and a very slow Time to Interactive of 23.2 seconds. Eliminating the redirect chain, optimizing the CSS delivery, and fixing the banner image loading could potentially improve the performance score by 40+ points and dramatically enhance user experience.
Other Optimization Recommendations
Eliminate Multiple Page Redirects
High Impact+25 points estimatedWhy It Matters:
Your site has a redirect chain costing 1.08 seconds and significantly delaying both FCP and LCP.
How to Fix:
Configure your Next.js app to serve the canonical URL directly. Update your next.config.js to add a redirect from the root domain to /en/home in one step, or better yet, serve content directly at the root. Remove the intermediate redirect through /en/ to avoid the 3-redirect chain.
Remove Unused CSS and JavaScript
Medium Impact+12 points estimatedWhy It Matters:
310KB of unused CSS and legacy JavaScript polyfills are unnecessarily bloating your bundles and slowing page load.
How to Fix:
Enable CSS tree-shaking in your Next.js build by reviewing your CSS imports and removing unused styles. Update your Next.js target in next.config.js to 'es2017' or newer to eliminate unnecessary polyfills for Array.prototype.at and other modern features. Use bundle analyzer to identify and split large chunks.
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
Remove Unused JavaScript Code
46KB of unused JavaScript delays LCP by 300ms and wastes bandwidth on mobile users.
Optimize Image Sizing and Compression
Oversized images waste 84KB and delay LCP by 150ms with unnecessary data transfer.
Eliminate Render Blocking CSS
Blocking CSS delays LCP and FCP by 850ms, preventing users from seeing content quickly.
Remove Unused CSS and JavaScript
310KB of unused CSS and legacy JavaScript polyfills are unnecessarily bloating your bundles and slowing page load.