movingintelligence.nl website review

About 588 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, PageSense and Cookiebot and others), adding 893 KiB and 699 ms of main-thread time.

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

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

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

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

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

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

8 KiB could be saved by minifying JavaScript.

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 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Knowledge in motion Al ruim 25 jaar partner in slimme mobil…”. Most of its time is resource load delay (5.1 s).

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

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

Real visitors wait 866 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Scripts block taps and scrolling for 332 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 89 ms to 103 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 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.6 MB in 194 requests on a phone: scripts 1.6 MB (27), images 649 KiB (17) and other files 256 KiB (143). Under 2 MB keeps phones on slow connections fast.

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

2 images are downloaded at several times the size a phone draws them, for example small_bmw_logo_logo_png_transparent_d2a7e0ee91.png at 500 px wide, shown at 40 px. Resized copies would save about 103 KiB.

3 images (150 KiB) 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.

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

7 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: 24 elements on the page fail this check, rated moderate by axe-core.

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

Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

The homepage links to 62 pages on movingintelligence.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.

Your homepage links to /voertuigbeveiliging/voertuigvolgsysteem, which answers with an error. Visitors hit a dead end and search engines drop it.

/dealer-pagina and /rittenregistratie are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/zoeken has no meta description, so Google writes the search snippet from whatever text it finds.

/zoek-een-dealer and /dealer-pagina use the same meta description. A description written for each page earns more clicks.

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

/zoeken has 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.

/voertuigbeveiliging, /voertuigbeveiliging/startonderbreker, /rittenregistratie, /rittenregistratie-app, /rittenregistratie/belastingdienst and /demo-boeken and 2 others took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'textContent')”.

Large scripts ship without source maps.

2 links from your homepage to your own site are broken, for example https://movingintelligence.nl/zoek-een-dealer (500).

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

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

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

movingintelligence.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.

There is no form on the homepage, so every lead has to click through to another page first.

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 675 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 Ads, Google Analytics and 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 5 cookies (measured from a US location before any click).

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