LCP
Largest Contentful Paint
13.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Image Sizes and Loading
How to optimize usepike.com
Optimize Image Sizes and Loading
High Impact+12 points estimated
Why It Matters
Images are 1,424 KiB oversized and delay LCP by 250ms while consuming excessive bandwidth.
How to Fix
Use Next.js Image component with proper responsive sizes prop (e.g., sizes='(max-width: 768px) 100vw, 50vw'). Generate multiple image variants using next/image's built-in optimization. Replace loading='lazy' with loading='eager' and fetchpriority='high' for above-the-fold images like the finance dashboard.
0Needs Improvement
What This Score Means
A score of 66 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
143ms
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 site has poor performance issues with a score of 66/100. The biggest problem is an extremely slow Largest Contentful Paint of 13.4 seconds, primarily caused by render-blocking CSS files that could save 560ms and oversized images wasting 1,424 KiB of bandwidth. The site also suffers from excessive main-thread blocking (2.2 seconds) and unused JavaScript (89 KiB), resulting in a delayed Time to Interactive of 14 seconds. Optimizing image sizes, deferring CSS loading, and removing unused code could dramatically improve load times and user experience.
Other Optimization Recommendations
Eliminate Render-Blocking CSS
High Impact+15 points estimatedWhy It Matters:
CSS files block initial render for 560ms, significantly delaying First Contentful Paint.
How to Fix:
Move critical CSS inline in your Next.js _document.js file using styled-jsx or CSS-in-JS. Use Next.js dynamic imports with ssr: false for non-critical components. Add preload links for essential CSS chunks in your custom Head component.
Remove Unused JavaScript Code
Medium Impact+8 points estimatedWhy It Matters:
89 KiB of unused JavaScript increases bundle size and delays LCP by 600ms.
How to Fix:
Enable Next.js bundle analyzer to identify dead code in chunks like 844ce7817c4277af.js (55% unused). Use dynamic imports for large components that aren't immediately needed. Configure webpack to remove legacy JavaScript polyfills since you're targeting modern browsers.
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
371 KiB of unused JavaScript is blocking the main thread for 2.4 seconds and delaying interactivity by 18+ seconds.
Fix Lazy-Loading on LCP Image
The LCP image has lazy loading enabled, delaying critical content painting by 4.5 seconds and causing massive element render delay.
Remove Unused JavaScript Bundles
92KB of unused JavaScript is adding 750ms to LCP and blocking the main thread unnecessarily.
Optimize Large Hero Images
Three oversized images (1.4MB total) are severely impacting LCP by loading at 3840px width when only 665px is needed.