secu.nl website review

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

About 149 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).

8 third-party services load with your homepage (Google Tag Manager, cookieconsent.io and Klaviyo and others), adding 605 KiB and 299 ms of main-thread time.

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

32 KiB could be saved by minifying JavaScript.

About 38 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 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Hier waakt SecuStrip! Laat zien dat inbrekers uw huis beter…”.

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

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

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

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

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

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

Your homepage downloads 2.2 MB in 170 requests on a phone: other files 677 KiB (73), scripts 585 KiB (49) and images 511 KiB (30). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (96 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

2 visible links have no text or label, so screen readers cannot say where they go.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 5 <h1> headlines (“SecuProducts BV”, “Hier waakt SecuStrip!” and “8 tips om uw voordeur tegen inbraak te beveiligen”). One clear main headline is easier for people and search engines.

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

The homepage links to 160 pages on secu.nl and 7 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://secu.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://secu.nl/collections/secustrips, https://secu.nl/collections/secubar, https://secu.nl/collections/secumax, https://secu.nl/collections/secuguard and https://secu.nl/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://secu.nl/collections/secustrips, https://secu.nl/collections/secubar, https://secu.nl/collections/secumax, https://secu.nl/collections/secuguard, https://secu.nl/collections/all and https://secu.nl/pages/store-locator have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://edge.cookieconsent.io/prod/css/cookie-consent-v2.css' from origin 'https://secu.nl…”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 368 words of visible text.

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.

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