LCP
Largest Contentful Paint
4.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render-Blocking CSS Resources
How to optimize tamer.web.vercel.app
Next.js SiteScore: 77/100Analyzed January 2026
Eliminate Render-Blocking CSS Resources
High Impact+12 points estimated
Why It Matters
Three CSS files are blocking initial page render and delaying LCP by 750ms.
How to Fix
Move critical CSS inline in your Next.js _document.js file. Use next/dynamic with ssr: false for non-critical styles. Configure next.config.js to defer loading of large CSS chunks like e162dfc33f8ffb0e.css using experimental.optimizeCss option.
0Needs Improvement
What This Score Means
A score of 77 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
72ms
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 moderate performance issues with a score of 77/100. The biggest problem is render-blocking CSS files that are delaying your page's initial display by 750ms, directly impacting both First Contentful Paint and Largest Contentful Paint metrics. Your site is also carrying significant unused JavaScript (227 KiB) and taking too long to become fully interactive (8.4 seconds), which hurts user experience. Deferring or inlining the CSS, removing unused JavaScript code, and optimizing your JavaScript bundles could improve your score by 15-20 points and make your site feel much more responsive to users.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+8 points estimatedWhy It Matters:
233KB of unused JavaScript is delaying LCP by 450ms and wasting bandwidth.
How to Fix:
Enable Next.js tree shaking by using ES6 imports and removing unused dependencies. Configure webpack-bundle-analyzer to identify dead code in chunks 8e9f1c067cec6a7e.js and 16c4ae1a778a6981.js. Use dynamic imports with next/dynamic for components not needed on initial load.
Optimize Hero Image Delivery
Medium Impact+3 points estimatedWhy It Matters:
Hero image is 50KB larger than needed and could improve perceived loading performance.
How to Fix:
Use Next.js Image component's responsive sizing by setting proper sizes prop for the hero image. Configure next.config.js with custom device sizes matching your breakpoints. Add priority={true} to the hero image to preload it and improve LCP.
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
Optimize Image Responsive Sizing
Images are served at larger dimensions than displayed, wasting 39 KiB of bandwidth and slowing perceived load time.
Reduce Unused JavaScript Bundle
238 KiB of unused JavaScript is delaying LCP by 450ms and blocking main thread execution.
Optimize Hero Image Loading
The hero mascot image is 15KB larger than needed and could be impacting perceived load performance.
Eliminate Render Blocking CSS Files
CSS files are blocking initial render for 750ms, significantly delaying both FCP and your 5.3s LCP.
Frequently Asked Questions
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