LCP
Largest Contentful Paint
4.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Implement Efficient Cache Headers
How to optimize osmanordu.dev
Implement Efficient Cache Headers
High Impact+12 points estimated
Why It Matters
Missing cache headers force re-downloading of 257KB assets on every visit, delaying LCP by 900ms.
How to Fix
Configure your web server to set cache-control headers for static assets. Set CSS/JS files to cache for 1 year with 'Cache-Control: max-age=31536000'. Add versioning to filenames for cache busting. Configure background image to cache for 30 days minimum.
0Needs Improvement
What This Score Means
A score of 80 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
119ms
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 website has decent performance with a score of 80/100, but there are significant opportunities for improvement. The biggest issue is slow loading of the main content, with Largest Contentful Paint taking 4.6 seconds due to render-blocking resources like CSS and JavaScript files that prevent the page from displaying quickly. The site is also missing proper caching (could save 257 KiB) and has 60 KiB of unused JavaScript from Google Analytics that's slowing things down. Fixing these caching issues and deferring non-critical resources could easily push the performance score into the 90s and make the site feel much faster for users.
Other Optimization Recommendations
Eliminate Render Blocking Resources
High Impact+10 points estimatedWhy It Matters:
CSS and fonts block initial render, delaying both LCP and FCP by 350ms each.
How to Fix:
Inline critical CSS directly in the HTML head section. Load Google Fonts using font-display: swap and preload key font files. Move EmailJS script to load after page interactive or use async/defer attributes. Consider self-hosting fonts to reduce external requests.
Remove Unused JavaScript Code
Medium Impact+8 points estimatedWhy It Matters:
60KB of unused JavaScript from Google Analytics delays LCP by 750ms and wastes bandwidth.
How to Fix:
Switch to Google Analytics 4 gtag implementation with minimal tracking code. Use Google Tag Manager's built-in triggers to load analytics only after user interaction. Consider lightweight alternatives like Plausible or Simple Analytics for better performance.
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 Generic Speed Tests
Generic Performance Resources
Remove Unused JavaScript Code
60KB of unused JavaScript from Google Analytics delays LCP by 750ms and wastes bandwidth.
Eliminate Render Blocking Resources
CSS and fonts block initial render, delaying both LCP and FCP by 350ms each.
Optimize Image Delivery Performance
Poor image optimization wastes 108KB bandwidth and delays LCP by 150ms.
Remove Unused JavaScript Code
96KB of unused JavaScript delays LCP by 450ms and blocks page interactivity.