keychron.ch website review

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

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

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

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

8 third-party services load with your homepage (galleryjs.io, Google Tag Manager and Shopify and others), adding 1.1 MB and 1.1 s of main-thread time.

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

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

galleryjs.io costs a phone 517 ms of main-thread work and 307 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.

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

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

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

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

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

3 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

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

Your homepage downloads 7.5 MB in 468 requests on a phone: images 5.4 MB (272), scripts 1.3 MB (82) and other files 684 KiB (85). Under 2 MB keeps phones on slow connections fast.

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

219 elements hidden from screen readers can still receive keyboard focus.

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Your title is 67 characters, so Google will cut it off around 60: “Keychron Switzerland | Custom Keyboards for Mac, Windows and Phones”.

There are 2 <h1> headlines (“” and “Looking for a Mechanical Keyboard?”). One clear main headline is easier for people and search engines.

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

The homepage links to 827 pages on keychron.ch and 24 external pages.

There is no https://keychron.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://keychron.ch/collections/all-products, https://keychron.ch/collections/q-ultra-series, https://keychron.ch/collections/keychron-q-max-series, https://keychron.ch/collections/keychron-q-pro-series, https://keychron.ch/collections/keychron-q-series-keyboard and https://keychron.ch/collections/k-ultra-series and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://keychron.ch/collections/all-products, https://keychron.ch/collections/q-ultra-series, https://keychron.ch/collections/keychron-q-max-series, https://keychron.ch/collections/keychron-q-pro-series, https://keychron.ch/collections/keychron-q-series-keyboard and https://keychron.ch/collections/k-ultra-series 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 196 found) and read each the way a search engine does.

3 errors were logged to the browser console while the page loaded, for example “Unexpected token ','”.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Reddit Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 11 cookies, 1 of them by other companies (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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.