blacktailor.store website review

6 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.6 s faster on a phone.

About 220 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Shopify, omnisnippet1.com and JSDelivr CDN and others), adding 1.2 MB and 357 ms of main-thread time.

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

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

Shopify costs a phone 160 ms of main-thread work and 515 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 30 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

1 long task block the main thread while loading, the longest for 55 ms. During a long task the page ignores taps.

4 KiB could be saved by minifying JavaScript.

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 30.1 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 30.9 s. Good is under 3.8 s.

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your homepage downloads 8.4 MB in 554 requests on a phone: images 5.7 MB (109), other files 1.3 MB (223) and scripts 1.1 MB (189). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.2 MB together. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example DSCF1296_copy_bbeedaaa-7182-4cb9-9b9f-a289d75e7c89.jpg at 2,250 px wide, shown at 390 px. Resized copies would save about 839 KiB.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

1 image has 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.

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 11 characters: “BLACKTAILOR”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 46 characters: “The official website of Blacktailor. EST 2018.”. 70 to 160 characters is enough to sell the click.

The homepage links to 188 pages on blacktailor.store and 8 external pages.

https://blacktailor.com/collections/back-in-stock, https://blacktailor.com/collections/drift, https://blacktailor.com/collections/experimental, https://blacktailor.com/collections/bottoms, https://blacktailor.com/collections/t-tapered and https://blacktailor.com/collections/v-skinny and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-static.okendo.io/styles/main.min.css' from origin 'https://blacktailor.com' ha…”.

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

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