maiburg.nl website review

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

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

About 637 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.0 s faster on a phone.

Your mobile performance score is 24 (desktop: 35). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, hsappstatic.net and Cookiebot and others), adding 2.5 MB and 3.3 s of main-thread time.

140 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).

About 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

112 KiB could be saved by minifying CSS.

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

hsappstatic.net costs a phone 618 ms of main-thread work and 713 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.

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

Cookiebot costs a phone 484 ms of main-thread work and 77 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.

Hotjar costs a phone 467 ms of main-thread work and 251 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.

Facebook costs a phone 403 ms of main-thread work and 264 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.

381 KiB could be saved by minifying JavaScript.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Polyfills for old browsers add 88 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 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Maiburg heeft een zeer compleet aanbod in materialen en tec…”.

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

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

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

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

43 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 156 ms to 170 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.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.5 MB in 293 requests on a phone: images 6.7 MB (58), scripts 4.6 MB (165) and stylesheets 716 KiB (12). Under 2 MB keeps phones on slow connections fast.

3 images weigh 3.8 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example Loba-ImpactOil-header-2.png at 2,000 px wide, shown at 320 px. Resized copies would save about 3.9 MB.

40 images (6.5 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.

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

3 buttons have no accessible name, so screen readers announce just “button”.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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.

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

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

6 links have no real href, so search engines can't follow them.

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

The homepage links to 505 pages on maiburg.nl and 5 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://www.maiburg.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.

/ and https://www.maiburg.nl/maiburg/nl/EUR all use the title “Maiburg | Wij helpen vakmensen vooruit”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.maiburg.nl/maiburg/nl/EUR, https://www.maiburg.nl/maiburg/nl/EUR/Interieur, https://www.maiburg.nl/maiburg/nl/EUR/Keukenbouw, https://www.maiburg.nl/maiburg/nl/EUR/schilder, https://www.maiburg.nl/maiburg/nl/EUR/verpakkingen and https://www.maiburg.nl/maiburg/nl/EUR/Automotive and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.maiburg.nl/maiburg/nl/EUR, https://www.maiburg.nl/maiburg/nl/EUR/Keukenbouw, https://www.maiburg.nl/maiburg/nl/EUR/schilder, https://www.maiburg.nl/maiburg/nl/EUR/Yachting-Marine, https://www.maiburg.nl/maiburg/nl/EUR/verpakkingen and https://www.maiburg.nl/maiburg/nl/EUR/Automotive and 1 other took over 3 s to send their HTML from our server.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “screenMd is not defined”.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 5 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 230 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 3 mores (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 30 cookies (measured from a US location before any click).

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