kiabi.am website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, pop-convert.com and Google CDN and others), adding 502 KiB and 213 ms of main-thread time.

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

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

1 image could be 11 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.

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

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

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

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

3 images 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' tap response (inp) went from 79 ms to 83 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 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.6 MB in 152 requests on a phone: media 757 KiB (1), other files 679 KiB (81) and images 544 KiB (20). Under 2 MB keeps phones on slow connections fast.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 21 characters: “KIABI – Kiabi Arménie”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 31 pages on kiabi.am and 3 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://kiabi.am/pages/wishlist, https://kiabi.am/collections/bestsellers-girls, https://kiabi.am/collections/bestsellers-baby, https://kiabi.am/pages/kiabi-grows-up-with-you and https://kiabi.am/pages/about-us have no meta description, so Google writes the search snippet from whatever text it finds.

https://kiabi.am/pages/wishlist, https://kiabi.am/collections/bestsellers-girls, https://kiabi.am/collections/bestsellers-baby, https://kiabi.am/pages/kiabi-grows-up-with-you and https://kiabi.am/pages/about-us have no <h1> headline, so visitors and search engines get no clear main topic.

https://kiabi.am/pages/wishlist and https://kiabi.am/pages/about-us have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://kiabi.am/collections/bestsellers-girls, https://kiabi.am/collections/bestsellers-baby and https://kiabi.am/pages/kiabi-grows-up-with-you took over 3 s to send their HTML from our server.

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

3 images failed to load on a phone, for example https://kiabi.am/Liquid%20error%20(sections/image-with-link%20line%2055):%20invalid%20url%20input.

4 errors were 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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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