dachcom.com website review

About 289 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 54 (desktop: 79). Pages that score under 90 lose visitors before the first paint.

Reduce initial server response time. Google estimates savings of 654 ms on a phone.

The HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.

8 files are served with short cache lifetimes, so returning visitors download them again (353 KiB).

A phone's processor spends 2.9 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your server takes 754 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

6 third-party services load with your homepage (Google Tag Manager, Hubspot and cookiefirst.com and others), adding 476 KiB and 306 ms of main-thread time.

10 long tasks block the main thread while loading, the longest for 191 ms. During a long task the page ignores taps.

Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

Desktop scores 79 but mobile only 54. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir machen Marken zum Erlebnis und bringen Ideen zum Glänzen”.

The page becomes fully interactive after 11.0 s. Good is under 3.8 s.

Visually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.

Real visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 479 ms in total while the page loads. Good is under 200 ms.

The first text or image appears after 2.4 s on a phone. Good is under 1.8 s.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 129 ms to 156 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.6 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.5 MB in 62 requests on a phone: media 9.1 MB (3), scripts 853 KiB (31) and fonts 214 KiB (4). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (37 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 2.99 g of CO₂e: 358.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 visible link has no text or label, so screen readers cannot say where it goes.

The page declares lang=“de_CH”, which is not a usable language code, so screen readers and translation tools guess.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 74 characters, so Google will cut it off around 60: “DACHCOM – Fullservice Kommunikations- und Werbeagentur Schweiz, Ostschweiz”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 43 pages on dachcom.com and 13 external pages.

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.

There is no /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.

/de-ch/referenzen/uebersicht has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.

10 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link from your homepage to your own site is broken, for example https://www.dachcom.com/cdn-cgi/l/email-protection (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://dachcom.com goes through 2 redirects before the homepage loads.

1 link go through two or more redirects, for example https://www.opendxp.ch/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

dachcom.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

dachcom.com 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.

dachcom.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 541 words of visible text.

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 4 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 22 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.