keychron.it website review

The page goes through 2 redirects before it starts loading, costing about 6.5 s. Link and advertise the final URL directly.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.4 s faster on a phone.

Google Tag Manager costs a phone 1.2 s of main-thread work and 1.5 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.

Your mobile performance score is 45. 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.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and seel.com and others), adding 3.0 MB and 1.8 s of main-thread time.

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

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

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

Shopify costs a phone 330 ms of main-thread work and 718 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.

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

About 27 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

seel.com costs a phone 214 ms of main-thread work and 522 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.

Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need.

21 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 14.6 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 27.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.

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 150 ms to 191 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your homepage downloads 6.4 MB in 542 requests on a phone: scripts 3.2 MB (175), images 1.3 MB (89) and other files 1.2 MB (234). Under 2 MB keeps phones on slow connections fast.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is 90 characters, so Google will cut it off around 60: “Keychron | Tastiere meccaniche personalizzate per Mac, Windows e telefoni – Keychron Italy”.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 801 pages on keychron.it and 0 external pages.

Your homepage links to https://keychron.it/products/keychron-v3-max-qmk-wireless-custom-mechanical-keyboard-iso-layout-collection, which answers with an error. Visitors hit a dead end and search engines drop it.

https://keychron.it/collections/tuttiiprodotti has no meta description, so Google writes the search snippet from whatever text it finds.

https://keychron.it/collections/tuttiiprodotti, https://keychron.it/collections/nuoviarrivi, https://keychron.it/products/keychron-k1-max-qmk-wireless-custom-mechanical-keyboard-iso-layout-collection, https://keychron.it/products/keychron-k3-max-qmk-via-wireless-custom-mechanical-keyboard-iso-layout-collection, https://keychron.it/products/keychron-k5-max-qmk-wireless-custom-mechanical-keyboard-iso-layout-collection and https://keychron.it/products/keychron-v6-max-qmk-via-wireless-custom-mechanical-keyboard-us-ansi-layout and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 (Forbidden)”.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Klaviyo (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 7 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 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.