Website review, no card needed

bonusan.com logo

bonusan.com website review

Visit site (opens in a new tab)Reviewed 24 October 202643 issues · 84 checks

This review found 43 issues worth fixing on bonusan.com, 21 of them high impact, across 84 checks. The most urgent: avoid multiple page redirects. 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.6 s1.2 sMay 2Oct 172.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.4 s
May 9, 20261.4 s
May 16, 20261.6 s
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20262.0 s
Sep 12, 20262.2 s
Sep 19, 20262.3 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
185 ms143 msMay 2Oct 17180 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026148 ms
May 9, 2026148 ms
May 16, 2026154 ms
May 23, 2026155 ms
May 30, 2026160 ms
Jun 6, 2026164 ms
Jun 13, 2026163 ms
Jun 20, 2026165 ms
Jun 27, 2026168 ms
Jul 4, 2026170 ms
Jul 11, 2026171 ms
Jul 18, 2026170 ms
Jul 25, 2026165 ms
Aug 1, 2026165 ms
Aug 8, 2026168 ms
Aug 15, 2026172 ms
Aug 22, 2026178 ms
Aug 29, 2026177 ms
Sep 5, 2026178 ms
Sep 12, 2026179 ms
Sep 19, 2026178 ms
Sep 26, 2026179 ms
Oct 3, 2026179 ms
Oct 10, 2026178 ms
Oct 17, 2026180 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 bonusan.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bonusan.com at 0.8 s0.8 s
  2. bonusan.com at 1.6 s1.6 s
  3. bonusan.com at 2.4 s2.4 s
  4. bonusan.com at 3.2 s3.2 s
  5. bonusan.com at 3.9 s3.9 s
  6. bonusan.com at 4.7 s4.7 s
  7. bonusan.com at 5.5 s5.5 s
  8. bonusan.com at 6.3 s6.3 s

Speed

13 to fix39
  • Avoid multiple page redirects

    56.7 s

    The page goes through 1 redirect before it starts loading, costing about 56.7 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    10.3 s · 1.8 MB

    About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.3 s faster on a phone.

  • Improve image delivery

    3.0 s · 5.7 MB

    16 images could be 5.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.

  • Reduce unused CSS

    2.5 s · 217 KiB

    About 217 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.5 s faster on a phone.

  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 8.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Facebook and others), adding 1.9 MB and 1.7 s of main-thread time.

  • Google Tag Manager adds 984 ms

    984 ms

    Google Tag Manager costs a phone 984 ms of main-thread work and 1.0 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.

  • Use efficient cache lifetimes

    250 ms · 311 KiB

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

  • 20 long tasks on the main thread

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

  • ZenDesk adds 183 ms

    183 ms

    ZenDesk costs a phone 183 ms of main-thread work and 413 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,851 HTML elements

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

  • Legacy JavaScript

    36 KiB

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

  • 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: 102 ms

    102 ms

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

Core Web Vitals

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

  • First Contentful Paint: 7.7 s

    7.7 s

    The first text or image appears after 7.7 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 64.5 s

    64.5 s

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

  • Speed Index: 19.5 s

    19.5 s

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

  • Time to Interactive: 77.6 s

    77.6 s

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

  • Total Blocking Time: 639 ms

    639 ms

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

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

    +21%

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

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

    +70%

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

  • Real-user TTFB: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

  • 2 images without width and height

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

5 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 151 ms

    151 ms

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

  • Real-user CLS: 0.05

    0.05

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0.043

    0.043

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

Images and page weight

1 to fix70
  • Page weight: 19.5 MB in 419 requests

    19.5 MB

    Your homepage downloads 19.5 MB in 419 requests on a phone: images 13.9 MB (169), scripts 4.6 MB (161) and stylesheets 450 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 5.5 g of CO₂ per visit

    5.53 g

    By the Sustainable Web Design model, a visit to your homepage emits about 5.53 g of CO₂e: 663.1 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

8 to fixGoogle 7889
  • Unlabelled dropdowns

    9 dropdowns have no label.

  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 22 text elements with low contrast

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

  • 10 form fields without a label

    10 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 3 links without text

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • Headings should not be empty (9 elements)

    Headings should not be empty: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • 2 H1 headlines

    There are 2 <h1> headlines (“Gezondheid begint met begrijpen.” and “Gezondheid begint met begrijpen.”). One clear main headline is easier for people and search engines.

  • 176 internal links, 8 external

    The homepage links to 176 pages on bonusan.com and 8 external pages.

7 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Bekijk het aanbod voedingssupplementen bij Bonusan eenvoudig online ✓120 jaar ervaring ✓Gratis bezorging vanaf €50,- ✓B…”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Bonusan Voedingssupplementen Online Bestellen | Bonusan”.

  • Canonical URL set

    The canonical URL is https://www.bonusan.com/nl-NL/.

  • Structured data in place

    Structured data found: 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://www.bonusan.com/nl-NL/sitemap.xml.

AI search readiness

2 to fix70
  • 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.

  • Parts of the site are closed to 1 AI crawler

    Your robots.txt lets ChatGPT search (OAI-SearchBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • No llms.txt

    There is no https://www.bonusan.com/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
  • Text is in the HTML

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

Other pages

3 to fix85
  • 2 pages without a meta description

    https://www.bonusan.com/nl-NL/producten/daily-essentials/bundels and https://www.bonusan.com/nl-NL/gezondheidsdoel/daily-essentials have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.bonusan.com/nl-NL/producten/daily-essentials/bundels, whose canonical is https://www.bonusan.com/nl-NL/producten/ontdek-meer/bundels. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 13 pages without an H1

    https://www.bonusan.com/nl-NL/gezondheidsdoel/bloedsuiker, https://www.bonusan.com/nl-NL/gezondheidsdoel/botten, https://www.bonusan.com/nl-NL/gezondheidsdoel/cholesterol, https://www.bonusan.com/nl-NL/gezondheidsdoel/concentratie-en-geheugen, https://www.bonusan.com/nl-NL/gezondheidsdoel/daily-essentials and https://www.bonusan.com/nl-NL/gezondheidsdoel/energie and 7 others 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 134 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=355052728&tm=gtm002&Ver=2&mid=47d18376-c2b3-4396-b89a-9e0c14a4b21d&bo=2&sid=901235f0cfbe11f1af12d1182b778c39&vid=901257c0cfbe11f1bd6633d085aa7fa6&vids=0&msclkid=N&gtm_.

  • 2 JavaScript errors while loading

    2 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

    21 of 25 tappable elements near the top are at least 24 px.

  • 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 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 1,154 words of copy

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

3 checks passed
  • 9 short forms

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

  • Social proof on the page

    Social proof on the homepage: 20 testimonial or review blocks, 10 customer or partner logos and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies (measured from a US location before any click).

  • 33 other companies contacted

    Loading the homepage contacts 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 bonusan.com, 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
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 43 issues on bonusan.com, including 23 speed issues, 1 SEO issue 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