LCP
Largest Contentful Paint
5.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused CSS and JavaScript
How to optimize tokyoportfolio.frontend.stg.vercel.app
Remove Unused CSS and JavaScript
Medium Impact+12 points estimated
Why It Matters
326KB of unused JavaScript and 19KB of unused CSS are blocking render and increasing load times unnecessarily.
How to Fix
Audit your Next.js bundle using @next/bundle-analyzer to identify unused code. Remove or lazy-load Google Tag Manager and Facebook Pixel if not critical. Use dynamic imports for components not needed immediately. Enable tree-shaking by ensuring proper ES6 imports.
0Poor
What This Score Means
A score of 31 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
441ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.81
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 score of only 31/100. The biggest problem is an extremely slow server response time of 4 seconds, which dramatically delays both First Contentful Paint (3.5s) and Largest Contentful Paint (5.5s). Additionally, the site suffers from massive layout shifts (0.808 CLS score) caused by the footer element moving during page load, and over 300KB of unused JavaScript from tracking scripts. Fixing the server response time alone could save nearly 4 seconds of load time and dramatically improve the user experience.
Other Optimization Recommendations
Fix Server Response Time
High Impact+25 points estimatedWhy It Matters:
The initial server response takes 4.06 seconds, delaying all other page resources and causing massive LCP/FCP delays.
How to Fix:
Investigate your Vercel deployment for performance bottlenecks. Check if API routes or data fetching in getServerSideProps/getStaticProps are causing delays. Consider moving to getStaticProps with ISR for better performance, or optimize database queries and external API calls.
Eliminate Layout Shifts from Footer
High Impact+20 points estimatedWhy It Matters:
A massive layout shift (0.808 CLS score) occurs when the footer loads, severely impacting user experience.
How to Fix:
Reserve space for the footer during initial render by setting a min-height in CSS. Check if dynamic content or images in the footer are loading without dimensions. Use Next.js Image component with explicit width/height for footer images.
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
Reduce Unused CSS and JavaScript
You're loading 287KB of unused JavaScript and 19KB of unused CSS, blocking rendering and slowing page load.
Fix Cumulative Layout Shift
Your CLS score of 0.806 is extremely poor (needs <0.1) with the footer element causing massive layout shifts.
Optimize Third-Party JavaScript
Google Analytics and Facebook Pixel scripts consume 213KB of unused JavaScript and cause 57ms of forced reflows.
Eliminate CSS Render Blocking
CSS files are blocking initial page render for 870ms and delaying First Contentful Paint by 850ms.