solvari.nl website review

4 images could be 421 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

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

Cloudinary costs a phone 0 ms of main-thread work and 756 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.

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

About 155 KiB of JavaScript is downloaded but never used on this page.

7 third-party services load with your homepage (Bing Ads, Google Tag Manager and FontAwesome CDN and others), adding 823 KiB and 31 ms of main-thread time.

Desktop scores 95 but mobile only 67. A gap that wide usually means heavy scripts and images that hit phones hardest.

1 file is served with short cache lifetimes, so returning visitors download them again (6 KiB).

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Je bepaalt zelf welke data wij mogen gebruiken door je cook…”.

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

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

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

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

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

3 images are downloaded at several times the size a phone draws them, for example dakrenovatie.jpg at 3,586 px wide, shown at 364 px. Resized copies would save about 686 KiB.

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

1 image (303 KiB) is 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.47 g of CO₂e: 56.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

2 links inside paragraphs rely on colour alone to stand out.

All page content should be contained by landmarks: 2 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.

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

Your title is only 26 characters: “Solvari | Bouwt vertrouwen”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 32 pages on solvari.nl and 14 external pages.

There is no https://www.solvari.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.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.solvari.nl/bedrijven-overzicht/reinas-bv, whose canonical is https://www.solvari.nl/kozijnen/limburg/echt-susteren/reinas-bv-echt. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.solvari.nl/vacatures has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=5062185&tm=gtm002&Ver=2&mid=4fb02dc9-3f23-46ce-9126-1b9ee3ca55e3&bo=2&page_path=%2F&tpp=1&spa=Y&r=&lt=2566&p=https%3A%2F%2Fwww.solvari.nl%2F&pi=918639831&lg=en-US&sw=3.

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 401 ()”.

Large scripts ship without source maps.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Tag Manager and Microsoft Ads (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 2 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.