kiokii.com website review

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

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

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

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

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

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

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

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

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

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

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

About 78 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.

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

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

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

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

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.

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

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

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

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Kiokii and...”.

Real visitors wait 229 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

6 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 6.6 MB in 477 requests on a phone: images 2.7 MB (99), scripts 2.1 MB (202) and other files 993 KiB (122). Under 2 MB keeps phones on slow connections fast.

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

7 tap targets are too small or too close together to hit reliably with a finger.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (5 elements).

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Your <h1> is empty.

The homepage links to 591 pages on kiokii.com and 17 external pages.

https://kiokii.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://kiokii.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://kiokii.com/en-us, https://kiokii.com/en-us/pages/store-locator, https://kiokii.com/en-us/collections/vendors, https://kiokii.com/en-us/collections/types and https://kiokii.com/collections/gift-sets all use the title “Kiokii and... | Your K-Beauty & Asian Skincare Destination”. Search engines can't tell which page to show for a search, so each competes with the others.

https://kiokii.com/en-us/pages/faq, https://kiokii.com/customer_authentication/redirect, https://kiokii.com/en-us/pages/wishlist and https://kiokii.com/pages/holiday-gift-guide have no meta description, so Google writes the search snippet from whatever text it finds.

https://kiokii.com/en-us/pages/store-locator, https://kiokii.com/en-us/collections/vendors, https://kiokii.com/en-us/collections/types and https://kiokii.com/collections/gift-sets use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://kiokii.com/en-us/pages/store-locator, whose canonical is https://kiokii.com/en-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://kiokii.com/en-us/collections/kiokii-beauty-advent-calendar-2026, https://kiokii.com/en-us/products/medicube-vanilla-fragrance-duo, https://kiokii.com/en-us/products/biodance-collagen-peptide-liposome-bubble-booster-95ml, https://kiokii.com/en-us/products/kiokii-advent-calendar-2026, https://kiokii.com/en-us/products/judydoll-liquid-highlighter-contour-duo-4-8g-2-colors and https://kiokii.com/en-us/products/flower-knows-strawberry-cupid-collection-perfume and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 149 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: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

The homepage has only about 45 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The page uses urgency cues (a countdown or limited-time wording).

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