gigaset.com website review

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

14 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

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

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

About 199 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 680 ms faster on a phone.

32 KiB could be saved by minifying JavaScript.

4 third-party services load with your homepage (Google Tag Manager, Civic and eye-able.com and others), adding 491 KiB and 358 ms of main-thread time.

18 KiB could be saved by minifying CSS.

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

Polyfills for old browsers add 54 KiB JavaScript that modern phones do not need.

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

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 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Gigaset GX30 & GX50”.

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

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

Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

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

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

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

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

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

Your homepage downloads 3.5 MB in 61 requests on a phone: images 2.2 MB (23), scripts 978 KiB (25) and stylesheets 262 KiB (5). Under 2 MB keeps phones on slow connections fast.

11 images (1.1 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 (855 KiB) 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.01 g of CO₂e: 120.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 72 pages on gigaset.com and 7 external pages.

Your Organization JSON-LD is missing name, sameAs (social profiles) and description. 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 /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.

/hq_en and /pro/hq_en all use the title “Gigaset - Phones & Smartphones | Made in Germany”. Search engines can't tell which page to show for a search, so each competes with the others.

/hq_en/telephones/telephone-accessories, /hq_en/telephones/spare-parts, /hq_en/telephones/elderly-phones, /hq_en/smartphones, /hq_en/smartphones/outdoor-smartphones and /hq_en/smartphones/elderly-mobile-phones have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example /hq_en/telephones-overview/cordless-phones-overview, whose canonical is /hq_en/cms/cordless-phones.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pro/hq_en has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 link from your homepage to your own site is broken, for example https://www.gigaset.com/hq_en/checkout/cart/ (404).

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

1 link go through two or more redirects, for example https://service.gigaset.com/.

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

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

gigaset.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

gigaset.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.

gigaset.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.

Social proof on the homepage: 39 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 468 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 Tag Manager (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 2 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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.