Website review, no card needed

goedvantoen.nl logo

goedvantoen.nl website review

Visit site (opens in a new tab)Reviewed 19 November 202630 issues · 81 checks

This review found 30 issues worth fixing on goedvantoen.nl, 8 of them high impact, across 81 checks. The most urgent: fails Core Web Vitals for real visitors. 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
2.1 s1.6 sMay 30Nov 141.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.6 s
Jun 6, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Nov 14, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
105 ms77 msMay 30Nov 1492 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202685 ms
Jul 11, 202680 ms
Jul 18, 202683 ms
Jul 25, 202683 ms
Aug 1, 202686 ms
Aug 8, 202684 ms
Aug 15, 202690 ms
Aug 22, 202691 ms
Aug 29, 202690 ms
Sep 5, 2026100 ms
Sep 12, 2026100 ms
Sep 19, 2026102 ms
Sep 26, 202694 ms
Nov 14, 202692 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 goedvantoen.nl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix71
  • 4,007 HTML elements

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

  • Mobile performance score: 71

    71/100

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

  • Reduce unused JavaScript

    750 ms · 132 KiB

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

  • Render-blocking requests

    550 ms

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

  • Improve image delivery

    300 ms · 57 KiB

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

  • Reduce unused CSS

    300 ms · 55 KiB

    About 55 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 102 KiB

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

  • Legacy JavaScript

    150 ms · 17 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google CDN, Shopify and seguno.com and others), adding 441 KiB and 107 ms of main-thread time.

  • Duplicated JavaScript

    50 ms · 27 KiB

    27 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

  • Font display

    50 ms

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

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

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 43 ms

    43 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 8.3 s

    8.3 s

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

  • Time to Interactive: 8.3 s

    8.3 s

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

  • Real-user CLS: 0.12

    0.12

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

  • Real-user TTFB: 949 ms

    949 ms

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

  • Speed Index: 3.6 s

    3.6 s

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

  • Cumulative Layout Shift: 0.103

    0.103

    The layout shifts by 0.103 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

    +13%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

5 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 87 ms

    87 ms

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

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

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.50 g

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

4 checks passed
  • Page weight: 1.8 MB in 169 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 169 requests on a phone: other files 753 KiB (85), scripts 572 KiB (66) and fonts 185 KiB (7). That is a lean page.

  • 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 7889
  • Invalid ARIA attributes

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

  • 84 text elements with low contrast

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

  • 14 tap targets too small

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 12 links without text

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

  • 8 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 76 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Eerlijke, duurzame, biologische, scandinavische retro kinderkleding”.

  • Meta description is long (270 characters)

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

  • 2 links crawlers can't follow

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

  • 330 internal links, 6 external

    The homepage links to 330 pages on goedvantoen.nl and 6 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “GOEDvanToen - Eerlijke & biologische kinderkleding en babykleding”.

  • Canonical URL set

    The canonical URL is https://goedvantoen.nl/.

  • Structured data in place

    Structured data found: 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://goedvantoen.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.

  • No llms.txt

    There is no https://goedvantoen.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.

2 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,360 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 7 pages without a meta description

    https://goedvantoen.nl/collections/all, https://goedvantoen.nl/pages/duns-collection-list, https://goedvantoen.nl/collections/adult, https://goedvantoen.nl/collections/basics-nieuw-binnen, https://goedvantoen.nl/collections/duns-sweden-nieuw-binnen and https://goedvantoen.nl/collections/duns-sweden-adult-nieuw-binnen and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages slow to respond

    https://goedvantoen.nl/collections/all and https://goedvantoen.nl/collections/adult took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • 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 8 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 “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    14 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 539 words of copy

    The homepage carries about 539 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “STAPEL & SHOP”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop now”, “STAPEL & SHOP” and “Shop Mòi”.

  • 11 short forms

    11 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 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.

  • 14 other companies contacted

    Loading the homepage contacts 14 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 goedvantoen.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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Seguno Popups · Quantity Price Breaks Limit Purchase · nfcube.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

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

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 goedvantoen.nl, including 13 speed issues, 3 SEO issues and 2 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