manebi.com website review

About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.9 s faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and tabarn.app and others), adding 3.2 MB and 2.1 s of main-thread time.

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

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

About 91 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

tabarn.app costs a phone 325 ms of main-thread work and 131 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.

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

Klaviyo costs a phone 231 ms of main-thread work and 373 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.

loloyal.com costs a phone 210 ms of main-thread work and 393 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.

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

56 KiB could be saved by minifying JavaScript.

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

9 KiB could be saved by minifying CSS.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 32.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Get 15% off”.

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

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

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

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

The first text or image appears after 2.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' largest content (lcp) went from 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 36.2 MB in 574 requests on a phone: media 26.6 MB (4), scripts 4.3 MB (151) and images 3.2 MB (40). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example M46KV_4.jpg at 390 px wide, shown at 92 px. Resized copies would save about 89 KiB.

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

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

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

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

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

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

Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//manebi.com/cdn/shop/t/308/assets/logo.png?v=185532")”.

The homepage links to 229 pages on manebi.com and 10 external pages.

There is no https://manebi.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://manebi.com/collections/new-arrivals-fw26-women, https://manebi.com/collections/new-arrivals-fw26-womens-shoes, https://manebi.com/collections/new-arrivals-womens-clothing-fw26, https://manebi.com/collections/new-arrivals-fw26-womens-bags, https://manebi.com/collections/new-arrivals-mens and https://manebi.com/collections/new-arrivals-fw26-mens-clothing and 1 other use the same meta description. A description written for each page earns more clicks.

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

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 28 cookies (measured from a US location before any click).

Loading the homepage contacts 55 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.