Website review, no card needed

sparklingstar.nl logo

sparklingstar.nl website review

Visit site (opens in a new tab)Reviewed 19 November 202640 issues · 77 checks

This review found 40 issues worth fixing on sparklingstar.nl, 17 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. 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 sparklingstar.nl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sparklingstar.nl at 0.9 s0.9 s
  2. sparklingstar.nl at 1.9 s1.9 s
  3. sparklingstar.nl at 2.8 s2.8 s
  4. sparklingstar.nl at 3.7 s3.7 s
  5. sparklingstar.nl at 4.6 s4.6 s
  6. sparklingstar.nl at 5.6 s5.6 s
  7. sparklingstar.nl at 6.5 s6.5 s
  8. sparklingstar.nl at 7.4 s7.4 s

Speed

9 to fix48
  • Use efficient cache lifetimes

    2.3 s · 1,015 KiB

    86 files are served with short cache lifetimes, so returning visitors download them again (1,015 KiB).

  • Improve image delivery

    1.2 s · 942 KiB

    5 images could be 942 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused JavaScript

    750 ms · 321 KiB

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

  • Reduce unused CSS

    750 ms · 177 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Hotjar and Google Tag Manager and others), adding 1.8 MB and 590 ms of main-thread time.

  • 10 long tasks on the main thread

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

  • Main-thread work: 3.5 s

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

  • WordPress adds 0 ms

    0 ms

    WordPress costs a phone 0 ms of main-thread work and 1.3 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.

  • Legacy JavaScript

    36 KiB

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

  • Minify JavaScript

    10 KiB

    10 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: 203 ms

    203 ms

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

Core Web Vitals

5 to fix45
  • Largest Contentful Paint: 8.7 s

    8.7 s

    Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welkom bij Sparkling Star Baby Spa Kinderkleding”.

  • Time to Interactive: 11.0 s

    11.0 s

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

  • Speed Index: 7.6 s

    7.6 s

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

  • Total Blocking Time: 866 ms

    866 ms

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

  • 2 images without width and height

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

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

    0.023

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

Images and page weight

2 to fix75
  • Page weight: 2.7 MB in 110 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 110 requests on a phone: images 1.3 MB (13), scripts 1,006 KiB (82) and stylesheets 185 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    46 KiB

    1 image is downloaded at several times the size a phone draws it, for example logo_sparkling-removebg-preview.png at 749 px wide, shown at 115 px. Resized copies would save about 46 KiB.

  • 3 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.76 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

8 to fixGoogle 8086
  • 47 text elements with low contrast

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

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Links look like plain text

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

  • 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 (9 elements)

    All page content should be contained by landmarks: 9 elements on the page fail 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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 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

4 to fixGoogle 8579
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

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

  • No social preview image

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

  • No robots.txt

    There is no robots.txt at sparklingstar.nl/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

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

  • 48 internal links, 3 external

    The homepage links to 48 pages on sparklingstar.nl and 3 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Welkom bijSparkling Star”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Sparkling Star – Baby Spa & Kids Clothing”.

  • Canonical URL set

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.sparklingstar.nl/sitemap.xml.

AI search readiness

1 to fix81
  • 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.

2 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (341 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.sparklingstar.nl/llms.txt (103 KiB, 1,088 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

3 to fix75
  • 4 pages without a title

    https://www.sparklingstar.nl/mijn-account, https://www.sparklingstar.nl/spa, https://www.sparklingstar.nl/wishlist and https://www.sparklingstar.nl/winkelwagen have no <title>, so Google invents the link text in results.

  • 15 pages without a meta description

    https://www.sparklingstar.nl/mijn-account, https://www.sparklingstar.nl/product-category/babys, https://www.sparklingstar.nl/product-category/kids, https://www.sparklingstar.nl/product-category/accessoires, https://www.sparklingstar.nl/product-category/sale and https://www.sparklingstar.nl/spa and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://www.sparklingstar.nl/mijn-account, https://www.sparklingstar.nl/product-category/babys, https://www.sparklingstar.nl/product-category/kids, https://www.sparklingstar.nl/product-category/accessoires, https://www.sparklingstar.nl/product-category/sale and https://www.sparklingstar.nl/spa and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://www.sparklingstar.nl/product-category/babys, https://www.sparklingstar.nl/product-category/kids, https://www.sparklingstar.nl/product-category/accessoires, https://www.sparklingstar.nl/product-category/sale, https://www.sparklingstar.nl/spa and https://www.sparklingstar.nl/shop/cadeaubon-baby-spa and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://demo.crocoblock.com/zolden-new/wp-content/uploads/2020/10/zolden-img-15.jpg.

  • 6 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 315 words of visible text.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel and Hotjar.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Hotjar 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.

  • 13 cookies set on arrival

    13

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 sparklingstar.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
Vue.js
E-commerce
WooCommerce
Analytics
Google Analytics | Hotjar
Hosting
Nl Bit Bit Bv

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on sparklingstar.nl, including 14 speed issues, 4 SEO issues and 4 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