Website review, no card needed

partenamut.be logo

partenamut.be website review

Visit site (opens in a new tab)Reviewed 31 October 202631 issues · 78 checks

This review found 31 issues worth fixing on partenamut.be, 7 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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
2.0 s1.7 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20262.0 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
262 ms190 msMay 9Oct 24202 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026249 ms
May 16, 2026251 ms
May 23, 2026253 ms
May 30, 2026254 ms
Jun 6, 2026254 ms
Jun 13, 2026252 ms
Jun 20, 2026252 ms
Jun 27, 2026253 ms
Jul 4, 2026253 ms
Jul 11, 2026253 ms
Jul 18, 2026247 ms
Jul 25, 2026236 ms
Aug 1, 2026227 ms
Aug 8, 2026219 ms
Aug 15, 2026216 ms
Aug 22, 2026214 ms
Aug 29, 2026213 ms
Sep 5, 2026211 ms
Sep 12, 2026205 ms
Sep 19, 2026204 ms
Sep 26, 2026198 ms
Oct 3, 2026198 ms
Oct 10, 2026199 ms
Oct 17, 2026201 ms
Oct 24, 2026202 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 partenamut.be (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. partenamut.be at 0.4 s0.4 s
  2. partenamut.be at 0.8 s0.8 s
  3. partenamut.be at 1.1 s1.1 s
  4. partenamut.be at 1.5 s1.5 s
  5. partenamut.be at 1.9 s1.9 s
  6. partenamut.be at 2.3 s2.3 s
  7. partenamut.be at 2.6 s2.6 s
  8. partenamut.be at 3.0 s3.0 s

Speed

4 to fix75
  • Render-blocking requests

    1.4 s

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

  • Improve image delivery

    800 ms · 333 KiB

    7 images could be 333 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

  • Mobile performance score: 75

    75/100

    Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    300 ms · 52 KiB

    About 52 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 163 KiB

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

  • Reduce unused JavaScript

    150 ms · 105 KiB

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

  • Document request latency

    103 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 3 long tasks on the main thread

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, VWO and ScientiaMobile), adding 94 KiB and 44 ms of main-thread time.

  • Legacy JavaScript

    6 KiB

    Polyfills for old browsers add 6 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.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 465 ms of it running JavaScript. That is comfortably low.

  • Server response: 277 ms

    277 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Real-user FCP: 2.2 s

    2.2 s

    Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.6 s

    1.6 s

    Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 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.

  • Speed Index: 4.9 s

    4.9 s

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

  • Time to Interactive: 5.4 s

    5.4 s

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

  • 12 images without width and height

    12 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) got 10% slower for real visitors

    +10%

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

6 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

    Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 185 ms

    185 ms

    Real visitors wait 185 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 19% faster for real visitors

    -19%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 30 ms

    30 ms

    Scripts block the page for only 30 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix83
  • 2 images far larger than shown

    178 KiB

    2 images are downloaded at several times the size a phone draws them, for example S'affilier-en-ligne.jpg at 800 px wide, shown at 110 px. Resized copies would save about 178 KiB.

  • 12 images below the first screen load straight away

    12 images further down the page (472 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (92 KiB) 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 0.5 g of CO₂ per visit

    0.52 g

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

1 checks passed
  • Page weight: 1.8 MB in 58 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 58 requests on a phone: images 1.1 MB (35), scripts 307 KiB (14) and fonts 247 KiB (4). That is a lean page.

Accessibility

6 to fixGoogle 9692
  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 32 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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

4 to fixGoogle 10084
  • 3 H1 headlines

    There are 3 <h1> headlines (“Prenez soin de vous avec les Avantages Partenamut”, “Cancer du sein : faites-vous dépister !” and “Rejoignez Partenamut dès aujourd’hui”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.partenamut.be/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at partenamut.be/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 181 internal links, 23 external

    The homepage links to 181 pages on partenamut.be and 23 external pages.

4 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Un remboursement pour vos soins de santé ? La mutuelle libre Partenamut est là ! Découvrez ici vos avantages et nos ass…”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Cultivons votre santé ! | Partenamut Mutualité Libre en Belgique”.

  • Canonical URL set

    The canonical URL is https://www.partenamut.be/fr.

  • Structured data in place

    Structured data found: Organization.

AI search readiness

100
  • No llms.txt

    There is no https://www.partenamut.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.

3 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Organization data: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix93
  • 2 pages share a title

    / and https://www.partenamut.be/fr all use the title “Cultivons votre santé ! | Partenamut Mutualité Libre en Belgique”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 internal pages checked

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

  • 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

2 to fixGoogle 9687
  • 6 small tap targets

    6 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Unrecognized Content-Security-Policy directive 'navigate-to'.”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 analytics detected

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

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

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

3 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Partenamut Shop”, “Aide et contact” and “Video Call”.

  • 2 short forms

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

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 partenamut.be, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Hosting
Combell

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 partenamut.be, including 12 speed issues, 4 SEO issues and 3 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