LCP
Largest Contentful Paint
8.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize LCP Image Loading
How to optimize tokyoportfolio.frontend.stg.vercel.app
Optimize LCP Image Loading
High Impact+18 points estimated
Why It Matters
The LCP image has lazy loading applied and lacks priority hints, causing a 4.8 second resource load delay.
How to Fix
Remove loading='lazy' from the first carousel image and add fetchpriority='high'. Use Next.js Image component with priority={true} prop. Preload the LCP image in the document head using <link rel='preload' as='image'> for the first carousel slide.
0Poor
What This Score Means
A score of 23 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
381ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.90
Poor
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 23/100. The biggest problem is an extremely slow server response time of 2.7 seconds, which cascades into poor Core Web Vitals including a 14-second Time to Interactive and massive layout shifts (0.9 CLS score). The site is also loading 372 KB of unused JavaScript and has render-blocking CSS that delays initial page rendering. Fixing the server response time and removing unused code could improve the score by 40+ points and dramatically enhance user experience.
Other Optimization Recommendations
Fix Server Response Time
High Impact+25 points estimatedWhy It Matters:
Your server response takes 2.7 seconds, blocking all other page resources and severely delaying LCP by 2.6 seconds.
How to Fix:
Investigate the Next.js backend performance on Vercel - check for slow database queries, API calls, or server-side rendering issues. Enable Edge Runtime for faster cold starts. Consider implementing ISR (Incremental Static Regeneration) for this buy page if content allows.
Eliminate Layout Shifts from Images
High Impact+12 points estimatedWhy It Matters:
Unsized images cause a massive 0.90 CLS score, creating jarring visual instability as content loads.
How to Fix:
Add explicit width and height attributes to the Instagram icon and other footer images. Use Next.js Image component with proper dimensions for all carousel images. Set CSS aspect-ratio or min-height on image containers to reserve space before loading.
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 CSS and JavaScript
326KB of unused JavaScript and 19KB of unused CSS are blocking render and increasing load times unnecessarily.
Eliminate Layout Shifts from Footer
A massive layout shift (0.808 CLS score) occurs when the footer loads, severely impacting user experience.
Remove Unused CSS Rules
87% of your main CSS bundle (18KB) is unused, wasting bandwidth and parse time.
Fix JavaScript Forced Reflows
JavaScript is causing 149ms of forced reflows by reading layout properties after DOM changes, blocking the main thread.