Get notified when this page gets slower
Register for free – monitoring, alerts and more.
The website has several clear performance bottlenecks that noticeably slow down page rendering. Server and loading speed is the biggest problem here.
Google PageSpeed · Mobile 45 · Desktop 82
These values come from the real page build in the browser and show the differences between desktop and mobile.
| Metric | Desktop (1440 px) | Mobile (390 px) |
|---|---|---|
| Requests | 139 | 139 |
| FCP i | 1680 ms | 1836 ms |
| LCP i | 2560 ms | 4296 ms |
| CLS i | 0.035 | 0.15 |
| TBT i | 111 ms 6 long tasks | 258 ms 7 long tasks |
LCP mobile: 4296 ms · desktop: 2560 ms.
Synthetic measurement from Google Lighthouse — measured independently of the turbometrics score.
Google rates this page as slow — action needed. · Fetched on 23 Aug 2026 8:08 PM
Largest Contentful Paint approx. 4296 ms
Server response approx. 1192 ms
Largest Contentful Paint approx. 4296 ms
No long-lived cache rules detected
The Largest Contentful Paint is around 4296 ms.
Recommendation: Optimise the hero image, CSS, server response and JavaScript load.
32 JavaScript files are loaded synchronously and block page rendering.
Recommendation: Load scripts with an async or defer attribute wherever possible.
The browser issued 139 requests.
Recommendation: Above all, reduce or bundle tracking, builder assets, fonts and additional external services.
The HTML directly references 33 CSS files and 42 external JavaScript files.
Recommendation: Reduce unnecessary assets and review the theme and plugin load.
HTML, CSS and the images loaded with the page add up to 75 distinct images.
Recommendation: Optimise images, use lazy loading and remove unnecessary media.
Mobile · Image
The largest visible content appears to be an image and can directly affect the page build.
Actually loaded in the browser.
Top hosts by data volume
Largest requests
Total: 2.465,2 KB
Total: 2.391,0 KB
42 JavaScript files adding up to around 124.25 KB. Reduce unnecessary scripts, tracking and plugin front-end load, defer them or load them only when needed.
The real page load triggers 139 individual requests. Reduce unnecessary lazy loads, third parties and extra front-end files first.
The LCP value is around 4296 ms. Check the hero image, critical CSS, server response and early JavaScript load first.
www.gstatic.com causes around 312.44 KB across 3 requests.
Recommendation: Reduce, bundle or defer third-party load.
The mobile LCP is around 1736 ms above the desktop value.
Recommendation: Check the mobile page load, image sizes, CSS and third parties separately.
The First Contentful Paint is around 1836 ms.
Recommendation: Check early render blockers, server response and critical assets.
recaptcha__en.js – 312.44 KB
File: recaptcha__en.js · Host: www.gstatic.com
https://www.gstatic.com/recaptcha/releases/xg_pWYS8-HRESiV6Rdg4aY_R/recaptcha__en.js
diegutachter.gmbh
Mobile 2.246,4 KB · Desktop 2.172,2 KB · Difference +74,2 KB
o.clarity.ms
These short texts put the most important measurements into plain language.
The server response has room for improvement and already delays page rendering noticeably.
Why it matters: TTFB stands for “time to first byte” — the time until the server returns the first data.
Technical value: 1192 ms
The page is served compressed, so less data has to be transferred.
Why it matters: Compression reduces the transfer size of HTML, CSS and JavaScript.
Technical value: Content-Encoding: gzip
No clear long-lived cache rules were detected.
Why it matters: Browser caching prevents unchanged files from being downloaded over and over again.
Technical value: CSS: 0/10, JS: 0/15, images: 0/15, fonts: unknown | page cache: no, CDN: none detected, origin: Apache | HTML Cache-Control: empty (normal for dynamic pages)
75 images were detected. Of those, 15 use lazy loading and 53 use modern formats such as WebP or AVIF.
Why it matters: Images are often the biggest performance factor. Lazy loading and modern formats help the most.
Technical value: WEBP: 5, JPG: 2, PNG: 3, SVG: 5 (15 of 75 measured), measured image weight: 1.15 MB
42 external JavaScript files were detected in the delivered HTML. Further scripts may only be loaded during the real page load through optimisation or lazy-load mechanisms.
Why it matters: Many or large JavaScript files can delay a page’s rendering and interactivity.
Technical value: 42 external files, 0 data URI scripts, 124.25 KB
50 font files were detected. In addition, 0 external font services (e.g. Google Fonts) are embedded.
Why it matters: Many or large web fonts increase loading time and can cause visible layout delays.
Technical value: 50 font files, 0 external font services, groups: no grouped fonts detected, measured font weight: 0 B
33 direct CSS files and 10 additional CSS dependencies were detected.
Why it matters: Many stylesheets or imported CSS files increase the number of loaded resources.
Technical value: Direct CSS files: 33, additional dependencies: 10, estimated CSS weight: 124.76 KB
The page loads content from 3 external hosts.
Why it matters: Every additional external domain increases dependencies and can affect loading time.
Technical value: no categories detected — www.google.com, www.googletagmanager.com, cdn.elementor.com
The first visible content appears after around 1836 ms, the most important visible content after around 4296 ms. Visible page rendering is noticeably delayed.
Why it matters: These values describe when users actually see the first and the most important content.
Technical value: FCP: 1836 ms, LCP: 4296 ms
Visible shifts occur while loading. The measured CLS value is 0.15.
Why it matters: CLS describes whether content shifts visibly while loading.
Technical value: CLS: 0.15
The real page load issues very many requests and a noticeable amount of data: 139 requests with around 2.59 MB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 139 requests, 2.59 MB
These services were actually contacted during the real page build in the browser.
3 requests · 312,4 KB
www.gstatic.com
4 requests · 94,2 KB
www.google.com
4 requests · 0,0 KB
www.googletagmanager.com
5 requests · 0,0 KB
www.clarity.ms, scripts.clarity.ms, c.clarity.ms, o.clarity.ms
These hosts were detected directly in HTML or CSS. Not every one of them was necessarily loaded during the real page build.
This list shows the largest requests from the real browser run and helps you spot notable files and hosts faster.
Tasks that blocked the browser main thread.
In-depth values for assets, images, fonts, CSS and JavaScript. The most important groups are grouped thematically below.
This list shows the largest measured files from the asset check.
This number shows detected hints in the HTML. It is not perfect proof that all images actually use lazy loading.
Sample: 15 of 75 images were loaded and measured. Size and count refer only to these images.
Detected font files: 50, External font services: 0. External font services are e.g. Google Fonts or Adobe Typekit, from which concrete font files are only loaded later.
Only the first 40 entries are shown.
These are stylesheets referenced within other CSS files via @import references.
These are the external script sources detected in the directly delivered HTML. Dynamically loaded scripts are not fully included.
Only the first 40 entries are shown.
These points are not critical, but can improve the performance, stability or clarity of the page structure.
The CLS value is 0.15.
Recommendation: Check image dimensions, reserved space, fonts and dynamically injected elements.
The browser main thread was blocked for around 258 ms during page load (Total Blocking Time).
Recommendation: Reduce JavaScript load, defer heavy scripts and break up long tasks.
The page contains 1650 DOM elements. Beyond roughly 1500 elements the browser slows down noticeably.
Recommendation: Reduce unnecessary wrapper elements and review the page builder output.
The real page load contacted 11 external hosts.
Recommendation: Reduce or bundle external scripts and third-party connections.
The server response takes around 1192 ms.
Recommendation: Check caching and backend performance.
No clear long-lived cache headers were detected for static resources.
Recommendation: Set Cache-Control headers for static files properly.
40 first-party assets have no clear long-lived cache rules.
Recommendation: Serve static files with long-lived Cache-Control values.
Detected 50 font files totalling around 0 B.
Recommendation: Load fewer font weights and serve fonts as efficiently as possible.
The website does not support HTTP/2.
Recommendation: Enable HTTP/2 at the hosting provider or web server.
These points already stood out positively in the current scan.
Detected compression: gzip.
41 @font-face rules with font-display detected.
Preconnect: 0, DNS prefetch: 3, prefetch: 0.
The website is reachable over HTTPS.
Supplementary hints from the scan that can be useful for classification and technical assessment.
CSS pulls in 10 further stylesheet dependencies.
CSS references 50 additional font files.
The page uses WordPress, likely with elementor.
Detected theme: hello-elementor.
Detected indicators: elementor, wp-rocket, yoast-seo, gravityforms.
The website is only reachable over IPv4.
Detailed request waterfall from the browser run.
Complete scan data as a machine-readable JSON file or tabular export.
More export formats & API access
PDF, Excel, CSV and full API access are available on paid plans.
Scan your website and get an AI analysis with concrete measures – free with an account.
Register for free →