inokim.com website review

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

About 553 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.8 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and Klaviyo and others), adding 1.0 MB and 773 ms of main-thread time.

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

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

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

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

About 46 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 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

13 KiB could be saved by minifying CSS.

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.

2 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 16.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “INOKIM OX under the Manhattan Bridge, Dumbo, New York”.

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

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

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

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

Scripts block taps and scrolling for 258 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' 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 3.6 MB in 323 requests on a phone: scripts 1.3 MB (70), other files 1.0 MB (211) and images 815 KiB (24). Under 2 MB keeps phones on slow connections fast.

4 images further down the page (95 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

2 elements have a tabindex above 0, which scrambles the keyboard order.

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

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

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

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

<td> elements in a large <table> do not have table headers. (1 element).

Your title is 67 characters, so Google will cut it off around 60: “INOKIM — Premium Electric Scooters Since 2009 · Global Distributors”.

There are 2 <h1> headlines (“INOKIM NYC” and “Built better.”). One clear main headline is easier for people and search engines.

Your meta description is 189 characters; Google truncates after about 160, so the end of your pitch is cut.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 43 pages on inokim.com and 18 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://inokim.com/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://inokim.com/policies/privacy-policy has no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 6 pages linked from your homepage and read each the way a search engine does.

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187030038&Ver=2&mid=19320798-e3bb-4bb9-8085-e2a4af9d26a4&bo=1&sid=af172a80dd6211f185ab5d16f5801555&vid=af175660dd6211f1b32df1ff584b3341&vids=1&msclkid=N&pi=918639831&l.

4 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

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

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