comspot.de website review

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.4 s).

39 images could be 8.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

Hotjar costs a phone 379 ms of main-thread work and 65 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

About 275 KiB of JavaScript is downloaded but never used on this page.

The page has 2,637 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

4 third-party services load with your homepage (Hotjar, Trusted Shops and Google CDN and others), adding 224 KiB and 419 ms of main-thread time.

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

4 files are served with short cache lifetimes, so returning visitors download them again (11 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.

3 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (1.8 s).

36 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-10, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 32.0 MB in 144 requests on a phone: fonts 20.9 MB (4), images 10.1 MB (70) and scripts 752 KiB (62). Under 2 MB keeps phones on slow connections fast.

5 images weigh 7.4 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 AppleCare_iPhone_PDP_Image_Position-1_Update24__DEDE.jpg at 4,000 px wide, shown at 128 px. Resized copies would save about 7.6 MB.

16 images further down the page (8.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

14 images (8.0 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.

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

12 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must be contained by particular parents: 5 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to 279 pages on comspot.de and 7 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.

/store-locator/offcanvas has no <title>, so Google invents the link text in results.

/store-locator and /compare/mac all use the title “COMSPOT”. Search engines can't tell which page to show for a search, so each competes with the others.

/store-locator/offcanvas, /store-locator, /Mac/MacBook-Neo, /Mac/MacBook-Air, /Mac/MacBook-Pro and /Mac/iMac and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

/store-locator/offcanvas, /Mac, /Mac/MacBook-Neo, /Mac/MacBook-Air, /Mac/MacBook-Pro and /Mac/iMac and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

/Mac took over 3 s to send its HTML from our server.

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

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

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.

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

Opening the homepage sets 3 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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.