shiseido.de website review

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

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

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

Your mobile performance score is 39 (desktop: 58). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

About 161 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.

7 images could be 341 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Bazaarvoice, AB Tasty and PayPal and others), adding 702 KiB and 500 ms of main-thread time.

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

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

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 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “25% AUF UNSERE BESTSELLER”.

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

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

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

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

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

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

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

Your homepage downloads 3.5 MB in 138 requests on a phone: scripts 1.7 MB (57), images 1.3 MB (42) and stylesheets 164 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

8 elements use ARIA attributes their role does not allow, which confuses screen readers.

Image buttons must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

2 dropdowns have no label.

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

Some list items are not inside a list.

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

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

Structured data found ((untyped), Organization, WebPage and WebSite) but with 1 problem, for example “block has no @type”.

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

3 links have no real href, so search engines can't follow them.

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

The homepage links to 214 pages on shiseido.de and 4 external pages.

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.

Your homepage links to /de/de/openSearch, /de/de/openMenu, /de/de/openCart, /de/de/openHome, /de/de/openAccount and /de/de/openContact, which answer with an error. Visitors hit a dead end and search engines drop them.

/de/de/footer and /de/de/aktuelle-angebot have no meta description, so Google writes the search snippet from whatever text it finds.

/de/de/footer, /de/de/must-haves/bestseller, /de/de/aktuelle-angebot, /de/de/geschenkideen-fur-weihnachten-2026, /de/de/must-haves and /de/de/must-haves/neuheiten and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

20 of 40 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 “Error: One or more required elements are missing.”.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

6 links from your homepage to your own site are broken, for example https://www.shiseido.de/de/de/openSearch (410).

http://shiseido.de does not redirect to https, so some visitors land on the insecure version.

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

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

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 1,311 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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 18 cookies, 1 of them by other companies (measured from a US location before any click).

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