LCP
Largest Contentful Paint
25.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Render Blocking Resources
How to optimize test.whitehouseblackmarket.com
Fix Render Blocking Resources
Medium Impact+8 points estimated
Why It Matters
Critical CSS files are blocking initial page render and delaying LCP by 200ms.
How to Fix
Inline critical CSS for above-the-fold content in your Next.js pages. Use next/dynamic with ssr: false for non-critical components. Implement CSS code splitting to load only necessary styles per route using Next.js built-in CSS modules.
0Poor
What This Score Means
A score of 32 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
716ms
Poor
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 severe performance issues with a critically low score of 32/100. The biggest problem is massive JavaScript bloat, with nearly 3.1MB of unused JavaScript causing the page to take over 38 seconds to become interactive and blocking user interactions for over 4 seconds. The site is loading enormous script files (like a 2MB chunk that's 99% unused) and suffering from poor caching strategies, render-blocking resources, and excessive main thread work. Immediate actions should focus on code splitting, removing unused JavaScript, implementing proper caching headers, and deferring non-critical scripts to dramatically improve Core Web Vitals and user experience.
Other Optimization Recommendations
Eliminate Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
Removing 3,139 KiB of unused JavaScript will reduce network transfer time and improve LCP by 12 seconds.
How to Fix:
Use Next.js tree shaking by importing only specific functions instead of entire libraries. Audit the 1889-230b4465461f49c4.js chunk (98% unused) and FindMine module (84% unused). Enable webpack-bundle-analyzer to identify dead code and remove unnecessary third-party integrations.
Reduce JavaScript Execution Time
High Impact+20 points estimatedWhy It Matters:
JavaScript takes 10.5 seconds to execute, blocking the main thread and preventing user interactions for 4.3 seconds.
How to Fix:
Code-split large bundles using Next.js dynamic imports with loading states. Move third-party scripts like FindMine and AudioEye to web workers or defer until after page load. Optimize the 1602-56d78daed72b7a22.js chunk that's consuming 1.5 seconds of execution time.
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
Eliminate Render-Blocking CSS Resources
Render-blocking CSS is delaying LCP by 1.95 seconds, preventing the page from displaying content quickly.
Reduce JavaScript Execution Time
JavaScript takes 10.5 seconds to execute, blocking the main thread and preventing user interactions for 4.3 seconds.
Eliminate Unused JavaScript Code
Removing 3,139 KiB of unused JavaScript will reduce network transfer time and improve LCP by 12 seconds.
Implement Long-term Asset Caching
Poor caching strategy wastes 74KB on repeat visits and slows LCP by 300ms.