Website review, no card needed

suitableshop.nl logo

suitableshop.nl website review

Visit site (opens in a new tab)Reviewed 22 October 202640 issues · 90 checks

This review found 40 issues worth fixing on suitableshop.nl, 11 of them high impact, across 90 checks. The most urgent: page weight: 18.6 MB in 186 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.3 s784 msMay 2Oct 171.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 2026904 ms
May 9, 2026906 ms
May 16, 2026890 ms
May 23, 2026909 ms
May 30, 2026909 ms
Jun 6, 2026917 ms
Jun 13, 2026933 ms
Jun 20, 2026898 ms
Jun 27, 2026897 ms
Jul 4, 2026908 ms
Jul 11, 2026916 ms
Jul 18, 2026939 ms
Jul 25, 2026955 ms
Aug 1, 2026945 ms
Aug 8, 2026918 ms
Aug 15, 2026881 ms
Aug 22, 2026868 ms
Aug 29, 2026844 ms
Sep 5, 2026853 ms
Sep 12, 2026866 ms
Sep 19, 2026885 ms
Sep 26, 2026956 ms
Oct 3, 20261.1 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
140 ms108 msMay 2Oct 17136 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026113 ms
May 9, 2026112 ms
May 16, 2026112 ms
May 23, 2026113 ms
May 30, 2026114 ms
Jun 6, 2026116 ms
Jun 13, 2026117 ms
Jun 20, 2026115 ms
Jun 27, 2026118 ms
Jul 4, 2026119 ms
Jul 11, 2026120 ms
Jul 18, 2026121 ms
Jul 25, 2026121 ms
Aug 1, 2026126 ms
Aug 8, 2026127 ms
Aug 15, 2026129 ms
Aug 22, 2026129 ms
Aug 29, 2026127 ms
Sep 5, 2026126 ms
Sep 12, 2026125 ms
Sep 19, 2026126 ms
Sep 26, 2026129 ms
Oct 3, 2026134 ms
Oct 10, 2026135 ms
Oct 17, 2026136 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of suitableshop.nl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. suitableshop.nl at 0.6 s0.6 s
  2. suitableshop.nl at 1.3 s1.3 s
  3. suitableshop.nl at 1.9 s1.9 s
  4. suitableshop.nl at 2.6 s2.6 s
  5. suitableshop.nl at 3.2 s3.2 s
  6. suitableshop.nl at 3.9 s3.9 s
  7. suitableshop.nl at 4.5 s4.5 s
  8. suitableshop.nl at 5.2 s5.2 s

Speed

8 to fix67
  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, Vimeo and Azure Web Services and others), adding 16.3 MB and 459 ms of main-thread time.

  • Vimeo adds 130 ms

    130 ms

    Vimeo costs a phone 130 ms of main-thread work and 15.9 MB 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.

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67 (desktop: 67). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    566 KiB

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

  • Use efficient cache lifetimes

    200 ms · 274 KiB

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

  • Render-blocking requests

    450 ms

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

  • Main-thread work: 3.0 s

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

  • 1,902 HTML elements

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

  • Improve image delivery

    150 ms · 134 KiB

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

  • Legacy JavaScript

    150 ms · 21 KiB

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

  • 9 long tasks on the main thread

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

  • Reduce unused CSS

    23 KiB

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

  • Minify JavaScript

    21 KiB

    21 KiB could be saved by minifying JavaScript.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

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

1 checks passed
  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Time to Interactive: 20.7 s

    20.7 s

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

  • Largest Contentful Paint: 6.6 s

    6.6 s

    Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 7.3 s

    7.3 s

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

  • Real-user LCP: 2.5 s

    2.5 s

    Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) got 20% slower for real visitors

    +20%

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

  • Largest content (LCP) got 34% slower for real visitors

    +34%

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

  • 61 images without width and height

    61 images have no width and height attributes, so the layout jumps as each one loads.

  • First Contentful Paint: 2.0 s

    2.0 s

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

6 checks passed
  • Real-user INP: 129 ms

    129 ms

    Real visitors wait 129 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 620 ms

    620 ms

    Real visitors wait 620 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 150 ms

    150 ms

    Scripts block the page for only 150 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 18.6 MB in 186 requests

    18.6 MB

    Your homepage downloads 18.6 MB in 186 requests on a phone: other files 15.4 MB (51), scripts 1.6 MB (38) and images 1.3 MB (59). Under 2 MB keeps phones on slow connections fast.

  • 14 images in older formats

    14 images (626 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.

  • 3 images below the first screen load straight away

    3 images further down the page (119 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 5.3 g of CO₂ per visit

    5.27 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8090
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 2 text elements with low contrast

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

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

  • All page content should be contained by landmarks (17 elements)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 8 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 177 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • Open Graph partly set

    Open Graph is missing og:title, so shared links fall back to guesses.

  • 458 internal links, 5 external

    The homepage links to 458 pages on suitableshop.nl and 5 external pages.

7 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “Herenmode shop je online bij Suitable: Smart Choice / Suitable Style! Beste herenmode webshop (Shopping Awards) ✔ 28 wi…”.

  • One H1 headline

    Your main headline reads: “Suitable, herenmode voor elk moment”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Suitable Herenmode: Al 4 jaar op rij de beste herenmode shop”.

  • Canonical URL set

    The canonical URL is https://www.suitableshop.nl/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.suitableshop.nl/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • Opted out of AI training for 1 crawler

    robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,603 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.suitableshop.nl/llms.txt (5 KiB, 0 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.suitableshop.nl/winkelwagen is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.suitableshop.nl/winkelwagen has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

5 to fixGoogle 5869
  • 1 broken image

    1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=e658300e-0eff-4aa3-91a8-0d1d1d314388&referrer=&landingpage=https%3A%2F%2Fwww.suitableshop.nl%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS.

  • 81 small tap targets

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

  • 3 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • No call to action on the first screen

    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 social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 587 words of copy

    The homepage carries about 587 words of visible text.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Suited for Fall | Shop nu >”, “Shop the look” and “Shop the lookLaat je inspireren”.

  • 5 short forms

    5 short forms (4 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager 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.

  • 29 cookies set on arrival

    29

    Opening the homepage sets 29 cookies, 3 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 27 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at suitableshop.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on suitableshop.nl, including 17 speed issues, 1 SEO issue and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25