cmdistro.de website review

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

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

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

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

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

6 third-party services load with your homepage (Shopify, Optanon and Google Tag Manager and others), adding 576 KiB and 308 ms of main-thread time.

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

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

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

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

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

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 33.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Blood Incantation - Starspawn (10th Anniversary Edition, Lt…”.

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

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

Real visitors wait 243 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

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

Your homepage downloads 12.0 MB in 181 requests on a phone: images 10.2 MB (14), other files 1.1 MB (120) and scripts 638 KiB (37). Under 2 MB keeps phones on slow connections fast.

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

1 image (101 KiB) is 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 3.41 g of CO₂e: 408.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 26 characters: “Century Media Online Store”. Between 30 and 65 characters leaves room to say what you do and for whom.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 110 pages on cmdistro.de and 5 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.

Your homepage links to /collections/vendors, which answers with an error. Visitors hit a dead end and search engines drop it.

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

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

1 error was logged to the browser console while the page loaded, for example “Uncaught ReferenceError: jQuery is not defined”.

2 images are served at too low a resolution for sharp phone screens.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

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.

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.

cmdistro.de 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.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 481 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, Meta Pixel and TikTok Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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