Website review, no card needed

bella-fit.nl logo

bella-fit.nl website review

Visit site (opens in a new tab)Reviewed 8 November 202626 issues · 75 checks

This review found 26 issues worth fixing on bella-fit.nl, 8 of them high impact, across 75 checks. The most urgent: 2 buttons without a name. 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
1.3 s508 msMay 16Oct 24604 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Sep 12, 20261.1 s
Oct 3, 2026901 ms
Oct 10, 2026684 ms
Oct 17, 2026625 ms
Oct 24, 2026604 ms
Real-visitor tap response (INP)75th percentile, phones
1.2 s0 msMay 16Oct 24137 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 20261.1 s
May 23, 2026436 ms
May 30, 2026264 ms
Jun 6, 2026237 ms
Jun 13, 2026243 ms
Jun 20, 2026251 ms
Jun 27, 2026265 ms
Jul 4, 2026308 ms
Jul 11, 2026312 ms
Jul 18, 2026311 ms
Jul 25, 2026289 ms
Aug 1, 2026251 ms
Aug 8, 2026235 ms
Aug 15, 2026229 ms
Oct 3, 2026161 ms
Oct 10, 2026147 ms
Oct 17, 2026137 ms
Oct 24, 2026137 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 bella-fit.nl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix91
  • 3,655 HTML elements

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

  • Render-blocking requests

    700 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Shopify and others), adding 1.2 MB and 576 ms of main-thread time.

  • Google Tag Manager adds 570 ms

    570 ms

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

    384 KiB

    About 384 KiB of JavaScript is downloaded but never used on this page.

  • 6 long tasks on the main thread

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

  • Improve image delivery

    142 KiB

    4 images could be 142 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    73 KiB

    About 73 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    14 KiB

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

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

3 checks passed
  • Mobile performance score: 91

    91/100

    Your mobile performance score is 91. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.5 s

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

  • Server response: 40 ms

    40 ms

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

Core Web Vitals

3 to fix92
  • Time to Interactive: 13.6 s

    13.6 s

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

  • Total Blocking Time: 323 ms

    323 ms

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

  • Speed Index: 3.8 s

    3.8 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

5 checks passed
  • Tap response (INP) got 82% faster for real visitors

    -82%

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

  • Largest content (LCP) got 50% faster for real visitors

    -50%

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.

Images and page weight

3 to fix69
  • Page weight: 2.7 MB in 96 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 96 requests on a phone: scripts 1.4 MB (35), images 895 KiB (36) and fonts 241 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Bella_Fit_Campaign_56.jpg 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).

  • 2 images far larger than shown

    190 KiB

    2 images are downloaded at several times the size a phone draws them, for example luxury-silicone-nipple-covers-set-van-2-paar-786257_0006168e at 1,500 px wide, shown at 88 px. Resized copies would save about 190 KiB.

  • About 0.8 g of CO₂ per visit

    0.76 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 7489
  • 2 buttons without a name

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

  • 35 tap targets too small

    35 tap targets are too small or too close together to hit reliably with a finger.

  • 33 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 9 links without text

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (17 elements).

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093
  • Title is long (81 characters)

    Your title is 81 characters, so Google will cut it off around 60: “Bella Fit: Beste Keus in Corrigerende Onderkleding en Waist Trainers – Bella Fit™”.

  • 168 internal links, 0 external

    The homepage links to 168 pages on bella-fit.nl and 0 external pages.

7 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Vind je perfecte shapewear, waist trainers, beauty producten en nog veel meer bij Bella Fit! ✓ Nieuwste trends ✓ Beste …”.

  • One H1 headline

    Your main headline reads: “ZOMER UITVERKOOP”.

  • Canonical URL set

    The canonical URL is https://www.bella-fit.nl/.

  • Structured data in place

    Structured data found: Organization and 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.bella-fit.nl/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.bella-fit.nl/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 5 pages without a meta description

    https://www.bella-fit.nl/collections/bodysuit, https://www.bella-fit.nl/collections/seamless-shapewear, https://www.bella-fit.nl/collections/bhs, https://www.bella-fit.nl/collections/corrigerende-jurken and https://www.bella-fit.nl/collections/nipple-covers have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://www.bella-fit.nl/collections/bestsellers, https://www.bella-fit.nl/collections/shapewear-corrigerend-ondergoed-bodysuit, https://www.bella-fit.nl/collections/bodysuit, https://www.bella-fit.nl/collections/seamless-shapewear, https://www.bella-fit.nl/collections/bhs and https://www.bella-fit.nl/collections/corrigerende-jurken and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.bella-fit.nl/products/selma-strapless-contour-butt-lifting-bodysuit and https://www.bella-fit.nl/products/ashley-seamless-shaping-bra-with-adjustable-shoulder-straps have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

1 to fixGoogle 9693
  • 51 small tap targets

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

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

    The homepage carries about 791 words of visible text.

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 5 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 8 cookies set on arrival

    8

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

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

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 bella-fit.nl, 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 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Timesact Pre Order · Gg Product Gallery · Ta Labels Badges · Kaching Cart · Instafeed · Klaviyo Email Marketing Sms · Pagefly Ai Page Builder · Pmslider Rb · Page Speed Optimizer · Smart Menu · snapchat.com · salessquad.co.uk · loox.io

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

Framework
jQuery
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 26 issues on bella-fit.nl, including 8 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