Website review, no card needed

jmband.be logo

jmband.be website review

Visit site (opens in a new tab)Reviewed 10 November 202638 issues · 85 checks

This review found 38 issues worth fixing on jmband.be, 18 of them high impact, across 85 checks. The most urgent: hcaptcha.com adds 1.2 s. 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
5.4 s3.8 sMay 23Oct 34.3 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20264.9 s
May 30, 20265.2 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
236 ms98 msMay 23Oct 10162 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026118 ms
May 30, 2026114 ms
Sep 19, 2026220 ms
Sep 26, 2026195 ms
Oct 3, 2026194 ms
Oct 10, 2026162 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 jmband.be (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. jmband.be at 0.8 s0.8 s
  2. jmband.be at 1.6 s1.6 s
  3. jmband.be at 2.4 s2.4 s
  4. jmband.be at 3.2 s3.2 s
  5. jmband.be at 4.0 s4.0 s
  6. jmband.be at 4.8 s4.8 s
  7. jmband.be at 5.6 s5.6 s
  8. jmband.be at 6.4 s6.4 s

Speed

11 to fix28
  • hcaptcha.com adds 1.2 s

    1.2 s

    hcaptcha.com costs a phone 1.2 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 28

    28/100

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

  • Main-thread work: 6.8 s

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

  • 3,370 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (hcaptcha.com, Shopify and Klaviyo and others), adding 3.1 MB and 2.0 s of main-thread time.

  • Reduce unused JavaScript

    770 ms · 569 KiB

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

  • Render-blocking requests

    700 ms

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

  • Use efficient cache lifetimes

    150 ms · 280 KiB

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

  • Shopify adds 304 ms

    304 ms

    Shopify costs a phone 304 ms of main-thread work and 1.2 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.

  • 18 long tasks on the main thread

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

  • Klaviyo adds 280 ms

    280 ms

    Klaviyo costs a phone 280 ms of main-thread work and 347 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.

  • Reduce unused CSS

    150 ms · 22 KiB

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

  • Legacy JavaScript

    90 KiB

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

  • Improve image delivery

    29 KiB

    3 images could be 29 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    17 KiB

    17 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: 16 ms

    16 ms

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

Core Web Vitals

7 to fix17
  • Time to Interactive: 31.3 s

    31.3 s

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

  • Largest Contentful Paint: 7.8 s

    7.8 s

    Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nous et nos partenaires, y compris Shopify, utilisons des c…”.

  • Cumulative Layout Shift: 0.609

    0.609

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

  • Speed Index: 7.0 s

    7.0 s

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

  • Total Blocking Time: 751 ms

    751 ms

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

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

    +53%

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

  • 7 images without width and height

    7 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
  • Largest content (LCP) got 18% faster for real visitors

    -18%

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

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

Images and page weight

3 to fix45
  • Page weight: 6.8 MB in 598 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 598 requests on a phone: scripts 2.4 MB (234), images 2.0 MB (27) and other files 1.5 MB (270). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    6c6382f0-e39c-4b2c-ba15-674469521f32.png weighs 1.7 MB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (1.7 MB) is 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.

  • About 1.9 g of CO₂ per visit

    1.93 g

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

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

8 to fixGoogle 8490
  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • 87 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

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

  • 46 images without alt text

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

  • All page content should be contained by landmarks (5 elements)

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

  • 9 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 56 automated accessibility rules passed

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

SEO

2 to fixGoogle 9288
  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “JM Band | +5500 produits imprimés personnalisés & livraison quotidienne”.

  • One H1 headline

    Your <h1> is empty.

  • 413 internal links, 44 external

    The homepage links to 413 pages on jmband.be and 44 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Plus de 30 000 clients satisfaits pour divers bracelets, billets à roulettes, billets de garde-robe, jetons, lanières e…”.

  • Canonical URL set

    The canonical URL is https://jmband.be/.

  • Structured data in place

    Structured data found: OnlineStore, WebPage 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://jmband.be/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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://jmband.be/collections/bracelets-rfid/Stofarmb%C3%A5nd, whose canonical is https://jmband.be/collections/bracelets-rfid/stofarmb%c3%a5nd. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://jmband.be/pages/livraison, https://jmband.be/collections/bracelet-personnalise, https://jmband.be/collections/bracelets-en-papier, https://jmband.be/products/bracelets-en-papier-avec-imprime, https://jmband.be/products/bracelets-en-papier-sans-imprimer and https://jmband.be/products/bracelet-couleur and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://jmband.be/collections/bracelet-tissu, https://jmband.be/products/bracelets-du-festival-avec-imprime, https://jmband.be/collections/bracelets-rfid/Stofarmb%C3%A5nd, https://jmband.be/products/bracelet-tissu-personnalise-petite-quantite, https://jmband.be/collections/bracelet-silicone-caoutchouc and https://jmband.be/products/bracelets-en-silicone-degivre-en-couleur 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 176 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

4 checks passed
  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 4 testimonial or review blocks, 1 customer or partner logo, a star rating and 9 trust badges.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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, Klaviyo 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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 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 jmband.be, 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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Gorgias Live Chat Helpdesk · Profitmetrics · Klaviyo Email Marketing Sms · Judge Me Reviews · Sc Easy Redirects · Pdf Invoice Customizer · Forms · zakeke.com

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
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on jmband.be, including 18 speed issues, 2 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