Website review, no card needed
materne.be website review
Visit site (opens in a new tab)Reviewed 30 October 202631 issues · 83 checks
This review found 31 issues worth fixing on materne.be, 5 of them high impact, across 83 checks. The most urgent: 1 button 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
90A- #2,488 of 124,197 reviewed websitesbeats 97%
- #1,187 of 69,815 online storesbeats 97%
- #1,149 of 63,493 Shopify storesbeats 97%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 132 ms |
| May 16, 2026 | 134 ms |
| May 23, 2026 | 135 ms |
| May 30, 2026 | 139 ms |
| Jun 6, 2026 | 141 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 138 ms |
| Jun 27, 2026 | 131 ms |
| Jul 4, 2026 | 133 ms |
| Jul 11, 2026 | 133 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 137 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 135 ms |
| Aug 15, 2026 | 135 ms |
| Aug 22, 2026 | 136 ms |
| Aug 29, 2026 | 136 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 127 ms |
| Oct 3, 2026 | 134 ms |
| Oct 10, 2026 | 138 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 142 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 (Klaviyo, Shopify and ShareThis and others), adding 918 KiB and 530 ms of main-thread time.
Render-blocking requests
550 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Improve image delivery
50 ms · 304 KiB9 images could be 304 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 209 ms
209 msKlaviyo costs a phone 209 ms of main-thread work and 336 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.
1,659 HTML elements
The page has 1,659 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
244 KiBAbout 244 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
130 KiB20 files are served with short cache lifetimes, so returning visitors download them again (130 KiB).
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 83 ms. During a long task the page ignores taps.
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need.
Reduce unused CSS
25 KiBAbout 25 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
15 KiB15 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.
2 checks passed
Mobile performance score: 92
92/100Your mobile performance score is 92. That is in Google's “good” band (90 and up).
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 13.4 s
13.4 sThe page becomes fully interactive after 13.4 s. Good is under 3.8 s.
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 2.7 s
2.7 sYour largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 132 ms to 142 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 156 ms
156 msReal visitors wait 156 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 499 ms
499 msReal visitors wait 499 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 107 ms
107 msScripts block the page for only 107 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
Page weight: 2.6 MB in 262 requests
2.6 MBYour homepage downloads 2.6 MB in 262 requests on a phone: scripts 1.0 MB (95), other files 813 KiB (115) and images 545 KiB (22). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
baniere_mobile_DUO_FR.png 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).
About 0.7 g of CO₂ per visit
0.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.74 g of CO₂e: 88.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
5 form fields without a label
5 form fields have 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 (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 6 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (28 characters)
Your title is only 28 characters: “Materne - Merci les fruits !”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (185 characters)
Your meta description is 185 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
142 internal links, 7 external
The homepage links to 142 pages on materne.be and 7 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Bienvenue chez Materne”.
Canonical URL set
The canonical URL is https://www.materne.be/.
Structured data in place
Structured data found: Organization 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://www.materne.be/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
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 (718 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.materne.be/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
9 pages without a meta description
https://www.materne.be/collections/all, https://www.materne.be/pages/extra, https://www.materne.be/pages/allege, https://www.materne.be/pages/recolte, https://www.materne.be/pages/nostalgie and https://www.materne.be/pages/so-fruit and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://www.materne.be/pages/extra, https://www.materne.be/pages/allege, https://www.materne.be/pages/recolte, https://www.materne.be/pages/nostalgie, https://www.materne.be/pages/compote-bio and https://www.materne.be/pages/jus 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 59 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.
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 15 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 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 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 323 words of copy
The homepage carries about 323 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
5 short forms
5 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Pinterest Tag (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
38 other companies contacted
Loading the homepage contacts 38 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 materne.be, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- 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 31 issues on materne.be, including 10 speed issues, 3 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.