LCP
Largest Contentful Paint
6.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Hero Video Loading
How to optimize claude.com
Optimize Hero Video Loading
High Impact+15 points estimated
Why It Matters
The 3.8MB hero video dominates network payload and significantly impacts LCP timing.
How to Fix
Compress the cowork-login-hero.mp4 using modern codecs (H.265 or AV1) to reduce size by 50-70%. Implement lazy loading for the video element and use a lightweight poster image for initial render. Consider replacing with an optimized hero image on mobile devices.
0Needs Improvement
What This Score Means
A score of 76 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
123ms
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 below-average performance with a score of 76/100, but faces significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 6.8 seconds, likely caused by a large 3.8MB video file that dominates the page load. The site is also bloated with unused CSS (24KB savings available) and unused JavaScript (43KB savings available), which are common issues with React applications that don't properly optimize their bundles. Compressing or replacing the hero video, removing unused code, and implementing better caching could dramatically improve load times and boost the performance score by 15-20 points.
Other Optimization Recommendations
Remove Unused CSS and JavaScript
High Impact+12 points estimatedWhy It Matters:
67KB of unused code is delaying LCP by 300ms and blocking critical rendering path.
How to Fix:
Use Next.js built-in bundle analyzer to identify unused chunks. Implement dynamic imports for non-critical components using React.lazy(). Configure webpack to enable tree-shaking in next.config.js and remove unused CSS rules from your stylesheets.
Fix Forced Reflows
Medium Impact+8 points estimatedWhy It Matters:
84ms of forced reflows are causing layout thrashing and blocking user interactions.
How to Fix:
Batch DOM reads and writes to avoid layout thrashing. Use React's useLayoutEffect instead of useEffect for DOM measurements. Cache geometric property values and avoid reading offsetWidth/offsetHeight in render loops.
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
Fix Forced Reflows
84ms of forced reflows are causing layout thrashing and blocking user interactions.
Remove Unused CSS and JavaScript
67KB of unused code is delaying LCP by 300ms and blocking critical rendering path.
Reduce Main Thread Blocking Time
806ms of Total Blocking Time prevents user interactions and degrades page responsiveness.
Optimize Font Loading Strategy
Font blocking is causing 530ms delay to First Contentful Paint with invisible text periods.