Website review, no card needed
nmmedical.be website review
Visit site (opens in a new tab)Reviewed 11 November 202630 issues · 83 checks
This review found 30 issues worth fixing on nmmedical.be, 5 of them high impact, across 83 checks. The most urgent: 10 buttons without a name. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
86B- #9,831 of 98,215 reviewed websitesbeats 86%
- #5,833 of 53,591 online storesbeats 84%
- #5,651 of 48,604 Shopify storesbeats 83%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 104 ms |
| May 30, 2026 | 100 ms |
| Jun 6, 2026 | 109 ms |
| Jun 13, 2026 | 111 ms |
| Jun 20, 2026 | 109 ms |
| Jun 27, 2026 | 117 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 118 ms |
| Jul 18, 2026 | 117 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 116 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 116 ms |
| Aug 29, 2026 | 112 ms |
| Sep 5, 2026 | 109 ms |
| Sep 12, 2026 | 111 ms |
| Sep 19, 2026 | 105 ms |
| Sep 26, 2026 | 106 ms |
| Oct 3, 2026 | 110 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 99 ms |
| Oct 31, 2026 | 97 ms |
| Nov 7, 2026 | 104 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
Speed
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, omnisnippet1.com and Yotpo and others), adding 974 KiB and 960 ms of main-thread time.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
150 ms · 574 KiB8 images could be 574 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.
Google Tag Manager adds 498 ms
498 msGoogle Tag Manager costs a phone 498 ms of main-thread work and 370 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 JavaScript
150 ms · 358 KiBAbout 358 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Use efficient cache lifetimes
150 ms · 295 KiB21 files are served with short cache lifetimes, so returning visitors download them again (295 KiB).
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 305 ms. During a long task the page ignores taps.
2,442 HTML elements
The page has 2,442 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 43 KiBAbout 43 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.
Minify JavaScript
40 ms · 18 KiB18 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: 35 ms
35 msYour server sent the HTML in 35 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 13.5 s
13.5 sThe page becomes fully interactive after 13.5 s. Good is under 3.8 s.
Largest Contentful Paint: 5.5 s
5.5 sYour largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Drap d'examen ouaté lisse - 50 x 38cm - Carton de 12 roulea…”.
Total Blocking Time: 466 ms
466 msScripts block taps and scrolling for 466 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 104 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 454 ms
454 msReal visitors wait 454 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.1 s
3.1 sVisually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.044
0.044The layout barely moves while loading (CLS 0.044, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 3.5 MB in 211 requests
3.5 MBYour homepage downloads 3.5 MB in 211 requests on a phone: images 1.1 MB (33), scripts 1.1 MB (62) and other files 762 KiB (106). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
sliders_gamme_dermlite.gif 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).
4 images in older formats
4 images (354 KiB) are 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.0 g of CO₂ per visit
0.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 118.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
10 buttons without a name
10 buttons have no accessible name, so screen readers announce just “button”.
24 text elements with low contrast
24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 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.
23 links without text
23 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h6, h2 → h4 and h2 → h6), 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 105 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (19 characters)
Your title is only 19 characters: “NM Medical Belgique”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (315 characters)
Your meta description is 315 characters; Google truncates after about 160, so the end of your pitch is cut.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
464 internal links, 11 external
The homepage links to 464 pages on nmmedical.be and 11 external pages.
5 checks passed
One H1 headline
Your main headline reads: “NM Médical : votre spécialiste en matériel médical depuis 1978”.
Canonical URL set
The canonical URL is https://nmmedical.be/.
Structured data in place
Structured data found: BreadcrumbList and WebSite.
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://nmmedical.be/sitemap.xml.
AI search readiness
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.
3 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 (1,598 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://nmmedical.be/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
10 pages share a meta description
https://nmmedical.be/pages/devis-gratuit-materiel-et-fournitures-medicales, https://nmmedical.be/pages/mon-compte, https://nmmedical.be/pages/anniversaire-p2, https://nmmedical.be/collections/promos, https://nmmedical.be/collections/la-selection-du-medecin-generaliste and https://nmmedical.be/pages/nos-catalogues and 4 others use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://nmmedical.be/pages/mon-compte and https://nmmedical.be/pages/anniversaire-p2 have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.
6 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.
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
10 broken images
10 images failed to load on a phone, for example https://nmmedical.be/cdn/shop/t/2/assets/data:image/svg+xml;base64,PHN2ZyBjbGFzcz0iIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCA1MjUuNSA1MjUuNSI+PHBhdGggZD0iTTMyNC41IDIxMi43SDIwM.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
39 of 46 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 554 words of copy
The homepage carries about 554 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Gel de contact Supragel LCH”.
9 calls to action
The homepage has 9 calls to action, for example “Contact”, “Gel de contact” and “Gel de contact Supragel LCH”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 3 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Mixpanel (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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
30 other companies contacted
Loading the homepage contacts 30 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 nmmedical.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Yotpo Loyalty Rewards · Doofinder Search Discovery · Yotpo Product Reviews · Omnisend · easyquote.pw · useamp.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
- CMS
- sharp
- Framework
- Tailwind CSS
- 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 nmmedical.be, including 13 speed issues, 2 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.