Website review, no card needed

8limbs.be logo

8limbs.be website review

Visit site (opens in a new tab)Reviewed 31 October 202626 issues · 73 checks

This review found 26 issues worth fixing on 8limbs.be, 14 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. 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 8limbs.be (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 8limbs.be at 0.9 s0.9 s
  2. 8limbs.be at 1.8 s1.8 s
  3. 8limbs.be at 2.8 s2.8 s
  4. 8limbs.be at 3.7 s3.7 s
  5. 8limbs.be at 4.6 s4.6 s
  6. 8limbs.be at 5.5 s5.5 s
  7. 8limbs.be at 6.5 s6.5 s
  8. 8limbs.be at 7.4 s7.4 s

Speed

7 to fix37
  • Reduce unused JavaScript

    4.2 s · 832 KiB

    About 832 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.

  • Render-blocking requests

    2.6 s

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

  • Reduce unused CSS

    1.2 s · 218 KiB

    About 218 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 37

    37/100

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

  • Main-thread work: 4.2 s

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    350 ms · 18 KiB

    Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

  • Minify CSS

    150 ms · 17 KiB

    17 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    29 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Fonts and YouTube), adding 177 KiB and 1 ms of main-thread time.

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

  • Improve image delivery

    5 KiB

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

1 checks passed
  • Server response: 290 ms

    290 ms

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

Core Web Vitals

6 to fix39
  • Largest Contentful Paint: 13.1 s

    13.1 s

    Your largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Vous devez accepter les cookies facultatifs pour visualiser…”. Most of its time is resource load delay (6.2 s).

  • Time to Interactive: 13.2 s

    13.2 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.2 MB in 28 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 28 requests on a phone: scripts 1.5 MB (5), stylesheets 240 KiB (4) and fonts 211 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.64 g

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

3 checks passed
  • 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

4 to fixGoogle 9193
  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

  • Frames without titles

    2 frames have no title, so screen-reader users cannot tell what they contain.

  • 2 form fields without a label

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

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

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

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

SEO

1 to fixGoogle 10095
  • 2 H1 headlines

    There are 2 <h1> headlines (“Vous ne venez pas seulement vous entraîner.Vous v…” and “Pas seulement vous entraîner.Vous transformer.”). One clear main headline is easier for people and search engines.

  • 56 internal links, 4 external

    The homepage links to 56 pages on 8limbs.be and 4 external pages.

7 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Vous ne venez pas seulement vous entraîner. Vous venez vous transformer. Cours privés de 50 minutes, Immersion Belgique…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Coaching privé Muay Thaï · Brabant wallon & Bruxelles | 8LIMBS”.

  • Canonical URL set

    The canonical URL is https://www.8limbs.be/.

  • Structured data in place

    Structured data found: Organization.

  • 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://www.8limbs.be/sitemap.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://www.8limbs.be/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 (2,009 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix78
  • 1 page points its canonical at the homepage

    https://www.8limbs.be/survey/start/7c8dd63e-ad28-4371-95ef-64ea8d86cf6e declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.8limbs.be/survey/start/7c8dd63e-ad28-4371-95ef-64ea8d86cf6e all use the title “Coaching privé Muay Thaï · Brabant wallon & Bruxelles | 8LIMBS”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.8limbs.be/shop/wishlist has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://www.8limbs.be/shop/wishlist 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.

  • 2 pages slow to respond

    https://www.8limbs.be/immersion-thailande and https://www.8limbs.be/survey/start/7c8dd63e-ad28-4371-95ef-64ea8d86cf6e took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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_UNKNOWN_URL_SCHEME”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

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

    The homepage carries about 681 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 10 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Analytics and Umami.

Privacy and tracking

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 8limbs.be, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on 8limbs.be, including 13 speed issues, 1 SEO issue 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