Website review, no card needed
deichmann.com website review
Visit site (opens in a new tab)Reviewed 5 November 202617 issues · 84 checks
This review found 17 issues worth fixing on deichmann.com, 5 of them high impact, across 84 checks. The most urgent: 1 text element with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 281 ms |
| May 23, 2026 | 282 ms |
| May 30, 2026 | 286 ms |
| Jun 6, 2026 | 290 ms |
| Jun 13, 2026 | 289 ms |
| Jun 20, 2026 | 287 ms |
| Jun 27, 2026 | 285 ms |
| Jul 4, 2026 | 284 ms |
| Jul 11, 2026 | 287 ms |
| Jul 18, 2026 | 288 ms |
| Jul 25, 2026 | 287 ms |
| Aug 1, 2026 | 286 ms |
| Aug 8, 2026 | 285 ms |
| Aug 15, 2026 | 286 ms |
| Aug 22, 2026 | 289 ms |
| Aug 29, 2026 | 288 ms |
| Sep 5, 2026 | 288 ms |
| Sep 12, 2026 | 287 ms |
| Sep 19, 2026 | 282 ms |
| Sep 26, 2026 | 279 ms |
| Oct 3, 2026 | 279 ms |
| Oct 10, 2026 | 282 ms |
| Oct 17, 2026 | 287 ms |
| Oct 24, 2026 | 288 ms |
| Oct 31, 2026 | 288 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
deichmann.com does not allow embedding, so this is Google's rendering of the page.
Speed
Improve image delivery
7 KiB1 image could be 7 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
3 checks passed
Mobile performance score: 100
100/100Your mobile performance score is 100. That is in Google's “good” band (90 and up).
Main-thread work: 0.1 s
A phone's processor spends 0.1 s on main-thread work while loading, 7 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest content (LCP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 281 ms to 288 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
12 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 55 ms
55 msReal visitors wait 55 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 526 ms
526 msReal visitors wait 526 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 1.7 s
1.7 sYour largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the element shown below.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 0.8 s
0.8 sThe first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.
Speed Index: 0.8 s
0.8 sVisually, the page fills in at 0.8 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 1.7 s
1.7 sThe page is fully interactive after 1.7 s.
Images and page weight
About 0.01 g of CO₂ per visit
0.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.01 g of CO₂e: 1.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Page weight: 49 KiB in 4 requests
49 KiBYour homepage downloads 49 KiB in 4 requests on a phone: images 42 KiB (3) and HTML 7 KiB (1). That is a lean page.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
24 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 26 WCAG 2.2 A/AA and best-practice rules on the phone render: 24 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 2 internal links
The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
6 checks passed
Meta description: 76 characters
Your meta description is 76 characters: “Please select one of the following countries or languages to visit our shop.”.
Title: 43 characters
Your title is a healthy 43 characters: “DEICHMANN Online Shop - Select your country”.
Canonical URL set
The canonical URL is https://www.deichmann.com/.
Structured data in place
Structured data found: Organization and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.deichmann.com/sitemap.xml.
AI search readiness
No llms.txt
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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Other pages
2 pages point its canonical at the homepage
/imprint.html and /privacy.html declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
3 pages share a title
/, /imprint.html and /privacy.html all use the title “DEICHMANN Online Shop - Select your country”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
/imprint.html and /privacy.html use the same meta description. A description written for each page earns more clicks.
1 page with very little text
/imprint.html has 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.
2 internal pages checked
We fetched 2 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 2 pages we checked loaded without an error.
Every page has a meta description
All 2 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 2 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
27 of 29 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
http:// does not redirect
http://deichmann.com does not redirect to https, so some visitors land on the insecure version.
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
Short HSTS lifetime
HSTS is set, but max-age is 0 days; one year is the recommended minimum.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
5 checks passed
Served over HTTPS
The homepage is served over HTTPS (deichmann.com).
Valid certificate (40 days left)
The certificate from Google Trust Services · WE1 verifies for deichmann.com and is valid for another 40 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
All 2 links work
All 2 links checked from your homepage (2 internal, 0 external) answered without errors.
Domain and trust
No CAA record
deichmann.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.
DNSSEC is off
deichmann.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.
2 checks passed
Domain is 31 years old
31 yearsdeichmann.com was registered in Dec 1994 through Gandi SAS. An established domain carries more trust with email providers and search engines.
Registered until Nov 2028
deichmann.com is registered until Nov 2028.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 53 words
The homepage has only about 53 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
1 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Weiter zum deutschen Shop”.
Email authentication
Email authentication score: 95/100
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.
3 checks passed
DMARC policy: reject
DMARC tells receivers to reject mail that fails authentication, and sends you reports.
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 mx include:spf.protection.outlook.com include:mail.zendesk.com include:spf.eu.exclaimer.net include:esagw.dse-te…”.
DKIM signing found
A DKIM key is published (selector “selector1”), so receivers can verify mail really came from you.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
No consent tool detected
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
Company
- Founded
- 1913
- Headquarters
- Essen
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 17 issues on deichmann.com, including 1 speed issue, 3 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.