Website review, no card needed
calmbach.de website review
Visit site (opens in a new tab)Reviewed 9 November 202634 issues · 75 checks
This review found 34 issues worth fixing on calmbach.de, 13 of them high impact, across 75 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
80BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.2 s
2.7 s
3.3 s
3.8 s
4.4 s
Speed
Render-blocking requests
5.2 s71 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.2 s.
Improve image delivery
2.9 MB9 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
Font display
600 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).
Use efficient cache lifetimes
521 KiB18 files are served with short cache lifetimes, so returning visitors download them again (521 KiB).
Reduce unused JavaScript
430 KiBAbout 430 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
300 ms · 50 KiBAbout 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
3 third-party services on the page
3 third-party services load with your homepage (Google Maps, saasweb.net and Google Fonts), adding 331 KiB and 152 ms of main-thread time.
Minify CSS
150 ms · 7 KiB7 KiB could be saved by minifying CSS.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 53 ms. During a long task the page ignores taps.
Minify JavaScript
29 KiB29 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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 249 ms of it running JavaScript. That is comfortably low.
Server response: 118 ms
118 msYour server sent the HTML in 118 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 24.1 s
24.1 sThe page becomes fully interactive after 24.1 s. Good is under 3.8 s.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Auch in mittelständisch geprägten Druck- und Verlagsunterne…”. Most of its time is element render delay (2.6 s).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 2 ms
2 msScripts block the page for only 2 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.9 MB in 157 requests
5.9 MBYour homepage downloads 5.9 MB in 157 requests on a phone: images 4.8 MB (14), scripts 750 KiB (67) and stylesheets 199 KiB (70). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
1.5 MB5 images are downloaded at several times the size a phone draws them, for example workflow-gross.jpg at 1,688 px wide, shown at 390 px. Resized copies would save about 1.5 MB.
11 images in older formats
11 images (4.5 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.
10 images below the first screen load straight away
10 images further down the page (4.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.66 g of CO₂e: 199.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
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.
No robots.txt
There is no robots.txt at calmbach.de/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
21 internal links, 2 external
The homepage links to 21 pages on calmbach.de and 2 external pages.
4 checks passed
One H1 headline
Your main headline reads: “BRANCHEN-STUDIEN”.
Title: 43 characters
Your title is a healthy 43 characters: “Calmbach – print and publishing consultants”.
Canonical URL set
The canonical URL is https://www.calmbach.de/.
XML sitemap found
Your XML sitemap is reachable at https://www.calmbach.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.
No llms.txt
There is no https://www.calmbach.de/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (716 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://www.calmbach.de/welcome declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.calmbach.de/welcome all use the title “Calmbach – print and publishing consultants”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://www.calmbach.de/welcome, https://www.calmbach.de/druckereistrategie-2, https://www.calmbach.de/workflow-optimierung, https://www.calmbach.de/vertriebsstrategie, https://www.calmbach.de/kampf-den-fehlerkosten and https://www.calmbach.de/workflow-pflichtenheft and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.calmbach.de/datenschutz and https://www.calmbach.de/impressum have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.calmbach.de/welcome and https://www.calmbach.de/vertriebsstrategie took over 3 s to send their HTML from our server.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 17 testimonial or review blocks. 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 683 words of copy
The homepage carries about 683 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
2 checks passed
Analytics in place
Analytics detected: Matomo.
Direct contact links
Visitors can reach you directly: 0 phone links and 6 email links.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
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).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at calmbach.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- 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 34 issues on calmbach.de, including 11 speed issues, 4 SEO issues and 5 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.