Get notified when this page gets slower
Register for free – monitoring, alerts and more.
The website is in very good shape. Minor optimisations are still possible.
Google PageSpeed · Mobile 100 · Desktop 100
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 | 6 | 6 |
| FCP i | 412 ms | 1716 ms |
| LCP i | 412 ms | 1716 ms |
| CLS i | 0 | 0 |
| TBT i | 16 ms 1 long tasks | 0 ms |
LCP mobile: 1716 ms · desktop: 412 ms.
Synthetic measurement from Google Lighthouse — measured independently of the turbometrics score.
Google rates this page as very fast. · Fetched on 13 Oct 2026 7:55 PM
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: 36,0 KB
Total: 36,0 KB
The server response takes around 781 ms. A full page cache, a faster backend and less server-side work will likely have the biggest effect.
Additional CSS dependencies (1) and many web fonts (0) should be combined or reduced.
The mobile LCP is around 1304 ms above the desktop value.
Recommendation: Check the mobile page load, image sizes, CSS and third parties separately.
The First Contentful Paint is around 1716 ms.
Recommendation: Check early render blockers, server response and critical assets.
The server response takes around 781 ms.
Recommendation: Check caching and backend performance.
FCP approx. 1716 ms
Server response approx. 781 ms
No WebP/AVIF detected
First Contentful Paint approx. 1716 ms
No lazy loading indicators found
LCP mobile 1716 ms vs. desktop 412 ms
667 public scans of this page
These short texts put the most important measurements into plain language.
The server response has room for improvement and already delays page rendering noticeably.
Why it matters: TTFB stands for “time to first byte” — the time until the server returns the first data.
Technical value: 781 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: 1/1, JS: 0/1, images: 2/2, fonts: unknown | page cache: no, CDN: cloudflare, origin: unknown | HTML Cache-Control: no-cache, private
3 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: SVG: 2 (2 of 3 measured), measured image weight: 7.44 KB
1 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: 1 external files, 0 data URI scripts, 4.88 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
1 direct CSS files and 1 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: 1, additional dependencies: 1, estimated CSS weight: 126.75 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 1716 ms, the most important visible content after around 1716 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: 1716 ms, LCP: 1716 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: 6 requests adding up to around 47.36 KB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 6 requests, 47.36 KB
This list shows the largest requests from the real browser run and helps you spot notable files and hosts faster.
In-depth values for assets, images, fonts, CSS and JavaScript. The most important groups are grouped thematically below.
Sample: 2 of 3 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.
These points are not critical, but can improve the performance, stability or clarity of the page structure.
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.
These points already stood out positively in the current scan.
The Total Blocking Time is around 0 ms.
Detected compression: br.
No fonts were requested from Google servers while loading the page.
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 1 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 →