cbr.de website review

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

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

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

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

1 third-party service load with your homepage (ctfassets.net), adding 1.9 MB and 0 ms of main-thread time.

ctfassets.net costs a phone 0 ms of main-thread work and 1.9 MB 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.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

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

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

Polyfills for old browsers add 14 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.

Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “we believe in quality and style.”. Most of its time is element render delay (5.8 s).

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 79 ms to 82 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.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.2 MB in 32 requests on a phone: images 1.9 MB (7), scripts 239 KiB (17) and fonts 62 KiB (1). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example SOM_26_10_Markenseite_Slider_Images_5.jpg at 1,828 px wide, shown at 390 px. Resized copies would save about 126 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is only 18 characters: “CBR Fashion - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

No XML sitemap at https://www.cbr.de/sitemap.xml, so Google discovers your pages only by following links.

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

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

The homepage links to 26 pages on cbr.de and 8 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.

/en, /brands and /de all use the title “CBR Fashion - Home”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/en/career/categories/design-product-creative, /en/career/categories/sales-retail-outlet and /en/career/categories/ecommerce have no meta description, so Google writes the search snippet from whatever text it finds.

/brands and /de use the same meta description. A description written for each page earns more clicks.

/brands, /en/brands/cecil, /en/brands/street-one, /en/brands/street-one-men, /en/brands/street-one-studio and /en/career/about-us have no <h1> headline, so visitors and search engines get no clear main topic.

/brands, /career, /en/brands/cecil, /en/brands/street-one and /en/brands/street-one-men have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/de, /en/brands/cecil, /en/brands/street-one-men, /en/career/categories/design-product-creative, /en/career/categories/sales-retail-outlet and /en/career/categories/ecommerce took over 3 s to send their HTML from our server.

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

2 of 7 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 “Failed to load resource: net::ERR_FAILED”.

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

Opening https://cbr.de goes through 2 redirects before the homepage loads.

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”; the header is deprecated and can introduce bugs. Use 0 or remove it.

cbr.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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 180 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

DMARC is set to p=none, so mail pretending to be cbr.de is still delivered. Reports are on, so moving to quarantine is the next step.

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