LCP
Largest Contentful Paint
27.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Hero Image Delivery
How to optimize wz.kliniken.de
Optimize Hero Image Delivery
High Impact+15 points estimated
Why It Matters
The main hero image is oversized and poorly compressed, wasting 80KB and delaying LCP by 600ms.
How to Fix
Compress the hero image using tools like TinyPNG to reduce file size by 65KB. Resize the image from 575x344 to match its displayed dimensions of 412x246. Convert to WebP format for additional 20-30% savings. Add fetchpriority='high' to prioritize this LCP element.
0Needs Improvement
What This Score Means
A score of 62 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
107ms
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 hospital website has poor performance with a score of 62/100, indicating significant issues that are hurting user experience. The biggest problem is render-blocking resources, particularly CSS and JavaScript files that are preventing the page from displaying content quickly - this alone is delaying your First Contentful Paint and Largest Contentful Paint by over 1.5 seconds. The site is also loading 88% unused CSS code and has unoptimized images that could be compressed by 80KB, while the overall page size of 8.4MB is excessive for a typical website. Addressing these render-blocking resources, cleaning up unused code, and optimizing images could easily improve your performance score by 30+ points and dramatically reduce the current 27-second load time.
Other Optimization Recommendations
Eliminate Render Blocking Resources
High Impact+25 points estimatedWhy It Matters:
Critical CSS and JavaScript files are blocking page rendering, delaying both FCP and LCP by 1,550ms.
How to Fix:
Inline critical above-the-fold CSS directly in the HTML head. Defer the main.min.css file using media='print' onload='this.media="all"'. Move non-critical JavaScript files to load asynchronously with async or defer attributes. Consider splitting the 62KB main.css file into critical and non-critical portions.
Remove Unused CSS and JavaScript
Medium Impact+10 points estimatedWhy It Matters:
88% of your main CSS file and 68% of your JavaScript bundle are unused, wasting 105KB of bandwidth.
How to Fix:
Use tools like PurgeCSS to remove unused CSS rules from main.min.css. Split the merged JavaScript bundle and load only required modules per page. Implement code splitting to defer loading of widget and third-party scripts until needed. Consider tree-shaking to eliminate dead code paths.
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 Third-Party Network Dependencies
The lights-on.io widget creates a 1.35-second dependency chain that blocks critical rendering.