Website review, no card needed
damart.be website review
Visit site (opens in a new tab)Reviewed 20 October 202641 issues · 80 checks
This review found 41 issues worth fixing on damart.be, 13 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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
71C- #99,831 of 123,862 reviewed websitesbeats 17%
- #61,075 of 69,698 online storesbeats 10%
- #427 of 725 Magento storesbeats 38%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.3 s |
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 102 ms |
| May 9, 2026 | 100 ms |
| May 16, 2026 | 99 ms |
| May 23, 2026 | 97 ms |
| May 30, 2026 | 97 ms |
| Jun 6, 2026 | 98 ms |
| Jun 13, 2026 | 102 ms |
| Jun 20, 2026 | 109 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 132 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 136 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 135 ms |
| Aug 15, 2026 | 132 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 128 ms |
| Sep 19, 2026 | 130 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 138 ms |
| Oct 10, 2026 | 142 ms |
| Oct 17, 2026 | 145 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
Reduce unused JavaScript
6.3 s · 963 KiBAbout 963 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.3 s faster on a phone.
Use efficient cache lifetimes
2.6 s · 592 KiB7 files are served with short cache lifetimes, so returning visitors download them again (592 KiB).
Render-blocking requests
2.5 s36 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Reduce unused CSS
1.1 s · 242 KiBAbout 242 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51 (desktop: 60). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Didomi and Google Tag Manager and others), adding 1.5 MB and 589 ms of main-thread time.
Google CDN adds 244 ms
244 msGoogle CDN costs a phone 244 ms of main-thread work and 730 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.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Didomi adds 98 ms
98 msDidomi costs a phone 98 ms of main-thread work and 323 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 165 ms. During a long task the page ignores taps.
Improve image delivery
9 KiB1 image could be 9 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 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.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
First Contentful Paint: 11.8 s
11.8 sThe first text or image appears after 11.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 17.3 s
17.3 sYour largest element takes 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Avec nos partenaires, nous traitons les données suivantes :…”.
Time to Interactive: 19.2 s
19.2 sThe page becomes fully interactive after 19.2 s. Good is under 3.8 s.
Speed Index: 11.8 s
11.8 sVisually, the page fills in at 11.8 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 42% slower for real visitors
+42%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 102 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 62% slower for real visitors
+62%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 230 ms
230 msScripts block taps and scrolling for 230 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.
3 checks passed
Real-user INP: 95 ms
95 msReal visitors wait 95 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.018
0.018The layout barely moves while loading (CLS 0.018, good is under 0.1).
Images and page weight
Page weight: 3.0 MB in 102 requests
3.0 MBYour homepage downloads 3.0 MB in 102 requests on a phone: scripts 2.1 MB (40), other files 357 KiB (20) and stylesheets 300 KiB (33). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.85 g of CO₂e: 102.3 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
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
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.
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 1 image in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (26 characters)
Your title is only 26 characters: “Damart (Belgique / België)”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (40 characters)
Your meta description is only 40 characters: “Choisissez votre language | Kies je taal”. 70 to 160 characters is enough to sell the click.
Structured data has 1 problem
Structured data found (WebPage and WebSite) but with 1 problem, for example “WebSite: missing name”.
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 XML sitemap
No XML sitemap at https://www.damart.be/sitemap.xml, so Google discovers your pages only by following links.
Only 2 internal links
The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
3 checks passed
One H1 headline
Your main headline reads: “BienvenueWelkom”.
Canonical URL set
The canonical URL is https://www.damart.be/fr_be/damart-belgique-belgie.
robots.txt in place
robots.txt is in place.
AI search readiness
Most text only appears after JavaScript runs
11%A phone browser shows 194 words, but the HTML your server sends has only 21. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.
No llms.txt
There is no https://www.damart.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.
1 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.
Other pages
2 pages without a meta description
https://www.damart.be/fr_be and https://www.damart.be/nl_be have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.damart.be/fr_be and https://www.damart.be/nl_be have no <h1> headline, so visitors and search engines get no clear main topic.
2 internal pages checked
We fetched 2 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 2 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.
Every page has a title
All 2 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading '0')”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
5 of 6 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 194 words
The homepage has only about 194 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.
13 cookies set on arrival
13Opening the homepage sets 13 cookies (measured from a US location before any click).
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Didomi
A consent management tool (Didomi) loads with the page.
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 damart.be, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2013.
Stack
- Framework
- Bootstrap
- E-commerce
- Magento
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on damart.be, including 21 speed issues, 6 SEO issues and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.