degroot.nl website review

1 image could be 61 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Facebook, ContentSquare and cookiebot.eu and others), adding 815 KiB and 234 ms of main-thread time.

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

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

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

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

2 KiB could be saved by minifying JavaScript.

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.

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

Real visitors wait 337 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 223 ms to 260 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.2 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

The homepage links to 161 pages on degroot.nl and 8 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.

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

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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

Before a visitor clicks anything, the page loads Google Ads, LinkedIn Insight and Meta Pixel (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 13 cookies (measured from a US location before any click).

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