01M1P4VBD98EA03WAQE7SW9B2Y
Overall score
The website is fundamentally solid. Some clear bottlenecks should be fixed.
Browser runtime measurement
These values come from the real page build in the browser and show the differences between desktop and mobile.
Google PageSpeed score
Synthetic measurement from Google Lighthouse — measured independently of the turbometrics score.
Google sees optimisation potential for this page. · Fetched on 4 Sep 2026 5:55 AM
Act now
Glanzbar-9.png – 814.69 KB
File: Glanzbar-9.png · Host: glanzbar.de
https://glanzbar.de/wp-content/uploads/2025/02/Glanzbar-9.png
Glanzbar-9.png – 814.69 KB
File: Glanzbar-9.png · Host: glanzbar.de
https://glanzbar.de/wp-content/uploads/2025/02/Glanzbar-9.png
No long-lived cache rules detected
14 scripts without async/defer
The HTML directly references 32 CSS files and 14 external JavaScript files.
Recommendation: Reduce unnecessary assets and review the theme and plugin load.
Likely LCP background image candidate
The largest visible content appears to be shaped by a CSS background image.
The element probably uses a background image via CSS.
Main causes
Actually loaded in the browser.
Top hosts by data volume
Largest requests
Total: 1.668,5 KB
Total: 2.917,4 KB
Recommendations
14 JavaScript files adding up to around 102.43 KB. Reduce unnecessary scripts, tracking and plugin front-end load, defer them or load them only when needed.
9 images adding up to around 2.82 MB. Large images, missing modern formats and missing lazy loading are a good lever here.
Static files should get clear, long-lived Cache-Control values so repeat visits become faster.
Glanzbar-9.png weighs around 814.69 KB.
Recommendation: Resize hero and above-the-fold images and compress them with modern formats.
14 JavaScript files are loaded synchronously and block page rendering.
Recommendation: Load scripts with an async or defer attribute wherever possible.
No clear long-lived cache headers were detected for static resources.
Recommendation: Set Cache-Control headers for static files properly.
No WebP/AVIF detected
2.82 MB
Explained simply
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: 483 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)
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/14, images: 0/12, fonts: unknown | page cache: no, CDN: none detected, origin: nginx | HTML Cache-Control: empty (normal for dynamic pages)
9 images were detected. Of those, 0 use lazy loading and 0 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: 7, JPG: 5 (4 of 9 measured), measured image weight: 2.82 MB
14 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: 14 external files, 0 data URI scripts, 102.43 KB
1 external font services were detected, but no concrete font files were measured. That still points to web fonts.
Why it matters: Many or large web fonts increase loading time and can cause visible layout delays.
Technical value: 0 font files, 1 external font services, groups: no grouped fonts detected, measured font weight: 0 B
32 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: 32, additional dependencies: 10, estimated CSS weight: 111.04 KB
The page loads content from 2 external hosts.
Why it matters: Every additional external domain increases dependencies and can affect loading time.
Technical value: no categories detected — fonts.googleapis.com, maps.google.com
The first visible content appears after around 740 ms, the most important visible content after around 796 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: 740 ms, LCP: 796 ms
Layout stability is good. The measured CLS value is 0.
Why it matters: CLS describes whether content shifts visibly while loading.
Technical value: CLS: 0
The number of real browser requests is manageable: 65 requests adding up to around 1.65 MB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 65 requests, 1.65 MB
Score breakdown
Speed
Cache quality by asset type
Externally loaded services in the browser
These services were actually contacted during the real page build in the browser.
7 requests · 4,6 KB
fonts.googleapis.com, fonts.gstatic.com
Statically detected external hosts
These hosts were detected directly in HTML or CSS. Not every one of them was necessarily loaded during the real page build.
Largest requests 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.
Technical metrics
Measurement conditions
Connection timing (TTFB: 483 ms)
Tasks that blocked the browser main thread.
Details on individual metrics
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.
Sample: 4 of 9 images were loaded and measured. Size and count refer only to these images.
Detected font files: 0, External font services: 1. 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.
WordPress detection
Optimisation potential
These points are not critical, but can improve the performance, stability or clarity of the page structure.
36 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 2.82 MB.
Recommendation: Resize and compress images and use modern formats.
Glanzbar-9.png weighs around 814.69 KB.
Recommendation: Resize and compress this image specifically and serve it in a more modern format.
Images were detected, but no loading="lazy" on any image element.
Recommendation: Enable lazy loading for images outside the viewport.
No WebP or AVIF image files were detected in the HTML image sources.
Recommendation: Use WebP or AVIF for images where possible.
Already done well
These points already stood out positively in the current scan.
The Total Blocking Time is around 49 ms.
The server response takes around 483 ms.
Detected compression: br.
Preconnect: 1, DNS prefetch: 0, prefetch: 0.
The website is reachable over HTTPS.
The website is served over HTTP/2.
Additional hints
Supplementary hints from the scan that can be useful for classification and technical assessment.
CSS pulls in 10 further stylesheet dependencies.
The page uses WordPress, likely with elementor.
Detected theme: hello-elementor.
Detected indicators: elementor, yoast-seo.
The website is only reachable over IPv4.
Waterfall
Detailed request waterfall from the browser run.
Raw data
Complete scan data as a machine-readable JSON file or tabular export.