Website review, no card needed
acatis.de website review
Visit site (opens in a new tab)Reviewed 3 November 202637 issues · 103 checks
This review found 37 issues worth fixing on acatis.de, 11 of them high impact, across 103 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
87BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 85 ms |
| May 23, 2026 | 87 ms |
| May 30, 2026 | 85 ms |
| Jun 6, 2026 | 90 ms |
| Jun 13, 2026 | 88 ms |
| Jun 20, 2026 | 90 ms |
| Jun 27, 2026 | 101 ms |
| Jul 4, 2026 | 101 ms |
| Jul 11, 2026 | 100 ms |
| Jul 18, 2026 | 97 ms |
| Jul 25, 2026 | 101 ms |
| Aug 1, 2026 | 101 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 97 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 98 ms |
| Sep 5, 2026 | 98 ms |
| Sep 12, 2026 | 90 ms |
| Sep 19, 2026 | 87 ms |
| Sep 26, 2026 | 87 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 93 ms |
| Oct 17, 2026 | 105 ms |
| Oct 24, 2026 | 99 ms |
| Oct 31, 2026 | 102 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
acatis.de does not allow embedding, so this is Google's rendering of the page.
Speed
Render-blocking requests
1.9 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Improve image delivery
1.1 MB15 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
150 ms · 63 KiBAbout 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
2 third-party services on the page
2 third-party services load with your homepage (Cookiebot and slsnlytcs.com), adding 157 KiB and 49 ms of main-thread time.
Reduce unused JavaScript
51 KiBAbout 51 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
36 KiB2 files are served with short cache lifetimes, so returning visitors download them again (36 KiB).
Minify CSS
15 KiB15 KiB could be saved by minifying CSS.
Minify JavaScript
9 KiB9 KiB could be saved by minifying JavaScript.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
3 checks passed
Mobile performance score: 93
93/100Your mobile performance score is 93. That is in Google's “good” band (90 and up).
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 173 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.122
0.122The layout shifts by 0.122 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 85 ms to 102 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 101 ms
101 msReal visitors wait 101 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 680 ms
680 msReal visitors wait 680 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.2 s
1.2 sYour largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Die Investmentvorbilder von ACATIS sind Benjamin Graham, Wa…”.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 1.2 s
1.2 sThe page is fully interactive after 1.2 s.
Images and page weight
1 image over 500 KB
slide-home__5-min.jpg weighs 773 KiB. On a phone connection a single image that size takes seconds.
5 images far larger than shown
609 KiB5 images are downloaded at several times the size a phone draws them, for example csm_01-Fondsmanager-des-Jahres_7e0e7d30c5.png at 576 px wide, shown at 78 px. Resized copies would save about 609 KiB.
Page weight: 3.6 MB in 84 requests
3.6 MBYour homepage downloads 3.6 MB in 84 requests on a phone: images 3.1 MB (31), scripts 313 KiB (27) and fonts 82 KiB (5). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (1.7 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
8 images below the first screen load straight away
8 images further down the page (780 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
1.02 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.02 g of CO₂e: 122.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
55 text elements with low contrast
55 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
22 tap targets too small
22 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
17 images without alt text
17 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
113 internal links, 14 external
The homepage links to 113 pages on acatis.de and 14 external pages.
5 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Wir investieren, wenn der Wert höher ist als der Preis. Wir investieren in unterbewertete Aktien, Länder, Branchen, Fon…”.
Title: 60 characters
Your title is a healthy 60 characters: “ACATIS Investment Kapitalverwaltungsgesellschaft mbH: ACATIS”.
Canonical URL set
The canonical URL is https://www.acatis.de/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.acatis.de/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (923 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (5 KiB, 30 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
/ and /en all use the title “ACATIS Investment Kapitalverwaltungsgesellschaft mbH: ACATIS”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
/sitemap, /rechtliche-hinweise-1 and /aktuelles/bericht-zur-lage-der-wirtschaft have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
/aktuelles/presse and /aktuelles/unternehmensneuigkeiten use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
/sitemap, /kontakt, /impressum, /datenschutz, /rechtliche-hinweise-1 and /en and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 58 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
13 small tap targets
13 of 49 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
8 distorted images
8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Security and trust
1 broken external link
1 link to other sites is dead, for example http://www.acatis.ch/ (404).
No X-Content-Type-Options
X-Content-Type-Options: nosniff is missing, so browsers may guess file types.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
8 checks passed
Served over HTTPS
The homepage is served over HTTPS (acatis.de).
Valid certificate (87 days left)
The certificate from Let's Encrypt · YR2 verifies for acatis.de and is valid for another 87 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
HSTS enabled
Strict-Transport-Security is set, so browsers always use https.
http:// redirects to https
http://acatis.de redirects to the secure version.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
security.txt published
A security.txt file tells researchers how to report a problem with your site.
Domain and trust
No CAA record
acatis.de has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 698 words of copy
The homepage carries about 698 words of visible text.
4 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Matomo.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Email authentication
No DKIM key on the usual selectors
We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.
Email authentication score: 80/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
DMARC policy: quarantine
DMARC tells receivers to quarantine mail that fails authentication.
SPF with a strict ending (-all)
An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 ip4:213.61.149.202 ip4:178.22.107.125 ip4:136.243.123.171 include:spf.protection.outlook.com include:email-deliv…”.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- TYPO3 CMS
- Framework
- jQuery
- Analytics
- Matomo
- Hosting
- Hetzner
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on acatis.de, including 5 speed issues, 5 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.