Get notified when this page gets slower
Register for free – monitoring, alerts and more.
The website is fundamentally solid. Targeted improvements can raise the score further. 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 | 12 | 12 |
| FCP i | 2268 ms | 2288 ms |
| LCP i | 2268 ms | 2288 ms |
| CLS i | 0 | 0 |
| TBT i | 0 ms | 0 ms 1 long tasks |
Server response approx. 1139 ms
No long-lived cache rules detected
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: 221,6 KB
Total: 221,6 KB
The server response takes around 1139 ms. A full page cache, a faster backend and less server-side work will likely have the biggest effect.
Static files should get clear, long-lived Cache-Control values so repeat visits become faster.
Additional CSS dependencies (3) and many web fonts (6) should be combined or reduced.
The First Contentful Paint is around 2288 ms.
Recommendation: Check early render blockers, server response and critical assets.
The server response takes around 1139 ms.
Recommendation: Check caching and backend performance.
No clear long-lived cache headers were detected for static resources.
Recommendation: Set Cache-Control headers for static files properly.
FCP approx. 2288 ms
First Contentful Paint approx. 2288 ms
must-revalidate, no-cache, private
No canonical link
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: 1139 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: 3/3, JS: 1/1, images: unknown, fonts: 0/6 | page cache: yes, CDN: none detected, origin: unknown | HTML Cache-Control: must-revalidate, no-cache, private
1 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
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, 22.86 KB
6 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: 6 font files, 0 external font services, groups: lora-v14-latin (3), Metropolis (2), Metropolis-SemiBold (1), measured font weight: 132.73 KB
3 direct CSS files and 3 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: 3, additional dependencies: 3, estimated CSS weight: 65.13 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 2288 ms, the most important visible content after around 2288 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: 2288 ms, LCP: 2288 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: 12 requests adding up to around 225.59 KB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 12 requests, 225.59 KB
This list shows the largest requests from the real browser run and helps you spot notable files and hosts faster.
Elevated latency to the remote host — the measurement may be affected.
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.
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.
Detected font files: 6, External font services: 0. External font services are e.g. Google Fonts or Adobe Typekit, from which concrete font files are only loaded later.
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.
No WebP or AVIF image files were detected in the HTML image sources.
Recommendation: Use WebP or AVIF for images where possible.
Detected 6 font files totalling around 132.73 KB.
Recommendation: Load fewer font weights and serve fonts as efficiently as possible.
These points already stood out positively in the current scan.
The Total Blocking Time is around 0 ms.
Detected compression: br.
6 @font-face rules with font-display detected.
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 3 further stylesheet dependencies.
CSS references 6 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 →