kihanan.com website review

75 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (Shopify, JSDelivr CDN and amp-cdn.tokyo and others), adding 370 KiB and 151 ms of main-thread time.

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

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

11 KiB could be saved by minifying JavaScript.

About 11 KiB of CSS is downloaded but never applied on this page.

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

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

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

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

The layout shifts by 0.449 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 39.8 MB in 825 requests on a phone: images 34.5 MB (664), fonts 4.0 MB (2) and other files 696 KiB (69). Under 2 MB keeps phones on slow connections fast.

S__127729677.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).

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

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

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

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

The homepage links to 984 pages on kihanan.com and 7 external pages.

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

9 images failed to load on a phone, for example https://kihanan.com/Liquid%20error%20(snippets/responsive-image%20line%2057):%20Width%20must%20be%20between%201%20and%205760.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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