kiabi.com.cy website review

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

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

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

20 files are served with short cache lifetimes, so returning visitors download them again (7.7 MB).

24 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and JSDelivr CDN and others), adding 1.3 MB and 1.0 s of main-thread time.

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

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

Facebook costs a phone 253 ms of main-thread work and 282 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.

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

7 long tasks block the main thread while loading, the longest for 237 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).

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

21 KiB JavaScript is shipped twice across bundles.

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

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 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “With Detachable Scarfs ✨”.

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

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

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

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

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

9 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.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 23.2 MB in 296 requests on a phone: media 13.8 MB (2), images 7.1 MB (88) and scripts 1.3 MB (60). Under 2 MB keeps phones on slow connections fast.

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

1 image further down the page (135 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

1 image (32 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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.

24 images have no alt text, which hurts accessibility and image search.

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

58 form fields have no label, so screen readers announce an empty box and autofill guesses.

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: 9 elements on the page fail this check, rated minor 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 (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 12 characters: “Kiabi Cyprus”. 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 250 pages on kiabi.com.cy and 11 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.cy/customer_authentication/redirect has no <title>, so Google invents the link text in results.

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

https://kiabi.cy/pages/wishlist, https://kiabi.cy/pages/stores, https://kiabi.cy/customer_authentication/redirect, https://kiabi.cy/collections/home, https://kiabi.cy/pages/kiabi-grows-up-with-you and https://kiabi.cy/collections/new-arrivals-women have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://kiabi.cy/collections/unv1000001-women, whose canonical is https://kiabi.cy/collections/women. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

https://kiabi.cy/customer_authentication/redirect, https://kiabi.cy/collections/new-arrivals, https://kiabi.cy/collections/our-top-picks, https://kiabi.cy/collections/unv1000001-women, https://kiabi.cy/collections/unv1000002-men and https://kiabi.cy/collections/plus-size and 3 others took over 3 s to send their HTML from our server.

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

10 images failed to load on a phone, for example https://kiabi.cy/.

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

2 errors were logged to the browser console while the page loaded, for example “Cannot set properties of null (setting 'innerHTML')”.

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

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.

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

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

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