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.
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 | 515 | 74 |
| FCP i | 1196 ms | 636 ms |
| LCP i | 1492 ms | 1752 ms |
| CLS i | 0.076 | 0.19 |
| TBT i | 3808 ms 31 long tasks | 69 ms 1 long tasks |
30 detected in the HTML
26 scripts without async/defer
No H1 detected
The HTML directly references 13 CSS files and 30 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 152 distinct images.
Recommendation: Optimise images, use lazy loading and remove unnecessary media.
Based on anonymous Chrome user data from the last 28 days · Chrome users only · No Firefox/Safari
Mobile · 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
Largest requests
Total: 1.007,3 KB
Total: 4.127,0 KB
30 JavaScript files adding up to around 13.17 KB. Reduce unnecessary scripts, tracking and plugin front-end load, defer them or load them only when needed.
152 images adding up to around 119.60 KB. Large images, missing modern formats and missing lazy loading are a good lever here.
The real page load triggers 74 individual requests. Reduce unnecessary lazy loads, third parties and extra front-end files first.
The CLS value is 0.19.
Recommendation: Check image dimensions, reserved space, fonts and dynamically injected elements.
69 JavaScript files are loaded synchronously and block page rendering.
Recommendation: Load scripts with an async or defer attribute wherever possible.
26 of 29 images have no explicit dimensions and can cause layout shifts (CLS).
Recommendation: Set width and height attributes on img tags.
CLS 0.19
74 requests during page load
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: 160 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: 3/9, fonts: unknown | page cache: no, CDN: none detected, origin: unknown | HTML Cache-Control: private
152 images were detected. Of those, 0 use lazy loading and 1 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: PNG: 5, SVG: 4 (9 of 152 measured), measured image weight: 119.60 KB
30 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: 30 external files, 0 data URI scripts, 13.17 KB
No clear web font files were detected.
Why it matters: Many or large web fonts increase loading time and can cause visible layout delays.
Technical value: 0 font files, 0 external font services, groups: no grouped fonts detected, measured font weight: 0 B
13 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: 13, additional dependencies: 10, estimated CSS weight: 65.17 KB
The page loads content from 1 external host.
Why it matters: Every additional external domain increases dependencies and can affect loading time.
Technical value: other: 18 — r.bing.com
The first visible content appears after around 636 ms, the most important visible content after around 1752 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: 636 ms, LCP: 1752 ms
Visible shifts occur while loading. The measured CLS value is 0.19.
Why it matters: CLS describes whether content shifts visibly while loading.
Technical value: CLS: 0.19
The real page load issues relatively many requests: 74 requests with around 728.44 KB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 74 requests, 728.44 KB
18 assets detected
r.bing.com
Externe Dienste erhöhen generell Abhängigkeiten und zusätzliche Verbindungen.
These services were actually contacted during the real page build in the browser.
4 requests · 35,4 KB
r.bing.com
These hosts were detected directly in HTML or CSS. Not every one of them was necessarily loaded during the real page build.
This classification is based on statically detected asset hosts and complements the real browser runtime measurement.
18 assets detected
r.bing.com
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.
These are image files that are not referenced directly in the HTML, but in CSS via url(...) references.
Sample: 9 of 152 images were loaded and measured. Size and count refer only to these images.
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.
https://bing.de/
These points are not critical, but can improve the performance, stability or clarity of the page structure.
The browser issued 74 requests.
Recommendation: Above all, reduce or bundle tracking, builder assets, fonts and additional external services.
Images were detected, but no loading="lazy" on any image element.
Recommendation: Enable lazy loading for images outside the viewport.
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 Total Blocking Time is around 69 ms.
The server response takes around 160 ms.
Detected compression: br.
Preconnect: 2, DNS prefetch: 2, prefetch: 1.
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 10 further stylesheet dependencies.
No clear WordPress indicators were found in the HTML or the asset paths.
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 →