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 | 10 | 9 |
| FCP i | 236 ms | 196 ms |
| LCP i | 296 ms | 196 ms |
| CLS i | 0 | 0 |
| TBT i | 5 ms 1 long tasks | 0 ms |
Synthetic measurement from Google Lighthouse — measured independently of the turbometrics score.
Google rates this page as very fast. · Fetched on 23 Oct 2026 2:55 AM
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: 129,9 KB
Total: 153,0 KB
The server response takes around 685 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 (2) should be combined or reduced.
The server response takes around 685 ms.
Recommendation: Check caching and backend performance.
HTML, CSS and the images loaded with the page add up to 12 distinct images.
Recommendation: Optimise images, use lazy loading and remove unnecessary media.
3 @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.
Server response approx. 685 ms
no-cache, private
No HIT/Age indicators detected
12 images
664 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: 685 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: 7/11, fonts: 2/2 | page cache: no, CDN: cloudflare, origin: unknown | HTML Cache-Control: no-cache, private
12 images were detected. Of those, 5 use lazy loading and 9 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: 5, AVIF: 4, SVG: 2 (11 of 12 measured), measured image weight: 431.08 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
2 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: 2 font files, 0 external font services, groups: poppins-latin-600-normal (1), poppins-latin-700-normal (1), measured font weight: 15.45 KB
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: 222.93 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 196 ms, the most important visible content after around 196 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: 196 ms, LCP: 196 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: 9 requests adding up to around 140.93 KB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 9 requests, 140.93 KB
This list shows the largest requests from the real browser run and helps you spot notable files and hosts faster.
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.
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: 11 of 12 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 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.
CSS references 2 additional font files.
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 →