orbitkey.jp website review

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

A phone's processor spends 6.0 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 4,702 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

Shopify costs a phone 92 ms of main-thread work and 29.4 MB 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 742 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

Klaviyo costs a phone 135 ms of main-thread work and 311 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.

okendo.io costs a phone 120 ms of main-thread work and 293 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.

122 KiB could be saved by minifying JavaScript.

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

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

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

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

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 17.8 s. Good is under 3.8 s.

Your largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your Everyday, Organised”.

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

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

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

1 image 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' largest content (lcp) went from 1.9 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 34.5 MB in 304 requests on a phone: media 30.8 MB (5), scripts 1.9 MB (110) and other files 758 KiB (104). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

The homepage links to 391 pages on orbitkey.jp and 15 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.

https://www.orbitkey.asia/collections/all-key-organisers and https://www.orbitkey.asia/collections/key-organiser all use the title “Key Organizers & Holders | Secure Locking - Orbitkey – Orbitkey Asia”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.orbitkey.asia/collections/all-products, https://www.orbitkey.asia/pages/orbitkey-professional-range and https://www.orbitkey.asia/collections/key-organiser-pro have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.orbitkey.asia/collections/all-key-organisers and https://www.orbitkey.asia/collections/key-organiser use the same meta description. A description written for each page earns more clicks.

https://www.orbitkey.asia/collections/all-key-organisers, https://www.orbitkey.asia/collections/all-productivity, https://www.orbitkey.asia/collections/everyday-carry, https://www.orbitkey.asia/collections/all-products, https://www.orbitkey.asia/products/essentials-pouch-trio and https://www.orbitkey.asia/products/foldable-tote-bag and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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