kiabi.eg website review

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

15 images could be 670 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.

About 324 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

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

8 third-party services load with your homepage (Clarity, Facebook and pop-convert.com and others), adding 949 KiB and 607 ms of main-thread time.

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

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

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

Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

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

11 KiB could be saved by minifying JavaScript.

6 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 19.2 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 19.5 s. Good is under 3.8 s.

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

The first text or image appears after 4.5 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 130 ms to 156 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

15 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' largest content (lcp) went from 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.8 MB in 243 requests on a phone: images 1.8 MB (46), scripts 964 KiB (60) and other files 760 KiB (102). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example BENTO-BIG-min.jpg at 600 px wide, shown at 163 px. Resized copies would save about 110 KiB.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

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

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

Your title is only 11 characters: “Kiabi Egypt”. 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 110 pages on kiabi.eg 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.eg/customer_authentication/redirect has no <title>, so Google invents the link text in results.

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

https://kiabi.eg/collections/buy-1-get-40-off-on-the-second-item, https://kiabi.eg/pages/wishlist, https://kiabi.eg/pages/stores, https://kiabi.eg/customer_authentication/redirect, https://kiabi.eg/collections/new-in-1 and https://kiabi.eg/collections/sale and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://kiabi.eg/pages/wishlist, https://kiabi.eg/customer_authentication/redirect and https://kiabi.eg/pages/kiabi-grows-up-with-you have no <h1> headline, so visitors and search engines get no clear main topic.

https://kiabi.eg/customer_authentication/redirect, https://kiabi.eg/collections/baby, https://kiabi.eg/collections/mens-womens-plus-size-clothes, https://kiabi.eg/collections/ingerie and https://kiabi.eg/collections/sale took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 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 ()”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 473 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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 7 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.