lockoutstore.nl website review

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

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

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

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

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

10 images could be 236 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

4 third-party services load with your homepage (Shopify, Google Tag Manager and shop.app and others), adding 770 KiB and 239 ms of main-thread time.

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

1 long task block the main thread while loading, the longest for 77 ms. During a long task the page ignores taps.

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

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

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.

Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “LOTO veiligheidssloten en lockout tagout materiaal voor ind…”.

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

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

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.

Your homepage downloads 2.2 MB in 286 requests on a phone: other files 962 KiB (114), scripts 654 KiB (116) and images 405 KiB (16). Under 2 MB keeps phones on slow connections fast.

1 image (33 KiB) is 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.

1 image further down the page (23 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.63 g of CO₂e: 75.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

Your title is 85 characters, so Google will cut it off around 60: “LOTO & Lockout Tagout Materialen — B2B Specialist | LockOutStore.nl – LOCKOUTSTORE.nl”.

1 link has no real href, so search engines can't follow it.

Your <h1> is empty.

The homepage links to 81 pages on lockoutstore.nl and 0 external pages.

There is no https://www.lockoutstore.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://www.lockoutstore.nl/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 10 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.