montel.nl website review

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

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

Your mobile performance score is 77 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

4 third-party services load with your homepage (Google Tag Manager, Cookiebot and elfsight.com and others), adding 554 KiB and 268 ms of main-thread time.

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

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

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

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

Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Onze Banken Marathon is gestart”.

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

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

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

1 image is downloaded at several times the size a phone draws it, for example https://s.montel.nl/typo3/user_upload/M_2026_012%20jubileum% at 864 px wide, shown at 188 px. Resized copies would save about 31 KiB.

4 images further down the page (160 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.46 g of CO₂e: 55.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

Banner landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

Structured data found (WebPage and WebSite) but with 1 problem, for example “WebSite: missing name”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 183 pages on montel.nl and 11 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 /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.

/sale and /mijn-montel have no meta description, so Google writes the search snippet from whatever text it finds.

/magazine and /mijn-montel have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 406 ()”.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

montel.nl has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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