suspiciousantwerp.com website review

A phone's processor spends 7.5 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,128 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

8 third-party services load with your homepage (monkcommerce.app, Google Tag Manager and Shopify and others), adding 1.3 MB and 661 ms of main-thread time.

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

About 510 KiB of JavaScript is downloaded but never used on this page.

monkcommerce.app costs a phone 171 ms of main-thread work and 565 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 121 ms of main-thread work and 353 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.

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

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

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

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

4 KiB JavaScript is shipped twice across bundles.

3 KiB could be saved by minifying CSS.

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

Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 105 ms to 141 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 1.4 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your homepage downloads 10.0 MB in 542 requests on a phone: images 7.3 MB (137), scripts 1.3 MB (91) and other files 1.2 MB (298). Under 2 MB keeps phones on slow connections fast.

6 images (868 KiB) 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.

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

ARIA attributes must conform to valid values: 48 elements on the page fail this check, rated critical by axe-core.

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

1 button has no accessible name, so screen readers announce just “button”.

All page content should be contained by landmarks: 10 elements on the page fail 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.

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h4 and h2 → h4), 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 266 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 235 pages on suspiciousantwerp.com and 36 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.suspiciousantwerp.com/collections/outerwear, https://www.suspiciousantwerp.com/collections/bestsellers, https://www.suspiciousantwerp.com/collections/restocked, https://www.suspiciousantwerp.com/collections/womens, https://www.suspiciousantwerp.com/collections/longsleeves and https://www.suspiciousantwerp.com/collections/knitwear and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.suspiciousantwerp.com/collections/current-availabilities, https://www.suspiciousantwerp.com/collections/new-in, https://www.suspiciousantwerp.com/collections/outerwear, https://www.suspiciousantwerp.com/collections/bestsellers, https://www.suspiciousantwerp.com/collections/restocked and https://www.suspiciousantwerp.com/collections/womens and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

1 error was logged to the browser console while the page loaded, for example “Missing data-related-products attribute on color dots container [node HTMLDivElement]”.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (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 22 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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.