koifootwear.com website review

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

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

6 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and shgcdn3.com and others), adding 1.1 MB and 792 ms of main-thread time.

Google Tag Manager costs a phone 444 ms of main-thread work and 500 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 365 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

8 KiB could be saved by minifying CSS.

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.

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

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

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

evanescence_koi_cdplayer_v2_portrait.gif weighs 2.0 MB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.9 MB in 105 requests on a phone: images 2.2 MB (10), scripts 1.2 MB (64) and fonts 248 KiB (7). Under 2 MB keeps phones on slow connections fast.

2 images (2.2 MB) are 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.

e6e342ff8a984a4eb3deaf0e5c4d85fe.thumbnail.0000000000.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.

Headings skip levels (h3 → 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 meta description is 192 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 142 pages on koifootwear.com and 8 external pages.

https://www.koifootwear.com/collections/view-all-new-in, https://www.koifootwear.com/collections/new-in-footwear, https://www.koifootwear.com/collections/womens-footwear, https://www.koifootwear.com/collections/mary-janes, https://www.koifootwear.com/collections/womens-boots and https://www.koifootwear.com/collections/womens-shoes and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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 233 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, Google Tag Manager, Klaviyo and Microsoft Clarity (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 12 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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.