orbitkey.com website review

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

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

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,621 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 Shopify and others), adding 31.0 MB and 1.2 s of main-thread time.

Shopify costs a phone 109 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 983 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

Google Tag Manager costs a phone 570 ms of main-thread work and 709 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 300 ms faster on a phone.

Klaviyo costs a phone 126 ms of main-thread work and 317 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 107 ms of main-thread work and 294 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.

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

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

122 KiB could be saved by minifying JavaScript.

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

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

1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 129 ms to 144 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 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 34.5 MB in 331 requests on a phone: media 30.8 MB (5), scripts 2.2 MB (115) and other files 847 KiB (125). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 9.78 g of CO₂e: 1173.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.

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

All page content should be contained by landmarks: 88 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.

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

Headings should not be empty: 2 elements on the page fail 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.

44 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 403 pages on orbitkey.com and 13 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.

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

/collections/all-products and /pages/orbitkey-professional-range have no meta description, so Google writes the search snippet from whatever text it finds.

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

/collections/all-key-organisers, /collections/all-productivity, /collections/everyday-carry, /collections/all-products, /products/clip-on-glasses-pouch and /products/crossbody-bag-strap 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 118 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…”).

5 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.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

orbitkey.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

DMARC is set to p=none, so mail pretending to be orbitkey.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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