LCP
Largest Contentful Paint
14.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render-Blocking CSS
How to optimize filizkozmetik.net
Eliminate Render-Blocking CSS
High Impact+20 points estimated
Why It Matters
Critical CSS is blocking first paint by 150ms and delaying both LCP and FCP metrics.
How to Fix
Extract above-the-fold CSS and inline it in the document head. Use Next.js dynamic imports for non-critical components. Move the 1352fe111a6f7cf0.css file to load asynchronously or split into critical and non-critical parts using next/dynamic.
0Needs Improvement
What This Score Means
A score of 67 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
79ms
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 poor performance with a score of 67/100, struggling significantly with Core Web Vitals. The biggest problem is massive, unoptimized images that are causing extremely slow loading times - your Largest Contentful Paint takes a concerning 14.4 seconds, and images alone could be reduced by over 16MB. The site is serving high-resolution images (5000x3368 pixels) for much smaller display areas, while also suffering from render-blocking CSS and excessive unused JavaScript from Google Analytics and React components. Implementing responsive images, compressing existing images, and removing unused code could dramatically improve your score by 30+ points and provide a much better user experience.
Other Optimization Recommendations
Optimize Image Sizes and Delivery
High Impact+25 points estimatedWhy It Matters:
Oversized images are causing a 3.5 second LCP delay and consuming 16MB of unnecessary bandwidth.
How to Fix:
Implement Next.js Image component with responsive sizes for washing-unit.jpg, salon-station.jpg, and barber-chair.jpg. Resize source images to match display dimensions (665x665px max). Use next/image with WebP format and proper srcSet for different screen sizes.
Remove Unused JavaScript Code
Medium Impact+12 points estimatedWhy It Matters:
138KB of unused JavaScript is delaying LCP by 600ms and slowing page interactivity.
How to Fix:
Remove unused Google Analytics features and configure minimal gtag.js setup. Use Next.js bundle analyzer to identify unused code in 4623-d5b40daffdc786e2.js and 273-557a4403745460dd.js. Implement code splitting for GSAP animations and load them only when needed using dynamic imports.
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
Remove Unused JavaScript Code
138KB of unused JavaScript is delaying LCP by 600ms and slowing page interactivity.
Optimize Image Sizes and Delivery
Oversized images are causing a 3.5 second LCP delay and consuming 16MB of unnecessary bandwidth.
Preload Critical Font Resources
Font loading dependency chains create 833ms delays that could impact text rendering and LCP timing.
Eliminate Forced Reflow Operations
41ms of forced reflow time is causing layout thrashing and degrading rendering performance.