Programmable

Website review, no card needed

geboorteplein.nl logo

geboorteplein.nl website review

Visit site (opens in a new tab)Reviewed 11 November 202637 issues · 86 checks

This review found 37 issues worth fixing on geboorteplein.nl, 12 of them high impact, across 86 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

Site score

76C

Closest competitors among WooCommerce stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
3.7 s3.2 sMay 23Nov 73.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.3 s
May 30, 20263.3 s
Jun 6, 20263.3 s
Jun 13, 20263.2 s
Jun 20, 20263.3 s
Jun 27, 20263.3 s
Jul 4, 20263.3 s
Jul 11, 20263.4 s
Jul 18, 20263.4 s
Jul 25, 20263.5 s
Aug 1, 20263.5 s
Aug 8, 20263.6 s
Aug 15, 20263.7 s
Aug 22, 20263.7 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.5 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.5 s
Oct 17, 20263.5 s
Oct 24, 20263.5 s
Oct 31, 20263.5 s
Nov 7, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
117 ms90 msMay 23Nov 7114 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202694 ms
May 30, 202693 ms
Jun 6, 202696 ms
Jun 13, 202697 ms
Jun 20, 202695 ms
Jun 27, 202697 ms
Jul 4, 202695 ms
Jul 11, 202694 ms
Jul 18, 202695 ms
Jul 25, 202695 ms
Aug 1, 202696 ms
Aug 8, 2026100 ms
Aug 15, 2026101 ms
Aug 22, 2026101 ms
Aug 29, 2026100 ms
Sep 5, 2026101 ms
Sep 12, 2026103 ms
Sep 19, 2026104 ms
Sep 26, 2026110 ms
Oct 3, 2026112 ms
Oct 10, 2026114 ms
Oct 17, 2026113 ms
Oct 24, 2026113 ms
Oct 31, 2026114 ms
Nov 7, 2026114 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

geboorteplein.nl (opens in a new tab)
Full-page screenshot of geboorteplein.nl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix68

  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 68

    68/100

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

  • Use efficient cache lifetimes

    500 ms · 431 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Cookiebot and others), adding 769 KiB and 767 ms of main-thread time.

  • Google Tag Manager adds 366 ms

    366 ms

    Google Tag Manager costs a phone 366 ms of main-thread work and 340 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.

  • Facebook adds 262 ms

    262 ms

    Facebook costs a phone 262 ms of main-thread work and 226 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 JavaScript

    275 KiB

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

  • 11 long tasks on the main thread

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

  • Main-thread work: 2.4 s

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

  • 2,179 HTML elements

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

  • Improve image delivery

    150 ms · 55 KiB

    2 images could be 55 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.

  • Reduce unused CSS

    150 ms · 38 KiB

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

  • Minify CSS

    150 ms · 9 KiB

    9 KiB could be saved by minifying CSS.

  • Font display

    100 ms

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

  • Legacy JavaScript

    35 KiB

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

  • Minify JavaScript

    7 KiB

    7 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: 122 ms

    122 ms

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

Core Web Vitals

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

  • Real-user FCP: 3.5 s

    3.5 s

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

  • Real-user TTFB: 3.2 s

    3.2 s

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

  • Time to Interactive: 11.0 s

    11.0 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

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

    +22%

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Total Blocking Time: 473 ms

    473 ms

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

  • Speed Index: 4.6 s

    4.6 s

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

3 checks passed

  • Real-user INP: 115 ms

    115 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100

  • 2 images in older formats

    2 images (115 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.

  • About 0.4 g of CO₂ per visit

    0.41 g

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

3 checks passed

  • Page weight: 1.5 MB in 124 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 124 requests on a phone: scripts 889 KiB (43), fonts 205 KiB (6) and images 159 KiB (6). That is a lean page.

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

  • 82 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

    All page content should be contained by landmarks: 14 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.

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

  • 5 links without text

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

  • Headings skip levels

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

2 checks passed

  • Every image has alt text

    All 50 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10080

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “Geboorteplein | Geboorteborden en geboorteversiering met liefde gemaakt”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 197 internal links, 7 external

    The homepage links to 197 pages on geboorteplein.nl and 7 external pages.

5 checks passed

  • Meta description: 152 characters

    Your meta description is 152 characters: “Op zoek naar een leuk geboortebord, geboorteposter of vlag? geboorteplein.nl heeft de leukste geboorteversiering om de …”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • 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://geboorteplein.nl/sitemap_index.xml.

AI search readiness

100

  • No llms.txt

    There is no https://geboorteplein.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 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 (1,194 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83

  • 1 linked page hidden from search

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

  • 9 pages without a meta description

    https://geboorteplein.nl/winkelmand, https://geboorteplein.nl/product-category/geboortebord-tuin/ronde-geboorteborden, https://geboorteplein.nl/product-category/geboortebord-tuin/jungle-en-tropen-designs, https://geboorteplein.nl/product-category/geboortebord-tuin/geboortebord-silhouette, https://geboorteplein.nl/product-category/geboortebord-tuin/geboortebord-wegwijzer and https://geboorteplein.nl/product-category/geboortebord-tuin/geboortebord-voertuig and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://geboorteplein.nl/winkelmand has no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://geboorteplein.nl/product-category/geboortebord-tuin/jungle-en-tropen-designs, https://geboorteplein.nl/product-category/geboortebord-tuin/geboortebord-silhouette, https://geboorteplein.nl/product-category/geboortebord-tuin/geboortebord-wegwijzer, https://geboorteplein.nl/product-category/geboortebord-tuin/geboortebord-voertuig, https://geboorteplein.nl/product-category/geboortebord-tuin/scandinavisch-design and https://geboorteplein.nl/product-category/geboortebord-tuin/geboortebord-meisje and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 74 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

1 to fixGoogle 10093

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

2 checks passed

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70

  • 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 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 735 words of visible text.

3 checks passed

  • 2 calls to action

    The homepage has 2 calls to action, for example “Start met shoppen” and “Contact”.

  • Social proof on the page

    Social proof on the homepage: 14 testimonial or review blocks, 6 customer or partner logos, a star rating, 1 trust badge and “1.700+ reviews”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Cloudflare Web Analytics.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 13 cookies set on arrival

    13

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

  • 17 other companies contacted

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

1 checks passed

  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on geboorteplein.nl, including 20 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