Get notified when this page gets slower
Register for free – monitoring, alerts and more.
The website is fundamentally solid. Some clear bottlenecks should be fixed.
Google PageSpeed · Mobile 97 · 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 | 80 | 79 |
| FCP i | 696 ms | 616 ms |
| LCP i | 3848 ms | 616 ms |
| CLS i | 0 | 0 |
| TBT i | 197 ms 3 long tasks | 154 ms 4 long tasks |
Synthetic measurement from Google Lighthouse — measured independently of the turbometrics score.
Google rates this page as very fast. · Fetched on 19 Oct 2026 7:52 AM
No long-lived cache rules detected
19 scripts without async/defer
No H1 detected
The HTML directly references 24 CSS files and 20 external JavaScript files.
Recommendation: Reduce unnecessary assets and review the theme and plugin load.
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: 373,9 KB
Total: 377,3 KB
20 JavaScript files adding up to around 65.93 KB. Reduce unnecessary scripts, tracking and plugin front-end load, defer them or load them only when needed.
The real page load triggers 79 individual requests. Reduce unnecessary lazy loads, third parties and extra front-end files first.
Static files should get clear, long-lived Cache-Control values so repeat visits become faster.
19 JavaScript files are loaded synchronously and block page rendering.
Recommendation: Load scripts with an async or defer attribute wherever possible.
The browser issued 79 requests.
Recommendation: Above all, reduce or bundle tracking, builder assets, fonts and additional external services.
No clear long-lived cache headers were detected for static resources.
Recommendation: Set Cache-Control headers for static files properly.
79 requests during page load
34 CSS files including imports
No lazy loading indicators found
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: 295 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: gzip
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/15, images: 0/2, fonts: unknown | page cache: no, CDN: none detected, origin: nginx | HTML Cache-Control: max-age=0
9 images were detected. Of those, 0 use lazy loading and 1 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: 1, GIF: 1 (2 of 9 measured), measured image weight: 203.22 KB
20 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: 20 external files, 0 data URI scripts, 65.93 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
24 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: 24, additional dependencies: 10, estimated CSS weight: 138.70 KB
The page loads content from 1 external host.
Why it matters: Every additional external domain increases dependencies and can affect loading time.
Technical value: no categories detected — app.hearthis.at
The first visible content appears after around 616 ms, the most important visible content after around 616 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: 616 ms, LCP: 616 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 real page load issues relatively many requests: 79 requests with around 405.39 KB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 79 requests, 405.39 KB
These services were actually contacted during the real page build in the browser.
30 requests · 15,7 KB
analytics.aimx.at, app.hearthis.at, img.hearthis.at, stats.hearthis.at
These hosts were detected directly in HTML or CSS. Not every one of them was necessarily loaded 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.
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.
These are image files that are not referenced directly in the HTML, but in CSS via url(...) references.
Sample: 2 of 9 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.
27 first-party assets have no clear long-lived cache rules.
Recommendation: Serve static files with long-lived Cache-Control values.
Images were detected, but no loading="lazy" on any image element.
Recommendation: Enable lazy loading for images outside the viewport.
Title: yes, H1: no, Viewport: yes.
Recommendation: Complete the basic HTML and SEO information.
These points already stood out positively in the current scan.
The Total Blocking Time is around 154 ms.
The server response takes around 295 ms.
Detected compression: gzip.
No fonts were requested from Google servers while loading the page.
The website is reachable over HTTPS.
The website is served over HTTP/2.
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 gutenberg.
Detected theme: enfold.
The website is only reachable over IPv4.
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 →