Get notified when this page gets slower
Register for free – monitoring, alerts and more.
The website has avoidable performance bottlenecks. Server and loading speed is the biggest problem here.
Google PageSpeed · Mobile 47 · Desktop 81
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 | 220 | – |
| FCP i | 888 ms | – |
| LCP i | 3056 ms | – |
| CLS i | 0.015 | – |
| TBT i | 704 ms 12 long tasks | – |
Synthetic measurement from Google Lighthouse — measured independently of the turbometrics score.
Google rates this page as slow — action needed. · Fetched on 23 Sep 2026 12:13 AM
Total Blocking Time approx. 704 ms
60 JavaScript files are loaded synchronously and block page rendering.
Recommendation: Load scripts with an async or defer attribute wherever possible.
The browser issued 220 requests.
Recommendation: Above all, reduce or bundle tracking, builder assets, fonts and additional external services.
The HTML directly references 103 CSS files and 64 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 60 distinct images.
Recommendation: Optimise images, use lazy loading and remove unnecessary media.
Desktop · Text / CSS block
The largest visible content appears to be text- or CSS-based and is more likely influenced by server response, CSS or fonts.
No direct image asset was detected for this LCP element. The visible main content here is probably text- or CSS-based.
Actually loaded in the browser.
Top hosts by data volume
No data.
Largest requests
No data.
Total: 2.108,2 KB
64 JavaScript files adding up to around 229.13 KB. Reduce unnecessary scripts, tracking and plugin front-end load, defer them or load them only when needed.
The real page load triggers 220 individual requests. Reduce unnecessary lazy loads, third parties and extra front-end files first.
60 images adding up to around 1.61 MB. Large images, missing modern formats and missing lazy loading are a good lever here.
No direct image asset was detected for the LCP element. The delay here is more likely caused by the server response, CSS or fonts.
Recommendation: Check TTFB, critical CSS, web fonts and the above-the-fold structure separately.
The Largest Contentful Paint is around 3056 ms.
Recommendation: Optimise the hero image, CSS, server response and JavaScript load.
The browser main thread was blocked for around 704 ms during page load (Total Blocking Time).
Recommendation: Reduce JavaScript load, defer heavy scripts and break up long tasks.
No direct image asset detected. LCP is likely driven by TTFB, CSS or fonts here.
Largest Contentful Paint approx. 3056 ms
01_Vollblut_Agetur_alles_fliesst.jpg – 202.99 KB
File: 01_Vollblut_Agetur_alles_fliesst.jpg · Host: vollblut-agentur.de
https://vollblut-agentur.de/wp-content/uploads/revslider/slider-1/01_Vollblut_Agetur_alles_fliesst.jpg
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: 426 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: 10/10, JS: 15/15, images: 0/15, fonts: unknown | page cache: no, CDN: none detected, origin: LiteSpeed | HTML Cache-Control: empty (normal for dynamic pages)
60 images were detected. Of those, 27 use lazy loading and 13 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: 8, PNG: 7 (15 of 60 measured), measured image weight: 1.61 MB
64 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: 64 external files, 0 data URI scripts, 229.13 KB
38 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: 38 font files, 0 external font services, groups: no grouped fonts detected, measured font weight: 0 B
103 direct CSS files and 11 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: 103, additional dependencies: 11, estimated CSS weight: 1.51 MB
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 888 ms, the most important visible content after around 3056 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: 888 ms, LCP: 3056 ms
Layout stability is good. The measured CLS value is 0.015.
Why it matters: CLS describes whether content shifts visibly while loading.
Technical value: CLS: 0.015
The real page load issues very many requests and a noticeable amount of data: 220 requests with around 1.90 MB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 220 requests, 1.90 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 60 images were loaded and measured. Size and count refer only to these images.
Detected font files: 38, 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 page contains 1564 DOM elements. Beyond roughly 1500 elements the browser slows down noticeably.
Recommendation: Reduce unnecessary wrapper elements and review the page builder output.
15 first-party assets have no clear long-lived cache rules.
Recommendation: Serve static files with long-lived Cache-Control values.
The inspected images add up to around 1.61 MB.
Recommendation: Resize and compress images and use modern formats.
Detected 38 font files totalling around 0 B.
Recommendation: Load fewer font weights and serve fonts as efficiently as possible.
26 @font-face rules without font-display detected. Without font-display, text can stay invisible while loading (FOIT).
Recommendation: Add font-display: swap or optional to the @font-face rules.
Title: yes, H1: no, Viewport: yes.
Recommendation: Complete the basic HTML and SEO information.
These points already stood out positively in the current scan.
The server response takes around 426 ms.
Detected compression: br.
Preconnect: 2, DNS prefetch: 0, prefetch: 0.
The website is reachable over HTTPS.
The website is served over HTTP/2.
The website advertises HTTP/3 via the Alt-Svc header.
The website is reachable over IPv6.
Supplementary hints from the scan that can be useful for classification and technical assessment.
CSS pulls in 11 further stylesheet dependencies.
CSS references 38 additional font files.
The page uses WordPress, likely with gutenberg.
Detected theme: Avada.
Detected indicators: contact-form-7, yoast-seo, revslider.
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 →