LCP
Largest Contentful Paint
5.3s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render Blocking CSS Files
How to optimize tamer.web.vercel.app
Next.js SiteScore: 73/100Analyzed January 2026
Eliminate Render Blocking CSS Files
High Impact+12 points estimated
Why It Matters
CSS files are blocking initial render for 750ms, significantly delaying both FCP and your 5.3s LCP.
How to Fix
Split the large 44KB CSS file (e7d0739c3c771678.css) into critical and non-critical styles. Inline critical CSS in the <head> and load non-critical styles asynchronously using next/dynamic or loadCSS. Configure Next.js to extract only above-the-fold styles for immediate rendering.
0Needs Improvement
What This Score Means
A score of 73 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
103ms
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/React website has poor performance with a score of 73/100, struggling with slow loading times that hurt user experience. The biggest problem is render-blocking CSS files that are delaying the page from displaying content, wasting 740ms and causing the Largest Contentful Paint to take a painfully slow 5.3 seconds. The site is also bloated with 207KB of unused JavaScript code that's not needed for the initial page load, further slowing down interactivity to 9.4 seconds. Deferring or inlining the CSS, removing unused JavaScript, and optimizing the build process to avoid unnecessary polyfills could dramatically improve performance and potentially boost the score by 20+ points.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+8 points estimatedWhy It Matters:
207KB of unused JavaScript is adding 150ms to LCP and blocking main thread execution.
How to Fix:
Use Next.js bundle analyzer (@next/bundle-analyzer) to identify unused code in chunks 8e9f1c067cec6a7e.js and 16c4ae1a778a6981.js. Implement dynamic imports for non-critical components using next/dynamic with ssr: false. Remove the nearly 100% unused chunk 51877078f99e0801.js by auditing your import statements.
Optimize Hero Image Loading
Medium Impact+3 points estimatedWhy It Matters:
The hero mascot image is 15KB larger than needed and could be impacting perceived load performance.
How to Fix:
Resize the heroTobbi.webp source image to match its display dimensions (257x385) instead of serving 640x960. Use Next.js Image component with priority={true} and sizes='257px' for the hero image. Consider using a placeholder or blur data URL while the image loads.
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.
Optimize Hero Image Delivery
Hero image is 50KB larger than needed and could improve perceived loading performance.
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