Website review, no card needed

comptoirdeskids.be logo

comptoirdeskids.be website review

Visit site (opens in a new tab)Reviewed 10 November 202627 issues · 76 checks

This review found 27 issues worth fixing on comptoirdeskids.be, 7 of them high impact, across 76 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Real-visitor load time (LCP)75th percentile, phones
4.6 s2.1 sMay 23Nov 73.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.4 s
May 30, 20262.5 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.8 s
Jul 11, 20263.4 s
Jul 18, 20263.4 s
Jul 25, 20263.5 s
Aug 1, 20263.6 s
Aug 8, 20263.7 s
Aug 15, 20264.0 s
Aug 22, 20264.2 s
Aug 29, 20264.3 s
Sep 5, 20264.2 s
Sep 12, 20263.9 s
Sep 19, 20263.8 s
Sep 26, 20263.7 s
Oct 3, 20263.6 s
Oct 10, 20263.7 s
Oct 17, 20263.4 s
Oct 24, 20263.0 s
Oct 31, 20263.1 s
Nov 7, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
502 ms149 msMay 23Oct 10243 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026190 ms
May 30, 2026226 ms
Jun 6, 2026298 ms
Aug 1, 2026461 ms
Aug 8, 2026408 ms
Aug 15, 2026399 ms
Aug 22, 2026408 ms
Aug 29, 2026347 ms
Sep 5, 2026343 ms
Sep 12, 2026306 ms
Sep 19, 2026295 ms
Sep 26, 2026271 ms
Oct 3, 2026255 ms
Oct 10, 2026243 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

Full-page screenshot of comptoirdeskids.be (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix97
  • Render-blocking requests

    500 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 500 ms.

  • Reduce unused CSS

    300 ms · 63 KiB

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

  • 1,654 HTML elements

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

  • Use efficient cache lifetimes

    150 ms · 173 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Yandex Metrica, Cloudflare and Gravatar), adding 90 KiB and 83 ms of main-thread time.

  • Reduce unused JavaScript

    73 KiB

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

  • Improve image delivery

    12 KiB

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

3 checks passed
  • Mobile performance score: 97

    97/100

    Your mobile performance score is 97. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 123 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

7 to fix50
  • 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 TTFB: 2.0 s

    2.0 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

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

    +20%

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

  • Largest content (LCP) got 24% slower for real visitors

    +24%

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • Speed Index: 4.4 s

    4.4 s

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

6 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “De markt voor online casino’s in België in 2026 is streng g…”.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.4 s

    1.4 s

    The page is fully interactive after 1.4 s.

Images and page weight

100
  • About 0.1 g of CO₂ per visit

    0.13 g

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

4 checks passed
  • Page weight: 452 KiB in 40 requests

    452 KiB

    Your homepage downloads 452 KiB in 40 requests on a phone: stylesheets 167 KiB (2), scripts 127 KiB (3) and images 112 KiB (25). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

5 to fixGoogle 9293
  • 12 text elements with low contrast

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 form field without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

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

SEO

3 to fixGoogle 10085
  • Title is long (76 characters)

    Your title is 76 characters, so Google will cut it off around 60: “Top 10 Online Casino’s in België voor september 2026 | Beste Legale Casino’s”.

  • Canonical points to another host

    Your canonical URL points to top10onlinecasinobelgie.org, not billysongrand.com, so Google may credit that host instead.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “Organization: url points at a different host (https://online-casinos-belgie.com/)”.

  • 11 internal links, 3 external

    The homepage links to 11 pages on comptoirdeskids.be and 3 external pages.

5 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Overzicht van de beste online casino’s in België in 2026 🇧🇪💳 Veilige en snelle uitbetalingen, legale aanbieders en c…”.

  • One H1 headline

    Your main headline reads: “TOP 10 Online Casino's van België in 2026”.

  • 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://online-casinos-belgie.com/sitemap_index.xml.

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://billysongrand.com/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.

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

Other pages

4 to fix68
  • 1 page without a title

    https://billysongrand.com/speel/baloo has no <title>, so Google invents the link text in results.

  • 3 pages share a title

    https://billysongrand.com/speel/trueluck, https://billysongrand.com/speel/spinalto and https://billysongrand.com/speel/spinorhino all use the title “Redirecting...”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://billysongrand.com/speel/trueluck, https://billysongrand.com/speel/baloo, https://billysongrand.com/speel/spinalto, https://billysongrand.com/speel/spinorhino and https://billysongrand.com/verantwoord-gokken have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://billysongrand.com/speel/trueluck, https://billysongrand.com/speel/baloo, https://billysongrand.com/speel/slotrush, https://billysongrand.com/speel/spinalto and https://billysongrand.com/speel/spinorhino have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://billysongrand.com/speel/slotrush has 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.

  • 1 page slow to respond

    https://billysongrand.com/speel/spinorhino took over 3 s to send its HTML from our server.

  • 8 internal pages checked

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

3 checks passed
  • Linked pages load

    7 pages of 8 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

  • 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 8,298 words of copy

    The homepage carries about 8,298 words of visible text.

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 40 customer or partner logos, a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Yandex Metrica (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.

  • 3 cookies set on arrival

    3

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 comptoirdeskids.be, 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
E-commerce
Shopify;Shopify Plus
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on comptoirdeskids.be, including 10 speed issues, 3 SEO issues and 3 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