01M0B66TWRSCZ44KB2EAEP5MH0
Overall score
The website is in very good shape.
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 rates this page as very fast. · Fetched on 18 Aug 2026 7:40 PM
Act now
gzip/Brotli not detected
Likely LCP text 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.
Main causes
Actually loaded in the browser.
Top hosts by data volume
Largest requests
Total: 0,3 KB
Total: 0,3 KB
Recommendations
The basics are in order. It pays off to work through the smaller bottlenecks from the report.
No clear gzip or Brotli compression was detected for the HTML response.
Recommendation: Enable gzip or Brotli for text-based content.
No canonical link
No HIT/Age indicators detected
No CDN indicators detected
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: 104 ms
No clear compression was detected, so unnecessarily much data may be transferred.
Why it matters: Compression reduces the transfer size of HTML, CSS and JavaScript.
Technical value: Not clearly detected
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: unknown, JS: unknown, images: unknown, fonts: unknown | page cache: no, CDN: none detected, origin: Caddy | HTML Cache-Control: empty (normal for dynamic pages)
0 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: no detailed types detected, measured image weight: 0 B
0 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: 0 external files, 0 data URI scripts, 0 B
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
0 direct CSS files and 0 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: 0, additional dependencies: 0, estimated CSS weight: 0 B
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 412 ms, the most important visible content after around 412 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: 412 ms, LCP: 412 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: 2 requests adding up to around 13.41 KB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 2 requests, 13.41 KB
Score breakdown
Caching
Cache quality by asset type
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
Elevated latency to the remote host — the measurement may be affected.
Connection timing (TTFB: 104 ms)
Note: only the measured sample could be used for images, not a measurement of the actual load process. The real image weight is probably higher than shown here.
Details on individual metrics
In-depth values for assets, images, fonts, CSS and JavaScript. The most important groups are grouped thematically below.
WordPress detection
Already done well
These points already stood out positively in the current scan.
The Total Blocking Time is around 0 ms.
The server response takes around 104 ms.
The website is reachable over HTTPS.
The website is served over HTTP/2.
The website advertises HTTP/3 via the Alt-Svc header.
Additional hints
Supplementary hints from the scan that can be useful for classification and technical assessment.
No clear WordPress indicators were found in the HTML or the asset paths.
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.