outdoorheld.nl website review

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

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

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

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

8 third-party services load with your homepage (Facebook, gemcommerce.com and Shopify and others), adding 864 KiB and 297 ms of main-thread time.

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

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

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

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

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.

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

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

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

3 images are downloaded at several times the size a phone draws them, for example 1_2.jpg at 2,700 px wide, shown at 245 px. Resized copies would save about 593 KiB.

Your homepage downloads 2.4 MB in 97 requests on a phone: images 1.3 MB (9), scripts 766 KiB (49) and fonts 205 KiB (7). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (481 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Your title is only 28 characters: “OutdoorHeld – OutdoorHeld NL”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 20 characters: “OutdoorHeld; Outdoor”. 70 to 160 characters is enough to sell the click.

Your <h1> is empty.

The homepage links to 30 pages on outdoorheld.nl and 1 external page.

There is no https://outdoorheld.nl/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.

https://outdoorheld.nl/collections/sale, https://outdoorheld.nl/collections/blotevoeten-schoenen, https://outdoorheld.nl/collections/zadel and https://outdoorheld.nl/collections/inlegzolen have no meta description, so Google writes the search snippet from whatever text it finds.

https://outdoorheld.nl/collections/sale, https://outdoorheld.nl/collections/blotevoeten-schoenen, https://outdoorheld.nl/collections/zadel and https://outdoorheld.nl/collections/inlegzolen have no <h1> headline, so visitors and search engines get no clear main topic.

https://outdoorheld.nl/collections/sale, https://outdoorheld.nl/collections/blotevoeten-schoenen, https://outdoorheld.nl/collections/zadel and https://outdoorheld.nl/collections/inlegzolen 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.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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 593 words of visible text.

Before a visitor clicks anything, the page loads Meta Pixel (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 9 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.