LCP
Largest Contentful Paint
3.4s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Heavy Video Assets
How to optimize fix.up.2.look.sharp.barbers.2.vercel.app
Optimize Heavy Video Assets
Medium Impact+8 points estimated
Why It Matters
3MB of video content dominates your payload and creates caching issues, slowing repeat visits significantly.
How to Fix
Implement proper caching headers for your Webflow CDN videos (set max-age=31536000). Consider using Mux or similar service to serve adaptive bitrate videos. Add proper video compression and consider poster images with lazy loading for videos below the fold.
0Needs Improvement
What This Score Means
A score of 51 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
415ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.92
Poor
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js barbershop website has poor performance with a score of 51/100. The biggest problem is a massive layout shift (0.92 score) caused by web fonts loading late, which makes the entire hero section jump around as the page loads and severely hurts user experience. The site is also weighed down by nearly 5MB of video files that aren't being cached properly, plus 404KB of unused JavaScript from the Mux video player that's only 43% utilized. Fixing the font loading strategy to prevent layout shifts and implementing proper caching for the video content could dramatically improve both the visual stability and loading speed of the site.
Other Optimization Recommendations
Fix Layout Shifts from Web Fonts
High Impact+25 points estimatedWhy It Matters:
Web font loading causes a massive CLS score of 0.918, severely impacting user experience as content jumps during page load.
How to Fix:
Add font-display: swap to your Google Fonts URL and preload critical fonts in your Next.js _document.js. Use CSS size-adjust or fallback fonts that match your web font metrics. Reserve space for text content with proper line-height and font-size before fonts load.
Eliminate Render Blocking Fonts
High Impact+18 points estimatedWhy It Matters:
Google Fonts are blocking initial render for 950ms, directly delaying both LCP and FCP by nearly a second.
How to Fix:
Move Google Fonts import from CSS to Next.js font optimization using next/font/google. This automatically handles font loading, preloading, and eliminates render blocking. Alternatively, self-host fonts and preload them in _document.js with rel='preload'.
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
Add Preconnect Headers for External Origins
Missing preconnect hints to CMS and Cookiebot domains waste 300ms each on connection setup.
Fix Cookie Dialog Element Render
Cookie dialog causes 5.2 second element render delay, making it the LCP element instead of actual content.
Add Preconnect to External Origins
Missing preconnect to cms.koditt.dev delays LCP by 323ms due to late connection establishment.
Eliminate Unused JavaScript Bundle
455 KiB of unused JavaScript delays LCP by 450ms and blocks main thread execution.