garmundo.nl website review

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

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

27 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

8 third-party services load with your homepage (Bugsnag, Google Tag Manager and Clarity and others), adding 921 KiB and 1.2 s of main-thread time.

Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

Bugsnag costs a phone 479 ms of main-thread work and 27 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.

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

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

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

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

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

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

2 KiB could be saved by minifying JavaScript.

Your largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Image 37010545049875”.

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

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

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

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

Your homepage downloads 6.3 MB in 311 requests on a phone: images 4.0 MB (96), scripts 1.2 MB (108) and other files 674 KiB (84). Under 2 MB keeps phones on slow connections fast.

37 images (4.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.

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

ARIA attributes must conform to valid values: 6 elements on the page fail this check, rated critical by axe-core.

<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 12 elements on the page fail this check, rated serious by axe-core.

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

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

Your title is only 8 characters: “Garmundo”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 38 characters: “Samen maken we de wereld écht groener.”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 252 pages on garmundo.nl and 3 external pages.

https://garmundo.nl/collections/blote-wortel-planten, https://garmundo.nl/collections/populaire-haagplanten, https://garmundo.nl/collections/groenblijvende-haagplanten, https://garmundo.nl/collections/bladverliezende-haagplanten, https://garmundo.nl/collections/snelgroeiende-haagplanten and https://garmundo.nl/collections/bloeiende-haagplanten and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://garmundo.nl/collections/bladverliezende-haagplanten took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 100 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=136014584&Ver=2&mid=6ece751f-2b4c-4e34-832f-2f3e11c21874&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Garmundo&p=https%3A%2F%2Fgarmundo.nl%2F&r=&lt=6818&mtp.

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

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.

Social proof on the homepage: 48 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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