pkz.ch website review

Other Google APIs/SDKs costs a phone 4.6 s of main-thread work and 4.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (Other Google APIs/SDKs, Google Tag Manager and Cloudflare CDN and others), adding 4.9 MB and 5.0 s of main-thread time.

38 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).

About 865 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 860 ms faster on a phone.

9 images could be 386 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

Google Tag Manager costs a phone 267 ms of main-thread work and 188 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.

Adobe TypeKit costs a phone 7 ms of main-thread work and 543 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.

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

About 16 KiB of CSS is downloaded but never applied on this page.

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

5 KiB could be saved by minifying JavaScript.

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

Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

The layout shifts by 0.51 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

29 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-31, real Chrome visitors' tap response (inp) went from 137 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 6.0 MB in 83 requests on a phone: other files 3.3 MB (17), scripts 1.5 MB (18) and images 803 KiB (32). Under 2 MB keeps phones on slow connections fast.

5 images (257 KiB) 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.

2 images further down the page (73 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (4 elements).

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

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

ARIA input fields do not have accessible names (3 elements).

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Some list items are not inside a list.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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.

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

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

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

The homepage links to 232 pages on pkz.ch and 3 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 https://www.pkz.ch/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.

https://www.pkz.ch/de, https://www.pkz.ch/de/changelanguage/2 and https://www.pkz.ch/de/changelanguage/3 all use the title “PKZ.CH | Fashion Online-Shop | Grosse Auswahl an Top-Marken”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.pkz.ch/de/changelanguage/2, https://www.pkz.ch/de/changelanguage/3, https://www.pkz.ch/de/wishlist, https://www.pkz.ch/de/nachhaltigkeit, https://www.pkz.ch/de/new-bekleidung-damen and https://www.pkz.ch/de/new-schuhe-damen and 4 others use the same meta description. A description written for each page earns more clicks.

https://www.pkz.ch/de/changelanguage/2 and https://www.pkz.ch/de/changelanguage/3 have no <h1> headline, so visitors and search engines get no clear main topic.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

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

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

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 272 words of visible text.

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