Get notified when this page gets slower
Register for free – monitoring, alerts and more.
The website is fundamentally solid. Some clear bottlenecks should be fixed. Loading speed in particular offers room for improvement.
Google PageSpeed · Mobile 70 · Desktop 95
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 | 92 | 83 |
| FCP i | 496 ms | 464 ms |
| LCP i | 716 ms | 612 ms |
| CLS i | 0 | 0.01 |
| TBT i | 132 ms 5 long tasks | 141 ms 4 long tasks |
Synthetic measurement from Google Lighthouse — measured independently of the turbometrics score.
Google sees optimisation potential for this page. · Fetched on 4 Oct 2026 5:55 PM
46 detected in the HTML
51 scripts without async/defer
The HTML directly references 4 CSS files and 46 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 69 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: 1.204,5 KB
Total: 1.880,1 KB
46 JavaScript files adding up to around 29.42 KB. Reduce unnecessary scripts, tracking and plugin front-end load, defer them or load them only when needed.
69 images adding up to around 1.39 MB. Large images, missing modern formats and missing lazy loading are a good lever here.
The real page load triggers 83 individual requests. Reduce unnecessary lazy loads, third parties and extra front-end files first.
The page contains 4235 DOM elements. Beyond roughly 1500 elements the browser slows down noticeably.
Recommendation: Reduce unnecessary wrapper elements and review the page builder output.
51 JavaScript files are loaded synchronously and block page rendering.
Recommendation: Load scripts with an async or defer attribute wherever possible.
The browser issued 83 requests.
Recommendation: Above all, reduce or bundle tracking, builder assets, fonts and additional external services.
83 requests during page load
hero-person-zk-2560x1173.webp – 230.23 KB
File: hero-person-zk-2560x1173.webp · Host: dev.sprecher-pascal.de
https://dev.sprecher-pascal.de/lib/3f2f19ac/assets/img/hero-person-zk-2560x1173.webp
These short texts put the most important measurements into plain language.
The server responds quickly.
Why it matters: TTFB stands for “time to first byte” — the time until the server returns the first data.
Technical value: 162 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: br (Brotli)
The browser is allowed to cache files, which can make repeat visits faster.
Why it matters: Browser caching prevents unchanged files from being downloaded over and over again.
Technical value: CSS: 4/4, JS: 15/15, images: 15/15, fonts: 6/6 | page cache: no, CDN: none detected, origin: Apache | HTML Cache-Control: no-cache, must-revalidate, max-age=0
69 images were detected. Of those, 36 use lazy loading and 59 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: 11, SVG: 4 (15 of 69 measured), measured image weight: 1.39 MB
46 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: 46 external files, 0 data URI scripts, 29.42 KB
6 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: 6 font files, 0 external font services, groups: rubik-v31-latin (3), rajdhani-v17-latin (2), teko-latin-variable (1), measured font weight: 101.44 KB
4 direct CSS files and 4 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: 4, additional dependencies: 4, estimated CSS weight: 524.70 KB
No external services were detected – good for loading time and privacy.
Why it matters: Every additional external domain increases dependencies and can affect loading time.
Technical value: 0 external hosts
The first visible content appears after around 464 ms, the most important visible content after around 612 ms. That is a good result.
Why it matters: These values describe when users actually see the first and the most important content.
Technical value: FCP: 464 ms, LCP: 612 ms
Layout stability is good. The measured CLS value is 0.01.
Why it matters: CLS describes whether content shifts visibly while loading.
Technical value: CLS: 0.01
The real page load issues relatively many requests: 83 requests with around 1.20 MB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 83 requests, 1.20 MB
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.
Only the first 20 entries are shown.
These are image files that are not referenced directly in the HTML, but in CSS via url(...) references.
Sample: 15 of 69 images were loaded and measured. Size and count refer only to these images.
Detected font files: 6, External font services: 0. External font services are e.g. Google Fonts or Adobe Typekit, from which concrete font files are only loaded later.
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 inspected images add up to around 1.39 MB.
Recommendation: Resize and compress images and use modern formats.
Detected 6 font files totalling around 101.44 KB.
Recommendation: Load fewer font weights and serve fonts as efficiently as possible.
These points already stood out positively in the current scan.
The Total Blocking Time is around 141 ms.
The server response takes around 162 ms.
Detected compression: br.
6 @font-face rules with font-display detected.
No fonts were requested from Google servers while loading the page.
The website is reachable over HTTPS.
The website is served over HTTP/2.
Supplementary hints from the scan that can be useful for classification and technical assessment.
CSS pulls in 4 further stylesheet dependencies.
CSS references 6 additional font files.
No clear WordPress indicators were found in the HTML or the asset paths.
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 →