Programmable

Website review, no card needed

sterrenregister.nl logo

sterrenregister.nl website review

Visit site (opens in a new tab)Reviewed 8 November 202630 issues · 76 checks

This review found 30 issues worth fixing on sterrenregister.nl, 7 of them high impact, across 76 checks. The most urgent: page weight: 4.1 MB in 224 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

81B

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.9 s1.6 sJul 4Oct 31.7 s
Show as table
DateReal-visitor load time (LCP)
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
217 ms174 msJul 11Oct 3183 ms
Show as table
DateReal-visitor tap response (INP)
Jul 11, 2026181 ms
Aug 15, 2026211 ms
Aug 22, 2026212 ms
Aug 29, 2026189 ms
Sep 26, 2026179 ms
Oct 3, 2026183 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

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

How it loaded on a phone

  1. sterrenregister.nl at 0.7 s0.7 s
  2. sterrenregister.nl at 1.4 s1.4 s
  3. sterrenregister.nl at 2.1 s2.1 s
  4. sterrenregister.nl at 2.8 s2.8 s
  5. sterrenregister.nl at 3.5 s3.5 s
  6. sterrenregister.nl at 4.3 s4.3 s
  7. sterrenregister.nl at 5.0 s5.0 s
  8. sterrenregister.nl at 5.7 s5.7 s

Speed

9 to fix72

  • Reduce unused JavaScript

    300 ms · 1.5 MB

    About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and TikTok and others), adding 2.0 MB and 970 ms of main-thread time.

  • Mobile performance score: 72

    72/100

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

  • Render-blocking requests

    750 ms

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

  • Reduce unused CSS

    300 ms · 165 KiB

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

  • YouTube adds 343 ms

    343 ms

    YouTube costs a phone 343 ms of main-thread work and 1,014 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.

  • Main-thread work: 3.6 s

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

  • Use efficient cache lifetimes

    357 KiB

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

  • Google Tag Manager adds 245 ms

    245 ms

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

  • Improve image delivery

    150 ms · 79 KiB

    5 images could be 79 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.

  • 10 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    9 KiB

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

1 checks passed

  • Server response: 78 ms

    78 ms

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

Core Web Vitals

4 to fix67

  • Time to Interactive: 21.5 s

    21.5 s

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

  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “sterrenregister testimonial moeder kind”.

  • Total Blocking Time: 275 ms

    275 ms

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

  • Speed Index: 3.9 s

    3.9 s

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

  • Tap response (INP) held steady for real visitors

    -8%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 181 ms to 183 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-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

2 checks passed

  • Cumulative Layout Shift: 0.047

    0.047

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

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

Images and page weight

2 to fix64

  • Page weight: 4.1 MB in 224 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 224 requests on a phone: scripts 2.2 MB (71), images 777 KiB (32) and other files 756 KiB (100). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    radial-ellipse.svg 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).

  • About 1.2 g of CO₂ per visit

    1.16 g

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

2 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9093

  • 17 text elements with low contrast

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

  • <dt> and <dd> elements must be contained by a <dl> (12 elements)

    <dt> and <dd> elements must be contained by a <dl>: 12 elements on the page fail this check, rated serious by axe-core.

  • <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (3 elements)

    <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 3 elements on the page fail this check, rated serious by axe-core.

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

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

2 checks passed

  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

Google 92100

  • 25 internal links, 11 external

    The homepage links to 25 pages on sterrenregister.nl and 11 external pages.

8 checks passed

  • Meta description: 156 characters

    Your meta description is 156 characters: “Koop en benoem een echte ster aan de hemel. Een onvergetelijk geschenk voor de eeuwigheid. Sterrenregister is de premiu…”.

  • One H1 headline

    Your main headline reads: “Geef een ster cadeau”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Koop en geef een ster weg met Sterrenregister”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and 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://sterrenregister.nl/sitemap.xml.

AI search readiness

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

  • llms.txt published

    The site publishes https://sterrenregister.nl/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix75

  • 2 linked pages hidden from search

    https://sterrenregister.nl/products/digitale-cadeaubon and https://sterrenregister.nl/products/plus-pakket-upgrade are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages share a title

    https://sterrenregister.nl/pages/star-configurator/geef-een-ster-silvernova, https://sterrenregister.nl/pages/star-configurator/geef-een-ster-uit-een-sterrenbeeld-supernova and https://sterrenregister.nl/pages/star-configurator/geef-een-binaire-ster-duonova all use the title “Star Configurator”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://sterrenregister.nl/apps/tracktor/track, https://sterrenregister.nl/pages/star-configurator/geef-een-ster-silvernova, https://sterrenregister.nl/pages/star-configurator/geef-een-ster-uit-een-sterrenbeeld-supernova, https://sterrenregister.nl/pages/star-configurator/geef-een-binaire-ster-duonova, https://sterrenregister.nl/products/digitale-cadeaubon and https://sterrenregister.nl/products/plus-pakket-upgrade and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://sterrenregister.nl/pages/sterrenpakketten, https://sterrenregister.nl/pages/faq-ster-cadeau, https://sterrenregister.nl/apps/tracktor/track, https://sterrenregister.nl/pages/star-configurator/geef-een-ster-silvernova, https://sterrenregister.nl/pages/star-configurator/geef-een-ster-uit-een-sterrenbeeld-supernova and https://sterrenregister.nl/pages/star-configurator/geef-een-binaire-ster-duonova and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://sterrenregister.nl/apps/tracktor/track, https://sterrenregister.nl/pages/star-configurator/geef-een-ster-silvernova, https://sterrenregister.nl/pages/star-configurator/geef-een-ster-uit-een-sterrenbeeld-supernova, https://sterrenregister.nl/pages/star-configurator/geef-een-binaire-ster-duonova and https://sterrenregister.nl/pages/klantenservice-contact 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.

  • 15 internal pages checked

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

3 checks passed

  • Linked pages load

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

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385

  • 24 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75

  • 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 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 1,174 words of copy

    The homepage carries about 1,174 words of visible text.

4 checks passed

  • 1 call to action

    The homepage has 1 call to action, for example “Hulp & contact”.

  • 6 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo, a star rating and 5 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix

  • 5 trackers load before any consent

    5

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

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies, 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.

  • 41 other companies contacted

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

Apps your storefront loads

Gorgias Live Chat Helpdesk · Noindexly · Triplewhale · Elevar Conversion Tracking · Trueprofit · Page Speed Optimizer · pandect.es

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
Analytics
Google Tag Manager
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 sterrenregister.nl, including 13 speed 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