Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize kontextplan.ch
Images waste 1,119 KiB and delay LCP by 1.95 seconds, significantly impacting page load performance.
Convert all JPEG/PNG images to WebP format using tools like Squoosh or ImageOptim for 60-80% size reduction. Implement proper responsive images with correct dimensions - your main image is served at 683x887 but displayed at 340x510. Use picture elements with WebP fallbacks for older browsers. Enable browser caching for images with long cache headers.
A score of 25 falls in the "Poor" 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This website has severe performance problems with a critically low score of 25/100. The biggest issue is massively oversized and unoptimized images that are wasting over 1,100 KiB of data and causing the Largest Contentful Paint to take a devastating 15.2 seconds - images are being served at twice their display size and in outdated formats instead of modern WebP/AVIF. Additionally, the site loads 565 KiB of unused JavaScript (including a heavy Spline 3D viewer) and has zero cache lifetimes on images, meaning returning visitors get no performance benefit. Fixing image optimization alone could improve load times by nearly 2 seconds and dramatically boost the user experience.
Why It Matters:
578 KiB of unused JavaScript blocks rendering for 3.15 seconds and creates massive main thread work.
How to Fix:
Remove or lazy-load the Spline 3D viewer (382 KiB unused) if not critical above-the-fold. Split your app.js bundle and load only essential code initially. Move Google Analytics to load after page interaction using partytown or similar worker-based solution. Implement code splitting to reduce initial bundle size.
Why It Matters:
LCP element isn't discoverable in HTML and missing preconnect hints delay critical resource loading.
How to Fix:
Add fetchpriority='high' to your LCP image element and ensure it's not lazy-loaded. Add preconnect hints to critical origins: <link rel='preconnect' href='https://prod.spline.design'>. Make your hero background image discoverable in initial HTML rather than loaded via JavaScript. Consider inlining critical CSS to reduce render-blocking time.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Optimizing cache headers ensures consistently fast repeat visits and maintains your excellent performance score.
With a perfect performance score, preloading key resources can further optimize LCP for varying network conditions.
Current viewport configuration causes 300ms tap delays on mobile interactions, directly impacting INP scores.
Images without width/height attributes cause layout shifts and poor user experience as they load.
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.