Website review, no card needed

passion4all.nl logo

passion4all.nl website review

Visit site (opens in a new tab)Reviewed 11 November 202630 issues · 71 checks

This review found 30 issues worth fixing on passion4all.nl, 8 of them high impact, across 71 checks. The most urgent: render-blocking 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

Full-page screenshot of passion4all.nl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. passion4all.nl at 0.4 s0.4 s
  2. passion4all.nl at 0.8 s0.8 s
  3. passion4all.nl at 1.1 s1.1 s
  4. passion4all.nl at 1.5 s1.5 s
  5. passion4all.nl at 1.9 s1.9 s
  6. passion4all.nl at 2.3 s2.3 s
  7. passion4all.nl at 2.6 s2.6 s
  8. passion4all.nl at 3.0 s3.0 s

Speed

7 to fix74
  • Render-blocking requests

    1.1 s

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

  • Improve image delivery

    450 ms · 730 KiB

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

  • Mobile performance score: 74

    74/100

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

  • Reduce unused JavaScript

    780 ms · 124 KiB

    About 124 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 780 ms faster on a phone.

  • Use efficient cache lifetimes

    600 ms · 87 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (jwwb.nl, Google Tag Manager and Plausible and others), adding 1.7 MB and 192 ms of main-thread time.

  • jwwb.nl adds 115 ms

    115 ms

    jwwb.nl costs a phone 115 ms of main-thread work and 1.5 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.

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    26 KiB

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

  • Legacy JavaScript

    14 KiB

    Polyfills for old browsers add 14 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.

2 checks passed
  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 450 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

3 to fix69
  • Largest Contentful Paint: 6.1 s

    6.1 s

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

  • Time to Interactive: 6.1 s

    6.1 s

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

  • Speed Index: 3.7 s

    3.7 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Total Blocking Time: 144 ms

    144 ms

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

  • Cumulative Layout Shift: 0.015

    0.015

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

Images and page weight

3 to fix81
  • An image on the first screen is lazy-loaded

    image-high-k11she.png 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).

  • 7 images below the first screen load straight away

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

  • 4 images far larger than shown

    180 KiB

    4 images are downloaded at several times the size a phone draws them, for example bs01-high-7u2mh2.jpg at 1,171 px wide, shown at 327 px. Resized copies would save about 180 KiB.

  • About 0.5 g of CO₂ per visit

    0.48 g

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

2 checks passed
  • Page weight: 1.7 MB in 39 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 39 requests on a phone: images 1.0 MB (13), scripts 351 KiB (12) and fonts 225 KiB (4). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 8591
  • ARIA commands must have an accessible name (246 elements)

    ARIA commands must have an accessible name: 246 elements on the page fail this check, rated serious by axe-core.

  • Images must have alternative text (10 elements)

    Images must have alternative text: 10 elements on the page fail this check, rated critical by axe-core.

  • 95 tap targets too small

    95 tap targets are too small or too close together to hit reliably with a finger.

  • 15 text elements with low contrast

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

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

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 9283
  • Title is short (13 characters)

    Your title is only 13 characters: “Passion 4 All”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (43 characters)

    Your meta description is only 43 characters: “Leuk kinderen, dames, baby kleren te vinden”. 70 to 160 characters is enough to sell the click.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “welkom,”). One clear main headline is easier for people and search engines.

  • 43 internal links, 239 external

    The homepage links to 43 pages on passion4all.nl and 239 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.passion4all.nl/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix83
  • 2 linked pages hidden from search

    https://www.passion4all.nl/winkelwagen and https://www.passion4all.nl/alg-voorwaarden-retour-formulier are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 5 pages without a meta description

    https://www.passion4all.nl/winkelwagen, https://www.passion4all.nl/evenementen, https://www.passion4all.nl/alg-voorwaarden-retour-formulier, https://www.passion4all.nl/kleding and https://www.passion4all.nl/kleding/accessoires-1 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.passion4all.nl/reviews, https://www.passion4all.nl/contact, https://www.passion4all.nl/evenementen, https://www.passion4all.nl/tabel-kleding-maten, https://www.passion4all.nl/bestellen and https://www.passion4all.nl/alg-voorwaarden-retour-formulier and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 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 a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 150 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of null (reading 'addEventListener')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • 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.

  • Only about 180 words

    The homepage has only about 180 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and Plausible.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (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.

  • 6 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics | Plausible
Hosting
Google Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on passion4all.nl, including 10 speed issues, 3 SEO issues 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