telecolumbus.com website review

10 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.

Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

About 43 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 50 ms faster on a phone.

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

About 20 KiB of CSS is downloaded but never applied on this page.

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 20.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Aktuelles PŸUR verteidigt Testsieg im connect Hotline-Test …”.

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

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

For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

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

22 images have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 6.0 MB in 55 requests on a phone: images 5.7 MB (33), scripts 204 KiB (16) and fonts 121 KiB (3). Under 2 MB keeps phones on slow connections fast.

4 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.

9 images are downloaded at several times the size a phone draws them, for example brekoanalyse2026.png at 1,421 px wide, shown at 350 px. Resized copies would save about 3.0 MB.

18 images (5.3 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 further down the page (4.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

12 images have no alt text, which hurts accessibility and image search.

7 visible links have no text or label, so screen readers cannot say where they go.

Your title is only 29 characters: “Startseite – Tele Columbus AG”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 70 pages on telecolumbus.com and 11 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.telecolumbus.com/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.

https://www.telecolumbus.com/en 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.

https://www.telecolumbus.com/en, https://www.telecolumbus.com/unternehmen/produkte, https://www.telecolumbus.com/unternehmen/corporate-governance, https://www.telecolumbus.com/unternehmen/wohnungswirtschaftlicher-beirat, https://www.telecolumbus.com/unternehmen/beteiligungen and https://www.telecolumbus.com/unternehmen/verbaende and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.telecolumbus.com/unternehmen, https://www.telecolumbus.com/unternehmen/produkte, https://www.telecolumbus.com/presse and https://www.telecolumbus.com/presse/corporate-blog took over 3 s to send their HTML from our server.

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

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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 614 words of visible text.

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.