Website review, no card needed

pommeloe.nl logo

pommeloe.nl website review

Visit site (opens in a new tab)Reviewed 20 November 202639 issues · 76 checks

This review found 39 issues worth fixing on pommeloe.nl, 15 of them high impact, across 76 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 pommeloe.nl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pommeloe.nl at 1.4 s1.4 s
  2. pommeloe.nl at 2.8 s2.8 s
  3. pommeloe.nl at 4.3 s4.3 s
  4. pommeloe.nl at 5.7 s5.7 s
  5. pommeloe.nl at 7.1 s7.1 s
  6. pommeloe.nl at 8.5 s8.5 s
  7. pommeloe.nl at 10.0 s10.0 s
  8. pommeloe.nl at 11.4 s11.4 s

Speed

7 to fix70
  • Render-blocking requests

    3.4 s

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

  • 4,929 HTML elements

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

  • Mobile performance score: 70

    70/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (webshopapp.com, Google CDN and elfsight.com and others), adding 3.2 MB and 284 ms of main-thread time.

  • webshopapp.com adds 224 ms

    224 ms

    webshopapp.com costs a phone 224 ms of main-thread work and 3.1 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.

  • Reduce unused JavaScript

    420 ms · 73 KiB

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

  • Main-thread work: 2.6 s

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

  • Minify JavaScript

    150 ms · 39 KiB

    39 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    150 ms · 34 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 108 ms. During a long task the page ignores taps.

  • Improve image delivery

    50 KiB

    1 image could be 50 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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: 542 ms

    542 ms

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

Core Web Vitals

6 to fix72
  • First Contentful Paint: 3.5 s

    3.5 s

    The first text or image appears after 3.5 s on a phone. Good is under 1.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 “Klarna Pay Later”.

  • 145 images without width and height

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

  • Cumulative Layout Shift: 0.17

    0.17

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

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

  • Time to Interactive: 4.2 s

    4.2 s

    The page becomes fully interactive after 4.2 s. Good is under 3.8 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.

1 checks passed
  • Total Blocking Time: 29 ms

    29 ms

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

Images and page weight

2 to fix78
  • Page weight: 3.3 MB in 100 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 100 requests on a phone: images 2.8 MB (61), scripts 322 KiB (21) and fonts 60 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 9 images below the first screen load straight away

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

  • 3 images in older formats

    3 images (217 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.9 g of CO₂ per visit

    0.92 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.92 g of CO₂e: 111.0 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

10 to fixGoogle 6085
  • 512 tap targets too small

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

  • 273 text elements with low contrast

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

  • Unlabelled dropdowns

    31 dropdowns have no label.

  • Links must have discernible text (97 elements)

    Links must have discernible text: 97 elements on the page fail this check, rated serious by axe-core.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

  • 68 form fields without a label

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

  • Alternative text of images should not be repeated as text (9 elements)

    Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 42 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: 42 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 8570
  • No H1 headline

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

  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “POMMELOE | De leukste online baby- en kinderkleding store! - POMMELOE”.

  • Meta description is long (200 characters)

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

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://www.pommeloe.nl/sitemap.xml, so Google discovers your pages only by following links.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 772 internal links, 6 external

    The homepage links to 772 pages on pommeloe.nl and 6 external pages.

3 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and 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.

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

Other pages

1 to fix0
  • 15 linked pages are broken

    Your homepage links to https://www.pommeloe.nl/service/payment-methods, https://www.pommeloe.nl/baby, https://www.pommeloe.nl/baby/newborn, https://www.pommeloe.nl/baby/newborn/rompers, https://www.pommeloe.nl/baby/newborn/jumpsuits and https://www.pommeloe.nl/baby/newborn/jackets and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 15 internal pages checked

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

Best practices

4 to fixGoogle 9263
  • 1 broken image

    1 image failed to load on a phone, for example https://placehold.it/50x50.

  • 51 small tap targets

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

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 6 low-resolution images

    6 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • 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 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 3,618 words of copy

    The homepage carries about 3,618 words of visible text.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Nieuw bij Pommeloe!Shop here”, “Contact + Adresgegevens” and “Start vergelijking”.

  • 68 short forms

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

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

  • 1 cookie set on arrival

    1

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

  • 9 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
jQuery
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on pommeloe.nl, including 13 speed issues, 6 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