weekampdeuren.nl website review

14 images could be 4.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.7 s faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Optanon and others), adding 1.0 MB and 907 ms of main-thread time.

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

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

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

212 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Polyfills for old browsers add 18 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.

Your largest element takes 18.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Ontdek onze deurenseries Perfect passend. Welkom thuis. Bin…”.

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

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

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

13 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-17, real Chrome visitors' tap response (inp) went from 107 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 11.6 MB in 321 requests on a phone: images 9.2 MB (32), scripts 1.5 MB (220) and fonts 783 KiB (10). Under 2 MB keeps phones on slow connections fast.

6 images weigh 5.7 MB together. On a phone connection a single image that size takes seconds.

17 images (7.7 MB) 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.

1 image is downloaded at several times the size a phone draws it, for example Weekamp-Magazine-mockup.jpg at 1,000 px wide, shown at 311 px. Resized copies would save about 6 KiB.

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

Certain ARIA roles must be contained by particular parents: 14 elements on the page fail this check, rated critical by axe-core.

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

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

Some list items are not inside a list.

1 element hidden from screen readers can still receive keyboard focus.

Page should contain a level-one heading: 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.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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

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 55 pages on weekampdeuren.nl and 14 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.

/over-weekamp, /service, /contact, /voordeuren and /binnendeuren have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /diensten/weekamp-montageservice, whose canonical is /service/weekamp-montageservice. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/informatie has no <h1> headline, so visitors and search engines get no clear main topic.

/dealers, /service, /informatie and /inspiratie 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.

/diensten/weekamp-montageservice took over 3 s to send its HTML from our server.

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

Chrome logged issues while loading the page (“Content security policy”).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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.

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

DMARC is set to p=none, so mail pretending to be weekampdeuren.nl is still delivered. Reports are on, so moving to quarantine is the next step.

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 Ads, Google Analytics, Google Tag Manager and Hotjar (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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