stanbarry.nl website review

About 405 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 1.2 MB and 1.1 s of main-thread time.

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

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

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

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

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

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

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SB198-Leather-Wearing-silver-3.jpg”.

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

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

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

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

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

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

Your homepage downloads 3.6 MB in 259 requests on a phone: scripts 1.3 MB (73), images 1.2 MB (42) and other files 831 KiB (100). Under 2 MB keeps phones on slow connections fast.

SB198-Leather-Wearing-silver-3.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 (146 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.01 g of CO₂e: 121.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Links must have discernible text: 6 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

Your <h1> is empty.

The homepage links to 157 pages on stanbarry.nl and 9 external pages.

https://www.stanbarry.nl/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.stanbarry.nl/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.stanbarry.nl/collections/all, https://www.stanbarry.nl/customer_authentication/redirect, https://www.stanbarry.nl/collections/fotoarmband, https://www.stanbarry.nl/collections/armbanden, https://www.stanbarry.nl/collections/kettingen and https://www.stanbarry.nl/collections/gepersonaliseerde-juwelen and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.stanbarry.nl/collections/all, https://www.stanbarry.nl/customer_authentication/redirect, https://www.stanbarry.nl/apps/parcelpanel, https://www.stanbarry.nl/pages/faq and https://www.stanbarry.nl/pages/help-center have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.stanbarry.nl/collections/all has 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.

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 799 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 3 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 25 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 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.