keychronjp.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and varify.io and others), adding 1.2 MB and 902 ms of main-thread time.

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

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

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

About 321 KiB of JavaScript is downloaded but never used on this page.

Google Tag Manager costs a phone 272 ms of main-thread work and 321 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 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.

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

12 KiB could be saved by minifying JavaScript.

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

8 KiB JavaScript is shipped twice across bundles.

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

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

Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Keychron G3 ウルトラライトワイヤレスマウス フロステッドグレー”.

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

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

Scripts block taps and scrolling for 230 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 128 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.5 MB in 389 requests on a phone: scripts 1.2 MB (144), images 1.0 MB (59) and other files 878 KiB (138). Under 2 MB keeps phones on slow connections fast.

K6U-SE-desc-09.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (36 KiB) is 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.

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

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

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

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

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

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

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

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

Your meta description is only 66 characters: “Keychron公式。Mac・Windows・iOS・Androidすべてに対応した、高性能ワイヤレスメカニカルキーボードをご提供。”. 70 to 160 characters is enough to sell the click.

Your <h1> is empty.

The homepage links to 379 pages on keychronjp.com and 24 external pages.

There is no https://keychron.jp/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.jp/collections/all-products and https://keychron.jp/collections/all-keyboards have no meta description, so Google writes the search snippet from whatever text it finds.

https://keychron.jp/pages/showroom, https://keychron.jp/collections/all-products, https://keychron.jp/collections/all-keyboards and https://keychron.jp/collections/mice-collection have no <h1> headline, so visitors and search engines get no clear main topic.

https://keychron.jp/collections/all-keyboards took over 3 s to send its HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'appendChild')”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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