Website review, no card needed

opposuits.nl logo

opposuits.nl website review

Visit site (opens in a new tab)Reviewed 7 November 202623 issues · 80 checks

This review found 23 issues worth fixing on opposuits.nl, 6 of them high impact, across 80 checks. The most urgent: main-thread work: 7.1 s. 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.8 s839 msMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 2026998 ms
May 23, 2026970 ms
May 30, 2026954 ms
Jun 6, 2026957 ms
Jun 13, 2026977 ms
Jun 20, 20261.0 s
Jun 27, 20261.0 s
Jul 4, 20261.1 s
Jul 11, 20261.3 s
Jul 18, 20261.5 s
Jul 25, 20261.6 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.4 s
Sep 26, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
150 ms113 msMay 16Oct 31146 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026121 ms
May 23, 2026118 ms
May 30, 2026117 ms
Jun 6, 2026119 ms
Jun 13, 2026121 ms
Jun 20, 2026122 ms
Jun 27, 2026127 ms
Jul 4, 2026127 ms
Jul 11, 2026132 ms
Jul 18, 2026135 ms
Jul 25, 2026136 ms
Aug 1, 2026144 ms
Aug 8, 2026136 ms
Aug 15, 2026135 ms
Aug 22, 2026133 ms
Aug 29, 2026137 ms
Sep 5, 2026139 ms
Sep 12, 2026139 ms
Sep 19, 2026137 ms
Sep 26, 2026127 ms
Oct 3, 2026122 ms
Oct 10, 2026125 ms
Oct 17, 2026128 ms
Oct 24, 2026136 ms
Oct 31, 2026146 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 opposuits.nl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. opposuits.nl at 1.1 s1.1 s
  2. opposuits.nl at 2.1 s2.1 s
  3. opposuits.nl at 3.2 s3.2 s
  4. opposuits.nl at 4.2 s4.2 s
  5. opposuits.nl at 5.3 s5.3 s
  6. opposuits.nl at 6.3 s6.3 s
  7. opposuits.nl at 7.4 s7.4 s
  8. opposuits.nl at 8.4 s8.4 s

Speed

7 to fix73
  • Main-thread work: 7.1 s

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

  • 5,150 HTML elements

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

  • Mobile performance score: 73

    73/100

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

  • Improve image delivery

    650 ms · 283 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Klaviyo and 9gtb.com and others), adding 1.0 MB and 526 ms of main-thread time.

  • Render-blocking requests

    600 ms

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

  • Shopify adds 243 ms

    243 ms

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

  • Reduce unused CSS

    150 ms · 57 KiB

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

  • Reduce unused JavaScript

    146 KiB

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

  • Use efficient cache lifetimes

    128 KiB

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

  • 10 long tasks on the main thread

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

  • Minify JavaScript

    61 KiB

    61 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    29 KiB

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

  • 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: 52 ms

    52 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 6.7 s

    6.7 s

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

  • Time to Interactive: 11.0 s

    11.0 s

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

  • Speed Index: 4.0 s

    4.0 s

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

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

    +18%

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

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

    +13%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 146 ms

    146 ms

    Real visitors wait 146 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.1 s

    1.1 s

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

  • Real-user TTFB: 200 ms

    200 ms

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

  • Total Blocking Time: 154 ms

    154 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.9 MB in 396 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 396 requests on a phone: images 1.3 MB (44), scripts 1.1 MB (186) and fonts 173 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.82 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • 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 9392
  • 14 text elements with low contrast

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

  • 8 images without alt text

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

  • 156 links without text

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

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

    All page content should be contained by landmarks: 9 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 (3 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner 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 banner landmark (1 element)

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

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

1 checks passed
  • 54 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • Meta description is long (169 characters)

    Your meta description is 169 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 350 internal links, 19 external

    The homepage links to 350 pages on opposuits.nl and 19 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “OppoSuits NL”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “OppoSuits | Geweldige Carnavalskleding, Onesies en Kerstpakken”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.opposuits.nl/sitemap.xml.

AI search readiness

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.opposuits.nl/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    6 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 6 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Failed to construct 'URL': Invalid URL”.

2 checks passed
  • Tap targets are thumb-sized

    209 of 212 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 1,323 words of copy

    The homepage carries about 1,323 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop op producttype” and “SHOP KERSTOUTFITS : KERSTOUTFIT”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop op producttype”, “SHOP KERSTOUTFITS : Kerstoutfit” and “SHOP KERST-TRUIEN”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 194 testimonial or review blocks and “1000+ reviews”.

  • Analytics in place

    Analytics detected: LinkedIn Insight and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 1 more (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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies, 1 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.

  • 38 other companies contacted

    Loading the homepage contacts 38 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 opposuits.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Returngo Returns Exchanges · Yotpo Loyalty Rewards · Instafeed · Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · K1 Pre Order · 9gtb.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Cloudflare

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on opposuits.nl, including 10 speed issues, 1 SEO issue and 1 conversion gap. 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