weightworld.nl website review

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

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

8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and Clarity and others), adding 1.4 MB and 790 ms of main-thread time.

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

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

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

Shopify costs a phone 79 ms of main-thread work and 749 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.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

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

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

8 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

The layout shifts by 0.491 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 4.2 MB in 499 requests on a phone: other files 1.4 MB (263), scripts 1.2 MB (126) and images 1.2 MB (55). Under 2 MB keeps phones on slow connections fast.

10 images (551 KiB) are 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.

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

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

2 images have no alt text, which hurts accessibility and image search.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 70 characters, so Google will cut it off around 60: “Natuurlijk Afvallen | Info en Advies over gewichtsverlies | WeightWorl”.

Your meta description is 225 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BreadcrumbList, ItemList, Organization and WebSite) but with 1 problem, for example “ld+json block 6 is not valid JSON (Bad control character in string literal in JSON at position )”.

2 links have no real href, so search engines can't follow them.

Your <h1> is empty.

The homepage links to 278 pages on weightworld.nl and 18 external pages.

https://www.weightworld.nl/collections/all and https://www.weightworld.nl/collections/shop-all have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.weightworld.nl/products/omega-3-visolie-2000-mg, https://www.weightworld.nl/products/magnesium-bisglycinaat-capsules, https://www.weightworld.nl/products/pure-coq10-capsules, https://www.weightworld.nl/products/multivitaminen-en-mineralen-400-tabletten, https://www.weightworld.nl/products/pure-marine-collageen and https://www.weightworld.nl/products/biologische-kurkuma-met-zwarte-peper-en-gember and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 119 found) and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.weightworld.nl/cdn/shop/t/2/assets/cc-slideshow.css?v=11858' because its MIME …”.

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

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 585 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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

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

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.

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