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.
Google PageSpeed · Mobile 28 · Desktop 34
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 | 11 | 11 |
| FCP i | 184 ms | 148 ms |
| LCP i | 2136 ms | 2132 ms |
| CLS i | 0 | 0 |
| TBT i | 1423 ms 5 long tasks | 1403 ms 5 long tasks |
Synthetic measurement from Google Lighthouse — measured independently of the turbometrics score.
Google rates this page as slow — action needed. · Fetched on 30 Sep 2026 7:47 PM
Total Blocking Time approx. 1403 ms
https://projekt-aicom.de/ – 2.69 MB
Host: projekt-aicom.de
https://projekt-aicom.de/
No H1 detected
No viewport meta tag
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: 0,4 KB
Total: 0,4 KB
The basics are in order. It pays off to work through the smaller bottlenecks from the report.
The browser main thread was blocked for around 1403 ms during page load (Total Blocking Time).
Recommendation: Reduce JavaScript load, defer heavy scripts and break up long tasks.
4 JavaScript files are loaded synchronously and block page rendering.
Recommendation: Load scripts with an async or defer attribute wherever possible.
6 of 6 images have no explicit dimensions and can cause layout shifts (CLS).
Recommendation: Set width and height attributes on img tags.
No WebP/AVIF detected
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: 63 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: unknown, JS: unknown, images: unknown, fonts: unknown | page cache: no, CDN: none detected, origin: LiteSpeed | HTML Cache-Control: empty (normal for dynamic pages)
8 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 148 ms, the most important visible content after around 2132 ms. That is still in the green range, but there is room for improvement.
Why it matters: These values describe when users actually see the first and the most important content.
Technical value: FCP: 148 ms, LCP: 2132 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: 11 requests with around 2.69 MB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 11 requests, 2.69 MB
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.
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.
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.
Title: yes, H1: no, Viewport: no.
Recommendation: Complete the basic HTML and SEO information.
These points already stood out positively in the current scan.
The server response takes around 63 ms.
Detected compression: br.
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.
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 →