LCP
Largest Contentful Paint
19.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Third-Party Network Dependencies
How to optimize wz.kliniken.de
Optimize Third-Party Network Dependencies
Medium Impact+12 points estimated
Why It Matters
The lights-on.io widget creates a 1.35-second dependency chain that blocks critical rendering.
How to Fix
Add preconnect hints for kzvnz.lights-on.io in the HTML head section. Move the widget initialization to after page load using window.onload event. Consider self-hosting or replacing with a lighter consent management solution.
0Needs Improvement
What This Score Means
A score of 69 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
52ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.01
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This website has poor performance with a score of 69/100, primarily due to extremely slow loading times with the Largest Contentful Paint taking 19.5 seconds. The biggest issue is render-blocking resources that are delaying the initial page display by 1.35 seconds, particularly CSS and JavaScript files that prevent content from appearing quickly. The site is also loading large amounts of unused JavaScript (53 KiB) and CSS (54 KiB) that aren't needed for the initial page load, while oversized images are wasting an additional 109 KiB of bandwidth. Fixing these render-blocking resources and removing unused code could dramatically improve load times and boost the performance score by 25+ points.
Other Optimization Recommendations
Eliminate Render-Blocking Resources
High Impact+25 points estimatedWhy It Matters:
CSS and JavaScript files are blocking initial page render, delaying LCP by 1.35 seconds.
How to Fix:
Move the lights-on.io script to load asynchronously by adding 'async' or 'defer' attributes. Inline critical CSS for above-the-fold content directly in the HTML. Move non-critical CSS like swiper.min.css to load after page render using media='print' then switching to 'all' onload.
Remove Unused CSS and JavaScript
High Impact+20 points estimatedWhy It Matters:
Unused code accounts for 89% of CSS and 71% of JavaScript, wasting 108KB and delaying LCP by 600ms total.
How to Fix:
Audit the main.min.css file to remove unused Bootstrap and framework styles. Split the merged JavaScript file to load only required components per page. Use PurgeCSS or similar tools to eliminate dead code automatically.
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
Optimize Mobile Viewport Configuration
Unoptimized viewport causes 300ms tap delays, negatively affecting user interaction responsiveness.
Reduce Document Request Latency
First network request latency of 300ms delays both LCP and FCP, slowing initial page render.
Eliminate Multiple Page Redirects
The redirect chain delays LCP and FCP by 800ms, significantly impacting user experience.
Optimize Hero Image Delivery
The main hero image is oversized and poorly compressed, wasting 80KB and delaying LCP by 600ms.