kiabi.com.mt website review

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

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

2 images could be 57 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

6 third-party services load with your homepage (Shopify, nfcube.com and goodays.co and others), adding 236 KiB and 67 ms of main-thread time.

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

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

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 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

Your homepage downloads 2.2 MB in 154 requests on a phone: media 842 KiB (1), other files 613 KiB (66) and images 401 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.63 g of CO₂e: 76.1 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.

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

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

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

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 40 pages on kiabi.com.mt 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.com.mt/pages/stores, https://kiabi.com.mt/pages/wishlist, https://kiabi.com.mt/collections/bestsellers-women, https://kiabi.com.mt/collections/bestsellers-men, https://kiabi.com.mt/collections/bestsellers-girls and https://kiabi.com.mt/collections/bestsellers-boys and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://kiabi.com.mt/pages/wishlist, https://kiabi.com.mt/collections/bestsellers-women, https://kiabi.com.mt/collections/bestsellers-men, https://kiabi.com.mt/collections/bestsellers-girls, https://kiabi.com.mt/collections/bestsellers-boys and https://kiabi.com.mt/collections/bestsellers-baby and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://kiabi.com.mt/pages/stores, https://kiabi.com.mt/collections/bestsellers-women, https://kiabi.com.mt/collections/bestsellers-men and https://kiabi.com.mt/collections/bestsellers-girls took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://kiabi.com.mt/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.

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

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

Opening the homepage sets 2 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.