pryl.nl website review

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

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

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

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

6 images could be 258 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.

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

7 third-party services load with your homepage (Google Tag Manager, Microsoft Hosted Libs and Bootstrap CDN and others), adding 368 KiB and 120 ms of main-thread time.

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

21 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Pryl kraamzorg Pryl staat voor een fijne kraamweek en een g…”.

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

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

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

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

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.

2 images are downloaded at several times the size a phone draws them, for example ouders-met-baby-2mb.jpg at 1,552 px wide, shown at 390 px. Resized copies would save about 101 KiB.

9 images (486 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.

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

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 10 pages on pryl.nl and 8 external pages.

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.

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

/ and https://www.pryl.nl/home all use the title “Pryl kraamzorg - Geluk dichtbij”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.pryl.nl/kraamzorg, https://www.pryl.nl/vragen, https://www.pryl.nl/contact, https://www.pryl.nl/algemene-voorwaarden, https://www.pryl.nl/privacy-statement and https://www.pryl.nl/klachten have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.pryl.nl/home, https://www.pryl.nl/contact, https://www.pryl.nl/algemene-voorwaarden, https://www.pryl.nl/privacy-statement and https://www.pryl.nl/klachten have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 7 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/e554f31585.css' from origin 'https://www.pryl.nl' has been blo…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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.

Opening the homepage sets 2 cookies (measured from a US location before any click).

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.

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